Re: [poe] source of a *Collection (and also Asset/Party?)

@nitmws I am not sure I understand your question. But if I guess it right: the 'URI hijacking' refers to a situation when the same subject is reused on the Semantic Web. E.g., if there is a statement somewhere saying 

``
<https://www.ivan-herman.net/#me> ex:isA ex:computer_scientist .
``

then third parties have to be careful whether they would assign new triples for that subject. Something like

``
<https://www.ivan-herman.net/#me> ex:isA ex:mathematician .
``

may be (sort of) o.k., but

``
<https://www.ivan-herman.net/#me> ex:isA ex:musician .
``

wouldn't be.

I do not think the usage of `source` is problematic. It designates, via a URL, an _object_, which is fine.

B.t.w., the issue of hijacking is really essential (and needs extra care) when the subject is a term in a _vocabulary_. You do not want, for example, to declare in your vocabulary a predicate in _another_ vocabulary to be functional. That may have far reaching consequences if, in this case, OWL inference engines take all statements concerning that predicate into account.







-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at https://github.com/w3c/poe/issues/258#issuecomment-329400488 using your GitHub account

Received on Thursday, 14 September 2017 07:40:19 UTC