This issue serves to track Schema.org developments around the evolving bib: extension proposal.

See #699 for final review tracking. In particular #700 regarding "Agent"

At this point we do not have a well-polished proposal for reviewing hosted schema.org extensions, i.e. those that will show us as "bib.schema.org" or similar.

• Implement the new extensions model  #429 tracks implementation of Extensions mechanism itself (i.e. python code and HTML/CSS UI)
• https://lists.w3.org/Archives/Public/public-schemabibex/2015Apr/0000.html "An initial proposal for bib.schema.org" within BibExtend CG

Issues to discuss (we can break out sub-issues as needed)

• is Schema.org CG (and steering group) happy with the term names requested for the extension?
• is there a high level mission statement indicating broad coverage of the extension?
• does it propose terms that are candidates for direct inclusion for the schema.org core?
• have we made the most of the opportunity to collaborate with BibFrame? see bib.schema.org should try accomodate ideas from BibFrame #642
• ... other questions?

Draft: https://www.w3.org/community/schemabibex/wiki/Bib.schema.org-1.0

Summary of request terms (including revisions, issues)

(to be completed)

• Agent - Guha concerned about generality. proposed Agent type is controversial: identify the design options #700
• Chapter, now called BookChapter
• ...todo