On 11/3/11 10:05 AM, Martin Hepp wrote:
Hi Kingsley, yes, that puts it more clearly. Note that in the case of www.productontology.org, we have RDFa and Microdata examples already live:http://www.productontology.org/doc/Laser_printer#microdata http://www.productontology.org/doc/Laser_printer#rdfa and even a pattern for combining it with Facebook OGP: http://www.productontology.org/doc/Laser_printer#facebook
So for the stickler in me, it goes like this: Class Identifier:http://www.productontology.org/id/Hammer Representation agnostic access address:http://www.productontology.org/doc/Hammer Representation specific (RDF/XML) access address:http://www.productontology.org/doc/Hammer.rdf Representation specific (N3/Turtle) access address:http://www.productontology.org/doc/Hammer.ttl Representation specific (HTML) access address:http://www.productontology.org/doc/Hammer.html Representation specific (HTML+Microdata data island) access address: http://www.productontology.org/doc/Hammer#microdata Representation specific (HTML+RDFa data island) access address: http://www.productontology.org/doc/Hammer#rdfa . Kingsley
Martin On Nov 3, 2011, at 2:32 PM, Kingsley Idehen wrote:On 11/3/11 5:12 AM, Martin Hepp wrote:You could take the same route thatwww.productontology.org is using for class definitions: Class Identifier http://www.productontology.org/id/Hammer Representation http://www.productontology.org/doc/Hammer RDF/XML http://www.productontology.org/doc/Hammer.rdf N3/Turtle http://www.productontology.org/doc/Hammer.ttl HTML http://www.productontology.org/doc/Hammer.html So in your case, it would be Pattern identifier http://www.ontologydesignpatterns.orh/ekp/id/Game Representation http://www.ontologydesignpatterns.orh/ekp/doc/Game RDF/XML http://www.ontologydesignpatterns.orh/ekp/doc/Game.owl N3/Turtle http://www.ontologydesignpatterns.orh/ekp/doc/Game.ttl HTML http://www.ontologydesignpatterns.orh/ekp/doc/Game.htmlMartin, I agree with your suggestions above, but for sake of clarity (bearing in mind that Linked Data remains challenged in this regard), would you object to: Class Identifier:http://www.productontology.org/id/Hammer Representation agnostic access address:http://www.productontology.org/doc/Hammer Representation specific (RDF/XML) access address:http://www.productontology.org/doc/Hammer.rdf Representation specific (N3/Turtle) access address:http://www.productontology.org/doc/Hammer.ttl Representation specific (HTML) access address:http://www.productontology.org/doc/Hammer.html This simple tweak crystallizes, with clarity, the fact that an object (resource) is endowed with identity that's distinct from its values (graph pictorial that delivers its representation). It also crystallizes why Names have to be distinct from Addresses in the Web's linked data realm even though hyperlinks are used to construct both. In addition, there would be benefits in adding HTML+Microdata and (X)HTML+RDFa representation specific examples, if possible. -- Regards, Kingsley Idehen President& CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
-- Regards, Kingsley Idehen President& CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
