- From: Dawson, Laura <Laura.Dawson@bowker.com>
- Date: Mon, 5 Nov 2012 17:02:03 -0500
- To: Kevin Ford <kefo@3windmills.com>
- CC: "public-schemabibex@w3.org" <public-schemabibex@w3.org>
- Message-ID: <2C597ABF-243B-42BC-8BD4-ED23BBC99285@bowker.com>
I think search engines is a great scope, simply because that is where end-users go to look for information about things - information that should include at the very LEAST listings for books. Even if we keep it to that scope to start, we're getting at the heart of the problem. Once we get this figured out for the search engines involved in Schema, we can then use what we've learned for additional consumers. On Nov 5, 2012, at 4:34 PM, Kevin Ford <kefo@3windmills.com<mailto:kefo@3windmills.com>> wrote: Dear All, In the interest of moving this along, is it possible for us to identify the audience for the schema.org<http://schema.org> bibliographic extension? Personally, I think it is rather simple: search engines generally, but primarily Google, Yahoo!, and Bing. I'm not against other consumers (those that are not search engines) but I would like to know why/how the schema.org<http://schema.org> vocabulary should be modified for those additional consumers and, perhaps more importantly, how/why the schema.org<http://schema.org> maintainers would accept those recommendations if they do not benefit the schema.org<http://schema.org> designers. I suspect a justification will have to be made for the extension to find approval. Is this assumption correct? In any event, I think that clearly identifying the audience for this extension would help us focus not only the use cases but also the resulting extension recommendation. Yours, Kevin -- Kevin Ford Network Development and MARC Standards Office Library of Congress Washington, DC Laura Dawson Product Manager, Identifiers Bowker 908-219-0082 917-770-6641 laura.dawson@bowker.com<mailto:laura.dawson@bowker.com>
Received on Monday, 5 November 2012 22:02:16 UTC