- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sat, 12 Apr 2014 09:43:42 -0400
- To: public-vocabs@w3.org
- Message-ID: <5349430E.5000100@openlinksw.com>
On 4/11/14 7:50 PM, Aaron Bradley wrote: > I think Thad typifies the difference between the "regular web" and the > "social web" (and it is indeed an important one for marketers) well > when he says: > > > The difference between the 2 is that one has the context of "allows a > communication pathway to an Organization or Person"...versus those > that are not constructed to really have communication to a > Organization or Person". > > Or - as I might have mentioned before - the "regular web" references > resources /about/ an entity, whereas the social web references > resources that emanate /from/ an entity. It is simpler, really. The Web provides foundation for many kinds of network abstractions [1][2][3]. Each of this abstractions is fundamentally driven by denotation relations. > In regard to the referenced entity the former is passive, the latter > active (or at least potentially so) - it's the difference between a > third and person narrative. > > Is the Wikipedia page /about /Monsanto in the same category as the > Twitter account run /by/ Monsanto? I sure don't think so, and I think > that its useful for data consumers to be able to distinguish between > these two classes of identifiers when returning information about the > entity in question. It just about which abstraction you are working with. We only get into trouble when we mangle the abstractions :-) BTW -- Dan's example provide good foundation for understanding the matters. It provides a bridge solution that ultimately aids in understanding important lines of demarcation. For instance, the role of a *pronoun* in natural language is subtle but powerful. Sticking with Dan's example, here are some additional relation name suggestions, as alternatives to anything with "sameAs" in it: 1. describedBy -- your Twitter Home page Identifies you since its comprised of a Description of you 2. profileAt -- your Twitter home page is a document at a location denoted by its HTTP(S) URL 3. hasProfileDoc -- variant of the above. The above are in addition to: 1. identifiedBy 2. referencedBy 3. subjectOf . All of these make Dan's example a little clearer, as alternatives to "sameAs" . Again, there is a subtlety in Dan's example that really needs to be picked up, it solves a major headache re. bridging the world of: 1. structured data 2. linked data 3. semantically enhanced linked data. Links: [1] http://bit.ly/1cjYwqN -- Internet abstraction (driven by DNS names for computers (actually their NICS) re. entity denotation and scope) [2] http://bit.ly/1e0pwdI -- Linked Document (or World Wide Web 1.0) abstraction (driven by HTTP names for Web Documents) [3] http://bit.ly/INv6ag -- Linked Data (or Data Web) abstraction driven by HTTP names for anything [4] http://bit.ly/1lHD31h -- Semantic Web abstraction (driven by names for anything combined with machine comprehensible relation semantics) > > > On Fri, Apr 11, 2014 at 1:58 PM, Kingsley Idehen > <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote: > > On 4/11/14 4:06 PM, Jarno van Driel wrote: >> Being a non-illuminati I think simple. The description of sameAs >> mentions about the item's identity. Now for me my 'identity' >> isn't defined by a Youtube channel where I share random stuff I >> like on the web. I am no @VideoGallery, I'm me, a real life >> person and not a collection of videos. > Dan's example in HTML+Microdata (which by notation choice > **inadvertently** blurs visibility of the relation semantics in > play) : > > <div itemscope itemtype="http://schema.org/Person" > <http://schema.org/Person>> > <span itemprop="name">Stephen Fry</span> > (<a itemprop="url" href="http://www.stephenfry.com/" > <http://www.stephenfry.com/>>stephenfry.com > <http://stephenfry.com></a>, > <a itemprop="sameAs" href="http://twitter.com/stephenfry" > <http://twitter.com/stephenfry>>twitter</a>, > <a itemprop="sameAs" > href="http://en.wikipedia.org/wiki/Stephen_Fry" > <http://en.wikipedia.org/wiki/Stephen_Fry>>wikipedia</a>) > </div> > > > Turtle translation: > > <> <http://www.w3.org/ns/md#item> <http://www.w3.org/ns/md#item> [ > <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> > <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> > <http://schema.org/Person> <http://schema.org/Person>; > <http://schema.org/name> <http://schema.org/name> "Stephen Fry"; > <http://schema.org/sameAs> <http://schema.org/sameAs> > <http://twitter.com/stephenfry> <http://twitter.com/stephenfry>, > <http://en.wikipedia.org/wiki/Stephen_Fry> > <http://en.wikipedia.org/wiki/Stephen_Fry>; > <http://schema.org/url> <http://schema.org/url> > <http://www.stephenfry.com/> <http://www.stephenfry.com/> > ]; > <http://www.w3.org/ns/rdfa#usesVocabulary> > <http://www.w3.org/ns/rdfa#usesVocabulary> <http://schema.org/> > <http://schema.org/> . > > > What does Dan's example demonstrate? > > The function of a **pronoun** in a sentence or statement. > Basically, the example makes the following claim, using terms from > <http://schema.org/> <http://schema.org/> (a Vocabulary): > > Someone or something has determined the existence of an entity > that has the following discernible attributes: > Name: "Stephen Fry" > Type: Person > referencedBy: <http://twitter.com/stephenfry> > <http://twitter.com/stephenfry>, <http://twitter.com/stephenfry> > <http://twitter.com/stephenfry>, <http://www.stephenfry.com/> > <http://www.stephenfry.com/> . > > Personally, I wouldn't denote a relationship predicate/property > for this relation, in this manner, due to the **equivalence** > intuition. Alternatives inclued: > > 1. referencedBy > 2. subjectOf > 3. identifiedBy -- this is my personal favorite . > > > -- > > Regards, > > Kingsley Idehen > Founder & CEO > OpenLink Software > Company Web:http://www.openlinksw.com > Personal Weblog:http://www.openlinksw.com/blog/~kidehen <http://www.openlinksw.com/blog/%7Ekidehen> > Twitter Profile:https://twitter.com/kidehen > Google+ Profile:https://plus.google.com/+KingsleyIdehen/about > LinkedIn Profile:http://www.linkedin.com/in/kidehen > > > > > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Saturday, 12 April 2014 13:44:04 UTC