Open StefanDumont opened 7 years ago
Just to be picky: <date>
should be close with </date>
not </event>
;-)
Thx, corrected! :-)
To sum up my thoughts on this issue from last week's SIG meeting: generally I'm wary of extending the CMIF in ways that allow for the inclusion of relatively ancillary information. In this case, particularly <bibl>
, <name>
and <date>
will only be used by a small fraction of data contributors. This will introduce a bias to the retrieval, i.e. coverage of and thus search results from these fields will be incomplete without the user noticing it. Therefore I would restrict CMIF to only the data fields that are absolutely necessary.
See current propsal on CMIF v2: https://encoding-correspondence.bbaw.de/v1/CMIF.html (please note the annotation function via Hypothes.is)
Edited copy from "Perspectives of the further development of the Correspondence Metadata Interchange Format"
Without doubt it is useful to indicate the persons, places, publications etc. mentioned in a letter text. In a printed edition these information will be usually provided in the various indexes. In the CMIF this could be encoded in
correspDesc/note
:Instead of using the element
event
, as proposed in the mentioned article, it could be better to usedate
, just because it is TEI conform (perhaps with an attribute@type="event"
).Even for the mentioned “entities”, the use of authority controlled IDs is necessary in an interchange format. Thus we should only consider to include those entities in the metadata record, for which authority files are available, i.e. persons, places and publications. Other entities such as objects and topics could also be provided in principle as long as authority files or standardized vocabularies exist, which we can refer to. One problem is, that publications have often multiple editions and therefore multiple URIs in Authority Files.