Re: Socialnetworks of a person or organization

Kingsley:
My main point is that the theroretically nice abstractions that form the basis for the Linked Data Paradigm (entity vs. representation of a description etc.) are not necessary and not appropriate for schema.org.

As you know from www.productontology.org, I know quite exactly what I am talking of (it has all the best practices built in), but

- they were very complex to implement
- they are practically useless (99% of www.productontology.org users just need an URI for indicating a type of product)
- the HTTP content negotiation between the document URIs and the entity URIs alone consumes 98 % of all server resources and costs me ca. 1000 EUR / year for no actual benefit.

I am planning to flatten the implementation in www.productontology.org so that there will be just one URI for the page and the type entity, essentially removing all linked data stuff in the near future.

Best wishes / Mit freundlichen Grüßen

Martin Hepp

-------------------------------------------------------
martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

e-mail:  martin.hepp@unibw.de
phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www:     http://www.unibw.de/ebusiness/ (group)
         http://www.heppnetz.de/ (personal)
skype:   mfhepp 
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!
=================================================================
* Project Main Page: http://purl.org/goodrelations/




On 10 Apr 2014, at 16:15, Kingsley Idehen <kidehen@openlinksw.com> wrote:

> 
> Conclusion:
> 
> The basis have been covered for a long time re., DBpedia. I don't see what applying "application/json+schema" or "text/plain" on all resources brings to the table, bar ambiguity and the resultant out-of-band processing which is antithetical to the fundamental goals of Linked Open Data.

Received on Friday, 11 April 2014 07:11:14 UTC