- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Fri, 4 Nov 2011 21:17:05 +0000
- To: Jason Douglas <jasondouglas@google.com>
- Cc: public-vocabs@w3.org, Guha <guha@google.com>, Dan Brickley <danbri@danbri.org>, HTML Data Task Force WG <public-html-data-tf@w3.org>
Jason, That's *really* helpful, thank you, especially around the rationale for the 'url' property. You suggest: On 4 Nov 2011, at 19:31, Jason Douglas wrote: > So to throw a strawman out there, maybe we could: > • State on schema.org that Thing/url is equivalent to itemid and either is accepted. If schema.org does this, it should also state what happens when both are specified and they clash. Perhaps they should be treated as aliases with the @itemid being the canonical URL? > • Add Thing/sameAs for stating item equivalences (via URLs) across data sources/sites. Nice, I can see the potential for that :) I'd love to know whether there are any consumers of schema.org markup that are or plan to aggregate data across different sites to create a view of information about the same thing, and indeed whether there are any publishers who are generating schema.org markup with common @itemids or urls... Jeni -- Jeni Tennison http://www.jenitennison.com
Received on Friday, 4 November 2011 21:17:32 UTC