A small beginning towards building a conversion specification

Hi All,

Firstly my apologies for the lack of recent progress within the group.
Hopefully we can start to move things forward a little faster from now on.

To that end I have put some work in on the bibframe2schema.org site - the
certificate that supports https has been updated and is now part of an
auto-renew cycle.

I have also put some work in on the W3C Group site
<https://www.w3.org/community/bibframe2schema/>, specifically in the Wiki
<https://www.w3.org/community/bibframe2schema/wiki/Main_Page> area.
Apart from a few minor tweaks, I have started on a Conversion Specification
<https://www.w3.org/community/bibframe2schema/wiki/Conversion_Specification>
document as it is not ideal to have to infer specifications from SPARQL
query examples.

My intention is to create a specification for each of the main
Bibframe entity types, indicating how Schema Types and properties should be
produced from interpreting the pattern of BF properties and relationships.

This I have discovered is not a simple task - without things starting to
look like SPARQL queries!

I have therefore picked a single Bibframe type (bf:Instance) and produced a
trial specification, to hopefully start a discussion as to the
appropriateness of the form I have chosen.

What do others think? Am I missing a standard approach to this that
produces understandable results?

I deliberately chose bf:Instance for this example as it has some particular
challenges where Schema property values need to be derived from properties
of an instance's related Work.

Please contribute.  When we have consensus on the way to define the
specification, I will proceed to define examples for other types such as
Work, Organization, Person, Item, Event, Place, etc.

Regards,
  Richard



Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw