Dear all,
In order to make an informed decision about each of the mappings proposed
by Bernard [1], I think it is necessary to look closely at the details. To do this,
I created a wiki page with the declarations of the properties and classes to
be mapped, in prefixed NTriples format, at [2].
It took two hours or so to put together that page, and the cutting-and-pasting
process seems inherently prone to error. I see it as a strawman mock-up of the
information one would want to be able to pull together automatically, in support
of an ongoing routine of creating and reviewing mappings. A quick wish list:
-- Software that identifies candidates for possible alignment.
-- For each candidate alignment, extract basic information about the property
or class from the published schemas -- e.g., type, definition, domain, range,
any other relevant annotations, date last revised.
-- For each domain or range class related to a candidate term for alignment, a
formal definition.
-- Presentation in a "readable" format suitable for publication.
-- Periodic refresh of the information, to be presented side-by-side with the
information used to decide on an alignment.
-- Ideally, "diff"-driven flagging of terms whose formal definition has changed,
so that related alignments can be flagged for review.
Tom
[1] http://wiki.dublincore.org/index.php/Schema.org_Alignment/Mappings
[2] http://wiki.dublincore.org/index.php/Schema.org_Alignment/Mappings_Details
--
Tom Baker <[log in to unmask]>
|