Re: How many extensions?

Excellent question Owen.

There are many ways to skin this particular cat.  There being two main considerations I believe.  Firstly, how would too much fragmentation effect how consumable/understandable Schema will be for those wishing to use it and refer to the documentation.  Secondly, how many interested groups could/will form to propose, manage, and promote those extensions.

I personally have always interpreted bibliographic, in this context, as broadly as possible.  Schema.org<http://Schema.org> being a general purpose vocabulary for describing things on the web - bib.schema.org<http://bib.schema.org> being the extension vocabulary for describing bibliographic things on the web.

In the same way that Schema (with our help) has laid the general foundation that we can build a bib extension upon, I would imagine that a bib extension would create the general bibliographic framework that others may further extend for specific areas, such as comics, archives etc.

I thus have little problem in considering initial proposals that spread quite widely from our initial core.

~Richard

On 17 Apr 2015, at 10:42, Shlomo Sanders <Shlomo.Sanders@exlibrisgroup.com<mailto:Shlomo.Sanders@exlibrisgroup.com>> wrote:

+1 as series of extensions

Thanks,
Shlomo

Sent from my iPad

On Apr 17, 2015, at 11:47, Owen Stephens <owen@ostephens.com<mailto:owen@ostephens.com>> wrote:

A question that has occurred to me during the discussion of the ‘bibliographic extension'. Is there any benefit/disadvantage in terms of how many extensions are added. For example are there benefits/disadvantages to proposing a ‘comics’ extension which is separate to a ‘books’ (or even ‘bib’) extension.

My guess is that the benefits of minimising the number of extensions relate to ease of managing/maintaining the extensions, but the disadvantages are around community input and cohesion.

Are we sure that a single ‘bib’ extension is what is needed, or would we be better served by breaking this down into a series of extensions?

Owen

Owen Stephens
Owen Stephens Consulting
Web: http://www.ostephens.com<http://www.ostephens.com/>
Email: owen@ostephens.com<mailto:owen@ostephens.com>
Telephone: 0121 288 6936

On 14 Apr 2015, at 22:26, Wallis,Richard <Richard.Wallis@oclc.org<mailto:Richard.Wallis@oclc.org>> wrote:

Hi all,

A few weeks back we discussed how this group or some of its members could participate as a bibliographic domain group to propose and review a bibliographic extension to schema.org<http://schema.org/> with the current working name of bib.schema.org<http://bib.schema.org/>.

Since then I have been liaising with Dan Brickley and others in the main Schema.org<http://schema.org/> group who have been working to establish the hosting software that enables the extension capability.  This work is now close to being ready for release.  Dan has indicated that this provides an excellent opportunity for a bibliographic extension to be one of, if not the first, enabled and released in this way.  In preparation for this, Dan Scott and I have put together a candidate set of types and properties that could constitute an initial bib extension release, which this email introduces.

There are many potential candidates for new/enhanced types and properties which the finessing and accepting of which would need to be the subject of some in depth discussion within this group.  To take advantage of the opportunity to release along with the capability release, however, we need to agree a starting subset fairly quickly.  To that end Dan and I have drawn up this initial (1.0) proposal consisting of what we believe to be things that are fairly noncontroversial.

I list the proposed types and properties below with links to their representation in a development version of the Schema.org<http://schema.org/> site.  They are in three independent groups of proposals, for general bibliographic markup; some helpful things for the physical structure of archives & basic collections; and for comics.

We can accept/reject either individual types and properties, or a whole group, because we need to explore things in more depth and defer things to a later release.  I would hope though that fairly quickly we could come to at least a subset of these as an initial release.

A reminder that Dan Brickley is still working on the software capable of handling extensions so please view the content more than how it currently displays.

General Bibliographic Types & Properties

  *   Agent<http://sdo-bib.appspot.com/Agent>
  *   Atlas<http://sdo-bib.appspot.com/Atlas>
  *   Chapter<http://sdo-bib.appspot.com/Chapter>
  *   Globe<http://sdo-bib.appspot.com/Globe>
  *   Kit<http://sdo-bib.appspot.com/Kit>
  *   Meeting<http://sdo-bib.appspot.com/Meeting>
  *   Newspaper<http://sdo-bib.appspot.com/Newspaper>
  *   MusicScore<http://sdo-bib.appspot.com/MusicScore>
  *   PublicationSeries<http://sdo-bib.appspot.com/PublicationSeries>
  *   Thesis<http://sdo-bib.appspot.com/Thesis>
  *   Toy<http://sdo-bib.appspot.com/Toy>
  *   BookFormatType:AudioBook<http://sdo-bib.appspot.com/AudioBook>
  *   BookFormatType:LargePrintBook<http://sdo-bib.appspot.com/LargePrintBook>
  *   BookFormatType:PrintBook<http://sdo-bib.appspot.com/PrintBook>
  *   MapCategoryType:CartographicMap<http://sdo-bib.appspot.com/CartographicMap>
  *   inSupportOf<http://sdo-bib.appspot.com/inSupportOf>
  *   translationOfWork<http://sdo-bib.appspot.com/translationOfWork>
  *   translator<http://sdo-bib.appspot.com/translator>
  *   workTranslation<http://sdo-bib.appspot.com/workTranslation>

Archive Containers/Collection

  *   BoxContainer<http://sdo-bib.appspot.com/BoxContainer>
  *   Collection<http://sdo-bib.appspot.com/Collection>
  *   Container<http://sdo-bib.appspot.com/Container>
  *   FolderContainer<http://sdo-bib.appspot.com/FolderContainer>
  *   Shelf<http://sdo-bib.appspot.com/Shelf>
  *   contains<http://sdo-bib.appspot.com/contains>
  *   containedIn<http://sdo-bib.appspot.com/containedIn>

Comics

  *   ComicIssue<http://sdo-bib.appspot.com/ComicIssue>
  *   ComicSeries<http://sdo-bib.appspot.com/ComicSeries>
  *   ComicStory<http://sdo-bib.appspot.com/ComicStory>
  *   CoverArt<http://sdo-bib.appspot.com/CoverArt>
  *   ComicCoverArt<http://sdo-bib.appspot.com/ComicCoverArt>
  *   BookFormatType:GraphicNovel<http://sdo-bib.appspot.com/GraphicNovel>
  *   artist<http://sdo-bib.appspot.com/artist>
  *   colorist<http://sdo-bib.appspot.com/colorist>
  *   inker<http://sdo-bib.appspot.com/inker>
  *   letterer<http://sdo-bib.appspot.com/letterer>
  *   penciler<http://sdo-bib.appspot.com/penciler>
  *   publisherImprint<http://sdo-bib.appspot.com/publisherImprint>
  *   variantCover<http://sdo-bib.appspot.com/variantCover>

I look forward to comments.

~Richard.