- From: Aaron Bradley <aaranged@gmail.com>
- Date: Fri, 24 Jan 2014 09:27:23 -0800
- To: David Deering <david@touchpointdigital.net>
- Cc: Thad Guidry <thadguidry@gmail.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>
- Message-ID: <CAMbipBs-LK0E=owyFK1Jh8NqRkDi71H+wdMRqCneiDExw9XUdg@mail.gmail.com>
+1 to this general idea, to David's fashioning this as an "Account" (or perhaps "OnlineAccount") rather than "SocialAccount", and to Thad's thought that this should be separated from "sameAs". Property-wise this need not be verbose, but I think "url" in itself is inadequate. In structuring account data for a person or organization supporting - aside from the properties inherited from Thing - something like "id" would be useful, to indicate the account holder's social network handle or exposed login name (and perhaps a property supporting the declaration of the entity to which the account belonged?). And simply having this as a separate itemtype would be useful, as a single individual or (more often) organization can have multiple accounts on the same network. E.g.: <div itemscope itemtype="http://schema.org/Organization"> <h1 itemprop="name">Acme News Service</h1> <p>Twitter accounts</p> <p itemprop="account" itemscope itemtype="http://schema.org/Account"> <a href="http://twitter.com/acmebreaking" itemprop="url"><span itemprop="id">@AcmeBreaking</span></a> - <span itemprop="name">Acme Breaking News</span> <span></p> <p itemprop="account" itemscope itemtype="http://schema.org/Account"> <a href="http://twitter.com/acmecom" itemprop="url"><span itemprop="id">@AcmeCom</span></a> - <span itemprop="name">Acme Indepth Commentary</span> <span></p> </div> On Fri, Jan 24, 2014 at 8:56 AM, David Deering <david@touchpointdigital.net>wrote: > I see. Thanks, Thad. Up until this point, I have been using the > "sameAs" property to link to other pages, but I wasn't sure if there was a > better way to define things for search engines. No problem, that method > works for me. Thanks. > > David > > > > On 1/24/2014 10:46 AM, Thad Guidry wrote: > > David, > > We already have your needs fulfilled with the property "sameAs" on > http://schema.org/LocalBusiness or even just > http://schema.org/Organization ... just use that and it works today. > This proposal for "Account" is for representing Account identities > sometimes represented as a url and not "__Pages__ that are created for > AccountHolders or that represent them topically on a page" as I understand > it. > > -- > -Thad > +ThadGuidry <https://www.google.com/+ThadGuidry> > Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/> > > On Fri, Jan 24, 2014 at 10:37 AM, David Deering < > david@touchpointdigital.net> wrote: > >> I've been listening to the conversation and have been debating with >> something myself. I'd like to see a way in which business listings and >> business profile pages could also be distinguished through Schemas. >> Particularly, I'm referring to a business' listing on sites such as Yelp, >> Angie's List, YP.com, Foursquare, Infogroup, Acxiom, Factual, Nokia, >> CitySearch, and even listings such as Google+ Local, Bing Places, and Yahoo >> Local. Whereas a Google+ Local or Business/Brand page could be considered >> a social account, I don't believe that the others could. >> >> So I'm not sure if SocialAccount would fit those applications, and I'm >> also not sure if Account would be too general or vague. Maybe >> BusinessListing, BusinessPage, ProfilePage, or even Page would be a better >> suited type for those pages, I don't know. So I'm just throwing that >> out there to get everyone's thoughts. Thanks. >> >> David >> >> >> > >
Received on Friday, 24 January 2014 17:27:51 UTC