ollowing hexadecimal digits.
>
> Is not a legal mailto: URI? Or does it
> need to be encoded somehow?
Yes the % character is reserved and must be encoded as %25. See
https://tools.ietf.org/html/rfc6068#page-10
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
v2rdf which is compliant to the W3C's CSV on
the Web specification. You can generate RDF from CSV file by creating a
metadata file (in JSON format) which describes the CSV. It uses URI
Templates to specify how to convert CSV values into resource identifiers.
NB this is different to Martynus's software of
nce,
> Elio HBEICH
>
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
interested in using any particular ontology or
> > > vocabulary for the conversion, so anything will work as long as I can
> > make
> > > the conversion.
> > > What would be an appropriate strategy for this? Since RDF requires
> > > absolute IRIs, woul
pache.org>
> To: users@jena.apache.org
> Subject: Re: Nodes without dereferenceable URIs
> Can you use HTTP URIs that simply don't point to an actual server? (E.g.
> http://lauras.namespace/blah/blah/blah)
>
> If no one tries to dereference them, it's fine if they don't work. I
.tdbloader utilityl, from an N-Quads
file of 3.5M triples. I have some CONSTRUCT queries which run rather
slowly, and I wondered if TDB2 needed a statistics file as TDB used to, or
if there's some other optimization step I might be missing.
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
ajs6f <aj...@apache.org>
> > To: users@jena.apache.org
> > Subject: Re: Use PREFIXes by default
> > If you are not concerned about performance, why not add those prefixes
> client-side?
> >
> >
> > ajs6f
>
>
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
ct my backup? I didn't find information about
> it from the documentation of Fuseki.
>
> Thank you very much!
>
> Sincerely,
> Sherry
>
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
makes it easy to process RDF *as a
graph* in XSLT. Whereas if your dataset is encoded in RDF/XML, it's
enormously difficult to process *as a graph*.
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
t is and always has been a HUGE error to maintain this
> ambiguity that RDF/XML is XML. No no and no, it is RDF.
> May be you can generate RDF/XML via XML tools. Sure.
> But consuming RDF/XML with XML tools is a BAD idea.
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
If it turns out that the problem actually is that your Turtle file is
incorrectly encoded, then Fuseki should return an HTTP 400 (Bad Request)
rather than a 500. Could you log this as a bug, if so?
On 18 Aug 2017 21:19, "Trevor Lazarus" wrote:
> Thanks Andy,
>
> This is what I
ales <laure...@mail.com> wrote:
> What does this warning mean when I execute riot on a .rdf file?
>
> $ riot --validate file.rdf
> WARN riot :: [line: 2, col: 35] {W119} A processing instruction is in RDF
> content. No processing was done.
>
> Here's the head of the
eption if I
> use a literal. My question is, why is this enforced at all? Why can't I
> name my graphs with literals, for example "graph-1" or "graph-2"?
> And related to this question, is there anything wrong (in any way) if I'm
> going to name my graphs , , etc. (bas
on
> > setting or similar which allows me to achieve this.
> > >
> > > Thank you very much in advance for your help
> > >
> > > Jakob
> > >
> > > ___
> > > Dr. Jakob Beetz - Assistant Professor
> > > Information Systems in the Built Environment (ISBE) Group
> > > Department of the Built Environment | Bouwkunde
> > > Eindhoven University of Technology, The Netherlands
> > > phone: +31 (0)40 247 2288 on-campus location: VRT 9.J06
> > >
>
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
if you want to keep track of the provenance of data, you can use named
graphs. If your graphs are small (fine-grained) enough then this may give
you the necessary precision to refer any triple back to its source.
On 18/01/2017 7:49 am, "Grahame Grieve"
wrote:
million.
Can anyone reassure me? Has anyone had problems with large number of named
graphs, and if so, were you able to fix them?
Thanks!
Conal
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
On 12 January 2017 at 12:34, Grahame Grieve <
grah...@healthintersections.com.au> wrote:
> Consider this JSON-LD:
> {
> "@type": "fhir:Claim",
> "@id": "http://hl7.org/fhir/Claim/760152;,
> "Quantity.value": {
> "decimal": 123.45
> }
> "@context": {
> "fhir":
>
> Wrong list for this suggestion, but what is missing from the w3c semantic
> web stack is a general graph transformation language, analogous to XSLT,
> that would allow one to write domain-specific transformations from graph to
> hierarchy.
Isn't this what JSON-LD "Framing" is about?
na question, though; you'd be better off asking on the
public-lod list or similar: https://lists.w3.org/Archives/Public/public-lod/
NB the domain covered by foaf:primaryTopic is foaf:Document, which seems
appropriate for use with named graphs, and the range is owl:Thing, so it's
as general-purpose as you could want.
--
Conal Tuohy
http://conaltuohy.com/
@conal_tuohy
+61-466-324297
On 11 January 2017 at 08:44, Grahame Grieve <
grah...@healthintersections.com.au> wrote:
> >
> > > - how do I know which node is the root node in the json-ld?
> >
> > what you get is a (RDF) graph, and in the general case, several resources
> > are described (cf. for instance the “@graph” in the
. Would it
be possible to put up a page at that address, with sections documenting
all the terms in the Fuseki configuration vocabulary? I would be happy
to contribute to the documentation!
Thanks
Conal
--
Conal Tuohy
eResearch Business Analyst
Victorian eResearch Strategic Initiative
+61-466324297
21 matches
Mail list logo