Skip to content

Don't use relators as property but indicate relator via "role" property #38

Closed
@acka47

Description

@acka47

As discussed in #10 , we will indicate the roles of a contributor in the contributor object with the "role" property and won't use relators as properties.

Example:

{
  "@context": {
    "id": "@id",
    "type": "@type",
    "role": "http://bibframe.org/vocab/relator",
    "contributor": {
      "@type": "@id",
      "@id": "http://purl.org/dc/terms/contributor",
      "@container": "@set"
    },
    "label": "http://www.w3.org/2000/01/rdf-schema#label",
    "altLabel": "http://www.w3.org/2004/02/skos/core#altLabel",
    "subject": {
      "@type": "@id",
      "@id": "http://purl.org/dc/terms/subject",
      "@container": "@list"
    }
  },
  "@id" : "http://lobid.org/resources/HT018843259#!",
  "contributor": [ {
    "id": "http://d-nb.info/gnd/118548018",
    "type": "DifferentiatedPerson",
    "role": {
      "id": "http://id.loc.gov/vocabulary/relators/cre",
      "label": "Autor/in"
    },
    "label": "Becker, Thomas Paul",
    "altLabel": [ "Becker, Thomas P." ]
  } ],
  "subject": [ {
     "id" : "http://d-nb.info/gnd/4031485-6",
     "type": "PlaceOrGeographicName",
     "label": "Erzstift Köln",
     "altLabel": [ "Kölner Krieg", "Truchsessischer Krieg" ]
  } ]
}

We won't be able to only use a string as value for "role" as proposed in #10 but will – as you can see in the example – also use the side car approach here – giving us presentation labels for the different roles in the data.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions