ivoa / bibvo Goto Github PK

About the biblink terms, the usual convention in the web-semantics world is to have:

• capitalised terms for classes ;
• camel-case with lower case first letter for properties.

Hence, I would propose to rename the terms as:

• BibRef (class)
• DatasetRef (class)
• Relationship (class)
• bibFormat (property)
• anchorText (property)
• cardinality (property)
• cites (property)
• isSupplementedBy (property)

There seems to be a discrepancy between the content of the biblinks.json file and the info page:

E.g:
http://dc.zah.uni-heidelberg.de/__system__/biblinks/links/info

The keys of the JSON are using _ (underscore) instead of - (dash). This is a minor issue, but it should be fixed.

As a preliminary statement, I'm totally for finding a way to advertise bibliographic links as known from the data provider, for articles older than the data citation/DOI era. I also agree that we can provide links to contribute even if the data DOIs are already cited in the published articles, since many editors are not exposing the paper-to-data relations in their DOI metadata.

This said, I would like to be able to be more interoperable with any linked-data enabled service, rather than having our own JSON specification.

Hence I propose to have several option for the biblink-harvest endpoint data, including at least: JSON-LD and RDF Turtle. With the example provided in section 3.1, here is what it could look like (using #3 proposed terms):

JSON_LD

{
   "@context": "http://ivoa.net/rdf/biblink#",
   "@graph": [ 
   {
      "@id": "2020A&A...637A...4R",
      "@type: "Bib-Ref",
      "bib-format": "bibcode",
      "isSupplementedBy": {
         "@id": "https://dc.g-vo.org/LP/org.gavo.dc/toss/q/line_tap",
         "@type": "Dataset-Ref"
   }, {
      "@id": "2012A&A...546A..55R",
      "@type: "Bib-Ref",
      "bib-format": "bibcode",
      "isSupplementedBy": {
         "@id": "https://dc.g-vo.org/LP/org.gavo.dc/toss/q/line_tap",
         "@type": "Dataset-Ref"
   }
}

RDF/Turtle

@prefix : <http://ivoa.net/rdf/biblink#> .

<2020A&A...637A...4R> a :Bib-Ref ; 
   :bib-format "bibcode" ; 
   :isSupplementedBy [
      <https://dc.g-vo.org/LP/org.gavo.dc/toss/q/line_tap> a :Dataset-Ref ] .

<2012A&A...546A..55R> a :Bib-Ref ; 
   :bib-format "bibcode" ;
   :isSupplementedBy [ 
      <https://dc.g-vo.org/LP/org.gavo.dc/toss/q/line_tap> a :Dataset-Ref ] .

NB: the proposed JSON-LD and RDF/Turtle might have issues since I didn't fully checked their syntax, but this is the idea. And of course a biblink vocabulary should be place at http://ivoa.net/rdf/biblink#

That corresponds to what DaCHS does like this: http://docs.g-vo.org/DaCHS/ref.html#per-publication-locally-aggregated-biblinks -- and we should probably use the lswscans/res/positions resource used there in bibVO, too.