search

SAA-SDT / eac-cpf-schema

https://eac.staatsbibliothek-berlin.de/
10 stars 4 forks source link

Disambiguate terms in <descriptiveNote> #270

Closed SJagodzinski closed 2 years ago

SJagodzinski commented 3 years ago

It should be possible to disambiguate terms in <descriptiveNote> with @vocabularySource, @vocabularySourceURI, @valueURI.

Creator of issue

  1. Gerhard Müller
  2. Staatsbibliothek zu Berlin

The issue relates to

Wanted change/feature

Add optional attributes @vocabularySource, @vocabularySourceURI, @valueURI to <descriptiveNote>.

Suggested Solution

example:

<descriptiveNote vocabularySource="GND Ontology" vocabularySourceURI="https://d-nb.info/standards/elementset/gnd" valueURI="https://d-nb.info/standards/elementset/gnd#EarlierNameOfThePerson">
    <term languageOfElement="en">Earlier name of the person</term>
    <term languageOfElement="de">Früherer Name der Person</term>
</descriptiveNote>

Context

Using vocabularies of an ontology to specify (in this case) the type of a name.

109 , #269

kerstarno commented 3 years ago

See my note on the general context of the suggested change in #269.

As for adding the vocabulary attributes to <descriptiveNote>, I would see this not being in line with the purpose of <descriptiveNote> as an element as well as not being in line with the purpose of the vocabulary attributes. If we wanted to follow the suggested change in #269, on which the change in this issue here builds, I'd rather think we should reconsider enabling the vocabulary attributes with <term>.

SJagodzinski commented 2 years ago

EAC-CPF meeting, 4 Nov 2021:

No change. Highlight in Tag Library that <descriptiveNote> is to be used for descriptive, not structured, content.