Part of the fun (and ease) of RDF is being able to make stuff up as you go along. But, as others have said, when you move past the stage of learning and experimentation, and make your work persistent or reusable, you'll want to be more formal.
The linked data patterns book [1] has several ideas for uris. Regards, --Paul [1] http://patterns.dataincubator.org/book Sent from my iPhone > On Apr 12, 2017, at 13:24, Dick Murray <dandh...@gmail.com> wrote: > > It is for this reason that I use <urn:example:...> and as a nod to my Cisco > engineer days and example.org... :-) > > As Martynas Jusevičius said give it a little thought. > > On 12 April 2017 at 17:37, Martynas Jusevičius <marty...@graphity.org> > wrote: > >> It would not be an error as long it is a valid URI. >> >> Conceptually non-HTTP URIs go against Linked Data principles because >> normally they cannot be dereferenced. >> >> Therefore it makes sense to give it a little thought and choose an >> http:// namespace that you control. >> >> On Wed, Apr 12, 2017 at 6:31 PM, Laura Morales <laure...@mail.com> wrote: >>>> I use "urn:ex:..." in a lot of my test code (short for "urn:example:"). >>>> >>>> Then the predicate is "urn:ex:time/now" or "urn:ex:time/duration" or >>>> whatever you need... >>> >>> would it be an error (perhaps conceptually) to use "ex:...", essentially >> removing the "urn:" scheme? >>
