search

SAA-SDT / eac-cpf-schema

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

@unit #255

Closed SJagodzinski closed 2 years ago

SJagodzinski commented 3 years ago

Unit

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. silkejagodzinski@gmail.com

Related issues / documents

Topic: Assertion description in EAS

EAD3 Reconciliation

Summary: The type of measurement used to calculate the value provided in <dimensions>. Data Type: token

Context

new EAC attribute

Solution documentation:

Summary needed

May occur within: <citedRange> Data tpye: token

Example encoding

<citedRange unit="pagenumber">p. 1</citedRange>
ailie-s commented 3 years ago

Tag Library Text:

Summary: Use @unit to document the format or unit that is specified in <citedRange>, for example page number ("pagenumber") or volume number ("volumenumber)". Data Type: token

kerstarno commented 3 years ago

Tested as part of Schema Team's schema testing:

The above applies to both schemas, RNG and XSD.

The attribute is ready.

kerstarno commented 3 years ago

@ailie-s Wondering, if example values that we provide with the TL should also follow the camelCase approach, i.e. "pageNumber" and "volumeNumber"? Especially here, where "page number" and "volume number" would be equally valid.

fordmadox commented 3 years ago

I'd suggest just using values like "page" or "volume".

Here are the examples from the TEI documentation, although we do not have the ability to use those "from" and "to" attributes:

<citedRange>pp 12–13</citedRange>
<citedRange unit="page" from="12" to="13"/>
<citedRange unit="volume">II</citedRange>
<citedRange unit="page">12</citedRange>