[rdfweb-dev] foaf.rdf as a requirement
wkearney99 at hotmail.com
Thu Jul 3 18:44:57 UTC 2003
> It does raise a good question though, how to handle "formally FOAF'd as" :
> Let's say my primary FOAF file is currently http://wayne.org/foaf.rdf but
> for some reason it moves to http://waynetta.org/foaf.rdf. Would it be
> better to use http 301 Moved, or something explicit within the RDF? In the
> new file and/or the old?
I greatly favor using in-band redirection and not leaving it up to the
transport. Yes, using the 301 redirects is a fine idea but the RDF itself
should contain it's own indicators of isReplacedBy and replaces. This so as to
maintain the provencance independently of the transport.
More information about the foaf-dev