- From: Breslin, John <john.breslin@nuigalway.ie>
- Date: Tue, 8 Jan 2013 23:28:50 +0000
- To: "Alex Milowski" <alex@milowski.com>, "Aaron Bradley" <aaranged@gmail.com>
- Cc: "Public Vocabs" <public-vocabs@w3.org>
- Message-ID: <78782529-8410-4D17-A09A-6FEED4204738@nuigalway.ie>
Actually this picture is a perhaps better :-) http://www.johnbreslin.com/sites/johnbreslin.com/files/uploads/2008/01/20080104b.png John http://bresl.in On 8 Jan 2013, at 23:23, "Breslin, John" <john.breslin@nuigalway.ie> wrote: > Hi Alex, Aaron - > > This picture from SIOC may also help: > > http://sioc-project.org/node/158 > > UserAccount is a subtype of OnlineAccount ( http://sioc-project.org/ontology#term_UserAccount ) > > Through multiple UserAccounts we had a Person creating content. Sometimes the Person is unknown so a UserAccount is all you have. > > In schema.org it'd be good to replicate some FOAF's accountServiceHomepage so generic services like WordPress or XenForo could be avoided. In SIOC the content items are connected to containers and those to sites / services but the serviceUrl is more elegant. > > HTH, > > John > http://bresl.in > > On 8 Jan 2013, at 23:08, "Aaron Bradley" <aaranged@gmail.com> wrote: > >> It's long struck me that schema.org would benefit by incorporating elements of FOAF OnlineAccount type [1] (FOAF being something with which one person closely associated with this list has more than a passing acquaintance:). >> >> That is, something like an "account" property for http://schema.org/Person and http://schema.org/Organization (and more specific types), where an expected type would include something like "OnlineAccount." >> >> So where we see in FOAF something like this: >> >> <foaf:Person> >> <foaf:name>Dan Brickley</foaf:name> >> <foaf:account> >> <foaf:OnlineAccount> >> <rdf:type rdf:resource="http://xmlns.com/foaf/0.1/OnlineChatAccount"/> >> <foaf:accountServiceHomepage >> rdf:resource="http://www.freenode.net/"/> >> <foaf:accountName>danbri</foaf:accountName> >> </foaf:OnlineAccount> >> </foaf:account> >> </foaf:Person> >> >> In schema.org we might see something like this (obviously not exactly equivalent): >> >> <div itemscope itemtype="http://schema.org/Person"> >> <span itemprop="name">Dan Brickley</span> >> <div itemprop="account" itemscope itemtype="http://schema.org/OnlineAccount"> >> <span itemprop="accountType">Twitter</span>: >> <a itemprop="url" href="https://twitter.com/danbri"><span itemprop="accountName">danbri</span></a> >> </div> >> </div> >> >> Food for thought, I hope? >> >> [1] http://xmlns.com/foaf/spec/#term_OnlineAccount >> >> >> On Tue, Jan 8, 2013 at 2:24 PM, Alex Milowski <alex@milowski.com> wrote: >>> I've been perusing the Person [1] type looking for how to encode a >>> person's set of alias/accounts on particular web services (e.g. >>> twitter, linkedin, etc.) and I don't see a good property to use for >>> such affiliated services. Did I miss something? >>> >>> What I would prefer is a new type for a web service for that identifies: >>> >>> * the alias/username >>> * the service type (probably by URI) >>> >>> I could imagine a simple Type of WebService that extends Thing (or >>> possibly Intangible). >>> >>> Then the name, url, etc. properties can be used to describe the >>> service. I would add an 'alias' or 'username' property (I prefer >>> 'alias') to represent the user's account on the service. >>> >>> Finally, I would add a 'webService' property to Person of type 'WebService'. >>> >>> >>> [1] http://www.schema.org/Person >>> >>> -- >>> --Alex Milowski >>> "The excellence of grammar as a guide is proportional to the paucity of the >>> inflexions, i.e. to the degree of analysis effected by the language >>> considered." >>> >>> Bertrand Russell in a footnote of Principles of Mathematics >> >> >> >> -- >> Resistance is futile: I have been assimilated. Into the Google world that is. Accordingly, my default email address is now aaranged@gmail.com. If I'm in your address book as aaranged@yahoo.com you may want to update that detail (but Yahoo! mail will continue to be forwarded to this account).
Received on Tuesday, 8 January 2013 23:29:24 UTC