2008/12/18 Mikkel Kamstrup Erlandsen <[email protected]> > 2008/12/18 Mikkel Kamstrup Erlandsen <[email protected]> > >> Hi all, >> >> I have started to write up some proper documentation for link-by-id as >> discussed on the hackfest (it will land in >> http://xesam.org/main/XesamOntologyAbout when ready). To this end I came >> upon some stuff that needed updating in the onto. Please see the attached >> patch. >> >> What the proposed patch does: >> >> * Document xesam:id and xesam:related as mandatedd by link-by-id >> >> * Make xesam:contactMedium a child of xesam:id. This has pretty big >> consequences - like postal addresses, email addresses and what not to >> suddenly become ids. Nonetheless I think it is the right choice >> >> * Make xesam:url a child of xesam:id >> >> Comments? >> > > I have a comment for myself already :-) > > While it might appear neat to have xesam:postalAddress as ids it also poses > some problems. Namely that I also write in the patch that ids should > generally be prefixed with an URI scheme (like http://, file:// or isbn:// > etc). I would rather not have to write my postal address in an URI :-) > > Obviously this needs a bit of thought... >
And I also forgot the attachment. Great! Here it is... -- Cheers, Mikkel
=== modified file 'xesam.rdfs' --- xesam.rdfs 2008-12-16 22:41:37 +0000 +++ xesam.rdfs 2008-12-18 06:32:44 +0000 @@ -165,7 +165,7 @@ <rdfs:label>xesam:related</rdfs:label> <rdfs:domain rdf:resource="&xesam;Content"/> <rdfs:range rdf:resource="&xss;Uri"/> - <rdfs:comment>Abstract content relation. Use children</rdfs:comment> + <rdfs:comment>Abstract content relation. Please only use the child fields of xesam:related. To form a relation the value of any child field of xesam:related should match up to some xesam:id of the related object, although it is not a requirement that the id in question exists</rdfs:comment> </rdf:Property> <rdf:Property rdf:about="&xesam;contains"> @@ -276,7 +276,7 @@ <rdfs:label>xesam:id</rdfs:label> <rdfs:domain rdf:resource="&xesam;Content"/> <rdfs:range rdf:resource="&xsd;string"/> - <rdfs:comment>Content ID</rdfs:comment> + <rdfs:comment>Abstract object identifier. Please only use the child fields of xesam:id. An id is a string value that uniquely identifies the content. The same must be true for any child field of xesam:id. Generally ids should be prefixed with an URI scheme like http://, file://, or isbn:// to ensure uniqueness among different types of ids. To form a relation to an object add any of the object's xesam:id values in some child field of xesam:related</rdfs:comment> </rdf:Property> <rdf:Property rdf:about="&xesam;contentCreated" xss:maxCardinality="1"> @@ -1478,9 +1478,10 @@ <rdf:Property rdf:about="&xesam;contactMedium"> <rdfs:label>xesam:contactMedium</rdfs:label> + <rdfs:subPropertyOf rdf:resource="&xesam;id"/> <rdfs:domain rdf:resource="&xesam;Contact"/> <rdfs:range rdf:resource="&xsd;string"/> - <rdfs:comment>Generic contact medium</rdfs:comment> + <rdfs:comment>Generic contact medium, ie. a means to contact the individual or organization in question</rdfs:comment> </rdf:Property> <rdf:Property rdf:about="&xesam;imContactMedium"> @@ -1792,6 +1793,7 @@ <rdf:Property rdf:about="&xesam;url" xss:maxCardinality="1"> <rdfs:label>xesam:url</rdfs:label> + <rdfs:subPropertyOf rdf:resource="&xesam;id"/> <rdfs:domain rdf:resource="&xesam;Source"/> <rdfs:range rdf:resource="&xss;Url"/> <rdfs:comment>URL to access the content, this must be a qualified URL and not just a file path. A hint on how to open or interpret the URL may be provided in xesam:urlHint</rdfs:comment>
_______________________________________________ Xesam mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xesam
