W3C home > Mailing lists > Public > public-vocabs@w3.org > April 2014

Re: Socialnetworks of a person or organization

From: Simon Spero <sesuncedu@gmail.com>
Date: Sun, 13 Apr 2014 22:33:15 -0400
Message-ID: <CADE8KM6QoCFiLwQmABtgC7WV3UDatb6OioB_OikeFSvB4RzkZg@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: W3C Web Schemas Task Force <public-vocabs@w3.org>
On Sun, Apr 13, 2014 at 8:39 PM, Kingsley Idehen <kidehen@openlinksw.com>wrote:

> Why? Because "identity" oriented relations infer (as per this case) that a
> sign signifies something. "sameAs" relations assert equivalence. "You" are
> not the same as the sign that signifies "You" .  You are != "Thad Guidry"
> that's a literal identifier that "signifies" or "denotes" the entity "You"
> i.e., the entity "You" is "denoted" or "signified" by the the literal sign
> "Thad Guidry" .

Using an #$IndexicalConcept possibly makes the example more complicated
than necessary, but you are right on  point.

The definition of schema:sameAs states that it specifies the  "URL of a
reference Web page that unambiguously indicates the item's identity".

This means that if any two subjects x and y have the same URL as a value of
schema:sameAs, then x and y are absolutely

Vocabulary is Cheap.

schema.org implictly  #$genlpreds any property whose name contains a "/" to
a property whose name consists of all characters prior to the final "/".

There is an existing property, schema:url, that can be used to associate a
URL with a schema:Thing.
A url for a socialMediaAccount could use property
<schema:url/socialMediaAccountPage> .
A google_plus URL could be <schema:url/socialMediaAccountPage/google_plus>

On the downside, this would be backwards compatible with
schema.orgapplications that only understood schema:url.

This seems far simpler than requiring only one entity to ever be associated
with a social media account, ever (under sameAs, if the founder of a
company started off using the corporate account as his only account, then
hired someone else to run social media, using schema:sameAs would require
the old account be abandoned.

Alternatively Service and ServiceChannel objects could be created, allowing
for serviceURL to be used.

[If schema:purpose  wasn't so specific, and Service's weren't constrained
to producing tangible things, one could specify that the purpose of the
Service was to produce an instance of a schema:CommunicationAction. ]

Received on Monday, 14 April 2014 02:33:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:39 UTC