RDF 303 redirect clarification -
i'd confirm 303 redirect protocol implication.
if 1 follow convention of building rdf (resources/instances file opposed vocabularies) using slash uri instead of hash uri flexibility purpose, mean each resource instance must have redirect defined (if want them dereferencable)? meaning must define purl 303 redirect each resource either same or different file see fit?
also, along way can tell me difference between information resource , non-information resource (also called real world object)? more specifically, not resource description framework stand information resource description framework? maybe better explanation of resource on web help.
can clarify concepts?
you think of information resource web document, , of non-information resource thing. (not definition, rough idea.)
i tried explain difference in this answer:
a http uri identify page or thing page about. can't tell if uri identifies page or thing looking @ it.
example (in turtle syntax):
<http://en.wikipedia.org/wiki/the_lord_of_the_rings> ex:author "john doe"
this could mean html page uri
http://en.wikipedia.org/wiki/the_lord_of_the_rings
authored "john doe". or mean thing described html page (→ novel) authored "john doe".
it’s practice make possible others can differentiate when re-using uris or data. however, not required; think non-issue or not worth effort.
the discussion differentiation known httprange-14 issue ("what range of http dereference function?").
some possible solutions are:
- hash uris (see example in answer)
- 303 uris (see dbpedia example in answer)
- property categories (rather new , not well-known; see my question brief explanation)
so when use "slash uris", , care differentiation (and think should!), yes, have use 303 redirect.
otherwise (if you’d send 200), user agents follow tag’s resolution think uri identifies information resource.
Comments
Post a Comment