Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace bibo properties and types #108

Closed
acka47 opened this issue Sep 22, 2016 · 7 comments
Closed

Replace bibo properties and types #108

acka47 opened this issue Sep 22, 2016 · 7 comments
Assignees

Comments

@acka47
Copy link
Contributor

acka47 commented Sep 22, 2016

bibo URIs don't resolve anymore, see e.g. http://purl.org/ontology/bibo/Book or http://purl.org/ontology/bibo/isbn. The website http://bibliontology.com/ currently has problem with links. There is another website at http://bibliographic-ontology.org/. I have my doubts about the future of bibo though a new human-readable interface might actually come, see structureddynamics/Bibliographic-Ontology-BIBO#10 (comment).

Nonetheless, we should try to replace bibo which we especially use for properties. Will look into RDA and Bibframe.

@acka47 acka47 assigned acka47 and unassigned acka47 Sep 22, 2016
@acka47 acka47 added the ready label Sep 22, 2016
@acka47 acka47 self-assigned this Sep 22, 2016
@acka47
Copy link
Contributor Author

acka47 commented Sep 30, 2016

The vocabulary URI now redirects to the new domain, see https://groups.google.com/forum/#!topic/bibliographic-ontology-specification-group/7WTE6VhyhMo. Class and property URIs still don't resolve.

@acka47 acka47 added working and removed ready labels Oct 6, 2016
@acka47
Copy link
Contributor Author

acka47 commented Oct 6, 2016

Here are the bibo properties and classes from the JSON-LD context:

    "doi" : {
      "@id" : "http://purl.org/ontology/bibo/doi",
      "@container" : "@set"
    },
    "edition" : {
      "@id" : "http://purl.org/ontology/bibo/edition",
      "@container" : "@set"
    },
    "editor" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/editor",
      "@container" : "@set"
    },
    "eissn" : {
      "@id" : "http://purl.org/ontology/bibo/eissn",
      "@container" : "@set"
    },
    "isbn" : {
      "@id" : "http://purl.org/ontology/bibo/isbn",
      "@container" : "@set"
    },
    "issn" : {
      "@id" : "http://purl.org/ontology/bibo/issn",
      "@container" : "@set"
    },
    "lccn" : {
      "@id" : "http://purl.org/ontology/bibo/lccn",
      "@container" : "@set"
    },
    "oclcnum" : {
      "@id" : "http://purl.org/ontology/bibo/oclcnum",
      "@container" : "@set"
    },
    "shortTitle" : {
      "@id" : "http://purl.org/ontology/bibo/shortTitle",
      "@container" : "@set"
    },
    "translator" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/translator",
      "@container" : "@set"
    },
    "volume" : {
      "@id" : "http://purl.org/ontology/bibo/volume",
      "@container" : "@set"
    },
    "Article" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Article",
      "@container" : "@set"
    },
    "Book" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Book",
      "@container" : "@set"
    },
    "Collection" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Collection",
      "@container" : "@set"
    },
    "Journal" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Journal",
      "@container" : "@set"
    },
    "MultiVolumeBook" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/MultiVolumeBook",
      "@container" : "@set"
    },
    "Newspaper" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Newspaper",
      "@container" : "@set"
    },
    "Periodical" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Periodical",
      "@container" : "@set"
    },
    "Proceedings" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Proceedings",
      "@container" : "@set"
    },
    "ReferenceSource" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/ReferenceSource",
      "@container" : "@set"
    },
    "Report" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Report",
      "@container" : "@set"
    },
    "Series" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Series",
      "@container" : "@set"
    },
    "Thesis" : {
      "@type" : "@id",
      "@id" : "http://purl.org/ontology/bibo/Thesis",
      "@container" : "@set"
    },

@acka47
Copy link
Contributor Author

acka47 commented Oct 6, 2016

I started an overview at https://github.com/hbz/lobid-resources/wiki/Changes-in-API-2.0#replace-bibo-properties-and-classes. Bibframe seems to be good to cover the properties. Regarding the types, I will think of a re-modeling together with the "medium" information. Related to hbz/lobid#266 and #115.

@acka47 acka47 added ready and removed working labels Oct 25, 2016
@acka47
Copy link
Contributor Author

acka47 commented Nov 9, 2016

It might make sense to use Bibframe 2.0 where possible. To investigate further I will make Bibframe-based versions of the examples from #79.

@acka47 acka47 added working and removed ready labels Dec 1, 2016
@acka47
Copy link
Contributor Author

acka47 commented Dec 7, 2016

Here are some thoughts I had around switching to Bibframe 2.0 as base vocabulary for lobid:

  1. We should settle on a base vocabulary before the API is officially launched.
  2. Bibo property/class URIs actually dereference to http://bibliographic-ontology.org/bibo/bibo.php where the ontology as RDF/XML is found. This is not ideal, especially the file extension but at least people can get to the ontology.
  3. I represent hbz/lobid in a group that actually proposes recommendations for publishing bibliographic data using bibo (amongst others).
  4. Bibframe 2.0 isn't a good candidate yet to switch to. There are neither tools nor good examples for Bibframe 2.0 published and won't be until the beginning of 2017.

However, for now, I will proceed and finally work on the examples I talked about four weeks ago.

@acka47 acka47 added ready and removed working labels Dec 9, 2016
@acka47
Copy link
Contributor Author

acka47 commented Dec 9, 2016

I tried different variants on going through all properties and types to see what vocabulary options we have. The best way seems to be to comment the context file as it contains all classes and properties used (but not the medium values, will also have to check this.) I did this in an hjson file, see https://gist.github.com/acka47/74f24ec7a23a152f30575d64fb23fa44. I would like to put this somewhere in this repo. Where is the best place? Shall I just put it in the root directory? What do you think, @dr0i?

@acka47
Copy link
Contributor Author

acka47 commented Dec 9, 2016

As we don't want to replace bibo anymore and my evaluation is going in a more general direction, this has become a duplicate of #5 . Closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant