lines for a scenario like this, and it's pretty frustrating because
> not all data need to be dereferenceable and not all data need to have a
> universally unique ID such as ISBN or telephone number...
>
>
>
> Sent: Wednesday, May 23, 2018 at 3:26 PM
> From: ajs6f <aj...@a
a.apache.org
Subject: Re: Nodes without dereferenceable URIs
Maybe you can tell us more about your use case(s) and the workflow(s) with
which you expect to use this data?
There is no general best practice here, but there are techniques that are
better and worse for some given situation.
ajs6f
>
hone number...
>
>
>
>
>
>
>
> Sent: Wednesday, May 23, 2018 at 3:26 PM
> From: ajs6f <aj...@apache.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
ajs6f <aj...@apache.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. If someone
might tr
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. If someone
might try to dereference them, that's when you might have problems.
ajs6f
> On May 22, 2018, at 2:01
Don't use blank nodes. You will regret it in the long run.
On Tue, May 22, 2018 at 4:43 PM, Laura Morales wrote:
> How can I deal with a RDF graph where I don't have dereferenceable URIs,
> but still need the URIs to link with other graphs? For example if I have a
> personal
How can I deal with a RDF graph where I don't have dereferenceable URIs, but
still need the URIs to link with other graphs? For example if I have a personal
graph of documents that I only need to use for myself, what URIs should I use?
Blank nodes?
_:document1
_:document2
_:document3
or do I