Re: Proposal for extension mechanism

Getting back to the merits of the proposal itself….

Although there are some details that would need to be worked out, I think there is the basis here for an elegant solution to sector specific needs that build upon, yet do not dilute, the value of the core<> vocabulary.

Some of those details that would contribute to the success of this approach are, however, in the hands of the search engines.

We know that Google et al are understandably reticent to share insights into what they do and don’t recognise in data they harvest, yet some indication of what they would do with something defined in one of these extension vocabularies would contribute significantly to the adoption of such extensions.

For example what would they do, or intend to do in the future, with a<>, or with a<> property associated with a<>

Would they:

  *   Ignore them both
  *   Recognise them both for what they describe
  *   At least recognise the Microform as an instance of CreativeWork (which it is a subtype of)
  *   ?


On 17 Feb 2015, at 14:23, Kingsley Idehen <<>> wrote:

On 2/17/15 6:04 AM, Wallis,Richard wrote:
On 15 Feb 2015, at 14:14, Dan Brickley <<>> wrote:

Could you help by providing some more realistic examples of cases
where a description mixes core<> terms with those from

Below are a few examples of live data from OCLC’s<> containing some<> terms mixed with core<>, plus a few other bits and pieces.  I’ve provided extracts, and include links to the full descriptions, in turtle.  (if you prefer other flavours, swap the .ttl suffix for .nt, .rdf, .jsonld, or remove it for the html/rdfa version)


        a                           schema:Book ;
        rdfs:label                  "Daxiong zai mo jie da mao xian" ;
        bgn:translationOfWork       <> ;
        schema:about                <> , <> ;
        schema:bookEdition          "Chu ban." ;
        schema:contributor          <> ;
        schema:creator              <> ;
        schema:datePublished        "2006" ;
        schema:description          "「大雄在魔界大冒險」是動畫電影的原著。這次的舞臺是以大雄創造出來的魔法世界為背景。但這個異次元世界與現實世界卻只有一線之隔。在這裡, 大雄與哆啦A夢等人同心協力一起對抗地球所面臨的危機。" ;
        schema:exampleOfWork        <> ;

bgn:Thesis, bgn:inSupportOf

        a                     schema:CreativeWork , bgn:Thesis , schema:Book , pto:Web_document ;
        bgn:inSupportOf       "Thesis / Dissertation ETD" ;
        library:oclcnum       "725508408" ;
        schema:about          <> , <<sseldorf><> , <> , <> ;
        schema:creator        <> ;
        schema:datePublished  "2009” ;


        a                           bgn:MusicScore ;
        library:oclcnum             11222068 ;
        library:placeOfPublication  <> , <> ;
        schema:about                <> , <> ;
        schema:copyrightYear        "1963" ;
        schema:creator              <> ;
        schema:datePublished        "1963" ;
        schema:exampleOfWork        <> ;
        schema:inLanguage           "zxx" ;
        schema:name                 "Twilight crane = fantasy for woodwind quintet = Yuzuru" ;
        schema:publication          <> ;
        schema:publisher            <> ;
        wdrs:describedby            <> .

These few examples are from a set of 300+ million bibliographic descriptions in<>, with links to some 200 million Work descriptions derived from the same source.  As a work in progress there are still a few issues to resolve both in vocabulary and data terms.  However they are an effective live demonstration of using<> as a core vocabulary and extending it with<> - the pattern being proposed for<>.



Please lookup the URL:

Note the object of the <><> relation, it's currently "schema:URL" instead of <><> .


Kingsley Idehen
Founder & CEO
OpenLink Software
Company Web:<>
Personal Weblog 1:<>
Personal Weblog 2:

Twitter Profile:

Google+ Profile:

LinkedIn Profile:

Personal WebID:

Received on Wednesday, 18 February 2015 17:00:52 UTC