On 3/26/12 3:51 AM, Giovanni Tummarello wrote:
Is annotating IRs is of *any value practical and role today* ?Anything of value and core interest to wikipedia, imdb, bestbuy, bbc, geonames, rottentomatoes, lastfm, facebook, whatever. is a NIR. We are talking people, products Everything on the LOD cloud (for what it matters) its all NIR Even pictures, comments, and text are easiy seen and BEST INTERPRETED as NIR they're not just the bytes they're composed of, they're the full record of their creation, the concept of message. a facebook picture is a full record of content, comments, tags, multiple resolutions etc. The mere stream OF BYTES (the IR) IS JUST A DeTAIL that if it REALLY needs to be annotated, ... it can. no problem, with proper attributes "hasResolution, hascopyright" ok i guess that refers to a IR then. Image (NIR), hasResolution, hasCopyright, andHeyThisIsTheDownloadUrl (your IR url here) So the proposal is to forget immediately the whole distinction and anything else than a simple 200: * Only return 200, * As a default, clients known that they're dealing with Non IR * if you really have to annotate some IR for very low lever purposes then you do it anyway with proper attributes/ontologies .. which clients will know and act accordingly. And we're back into reality, you're compatible with opengraph, schema.org,
Gio,All you are doing is describing the state of play re. Structured Data. You only open up a can of worms when you seek to infer that this is Linked Data.
Linked Data is a kind of Structured Data with specific attributes. Thus, all Structured Data != Linked Data.
As I've already stated in an earlier post, the following are just mechanisms for creating and publishing Structured Data on the Web:
1. RDF family of syntaxes -- RDF/XML, N3, Turtle, N-Triples, TriX, TriG, etc..
2. Non RDF family XML based syntaxes 3. JSON syntaxes 4. Others. Conflating Linked Data and Structured Data gets us nowhere.Schema.org is all about Structured Data, it isn't currently concerned about Linked Data fidelity re. URIs and Name/Address disambiguation.
I apologize for starting a new thread but i feel the discussion is very easily skewed by the fact that those who have time to answer often are the most prone to make rules as complicated as "it needed" and to accept them as such. But this is not the way the world goes. Or that anything that's meant to reach the world as large can be.
Nice discussion. It time will kill this problem off one and for all. Once again, all Linked Data is Structured Data. All Structured Data isn't Linked Data.
Linked Data is a specific approach to Structured Data with its own specific attributes.
Gio
-- Regards, Kingsley Idehen Founder& 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
