[foaf-dev] strawpoll: migrate from foaf:holdsAccount to foaf:account?

[Simon Reinhardt]

Peter Ansell wrote:
> For example if I said that <http://twitter.com/p_ansell>
> <twitterPosts> "39" and <http://twitter.com/p_ansell> <contentType>
> "text/html", I would expect that there are two contexts being referred
> to by virtue of a previous declaration that the domain of
> <twitterPosts> is <foaf:Account> and the previous declaration that the
> domain of <contentType> is <document>, and be able to have the
> knowledge that they are that, without simply having a contradiction.
> If foaf:Account for any reason was derived from <document> than there
> wouldn't be a current contradiction, but if the domains are
> independently traversed and segmented so they only apply to their
> localised triples then there could easily be two concepts with one
> name, and future references would have to have a range or domain that
> either made it clear what they were referring to, or they would have
> to refer to both concepts at the same time because that would be the
> nature of the statement. In the example this would mean that I could
> interpret <http://twitter.com/iand> <hasFollower>
> <http://twitter.com/p_ansell> as referring to the foaf:Account
> context, and <file://mycomputer/downloads/twitter.com_p_ansell>
> <copyOf> <http://twitter.com/p_ansell> as referring to the document
> context while <http://mailinglist.org/posts/2008/August/4342.html>
> <containsLinkTo> <http://twitter.com/p_ansell> would have to refer to
> both, otherwise you would not be able to interpret arbitrary links to
> URI's in plain text mailing list posts that could infact not just be
> of type <document>

So, in order to treat the different contexts of triples properly you need to dereference all properties being used and find out their domains and ranges. But doesn't that kind of contradict what you said earlier:

> I don't
> think it is wise to indicate to people that unless they have internet
> access they can't interpret RDF documents as I don't see any reason
> why HTTP GET needs to be performed before any interpretation can
> occur.

Reagards,
  Simon