RE: Audience for Schema Bib extension

I agree that "Schema Bib extension" should focus on "search engines" as
the "audience". I especially like the POV that Bowker (and other
parties) presumably bring to the table that "books" (and other forms of
"manifestation") are identifiable products that bridge world views.
These overlaps will become even stronger if/when Schema.org is formally
integrated/mapped with GoodRelations.

 

I would suggest these mappings to bridge FRBR and Schema/GoodRelations:

 

frbr:Manifestation rdfs:subClassOf gr:SomeItems .

frbr:Item rdfs:subClassOf gr:Individual .

 

Jeff

 

From: Dawson, Laura [mailto:Laura.Dawson@bowker.com] 
Sent: Monday, November 05, 2012 5:02 PM
To: Kevin Ford
Cc: public-schemabibex@w3.org
Subject: Re: Audience for Schema Bib extension

 

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> wrote:





Dear All,

In the interest of moving this along, is it possible for us to identify
the audience for the 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 vocabulary should be modified for those additional consumers
and, perhaps more importantly, how/why the schema.org maintainers would
accept those recommendations if they do not benefit the 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