Commit 0a55b040 authored by mrodzis's avatar mrodzis 🌎
Browse files

feat: add @measurementsGroup

parent 3bc6858a
......@@ -3288,6 +3288,13 @@ target="
<xs:attribute name="measurementsGroup" type="xs:anyURI" id="measurementsGroup">
<tei:ab type="description">TODO</tei:ab>
<xs:complexType name="measurementsSetComplexType" id="measurementsSetComplexType">
......@@ -4120,6 +4127,7 @@ target="
<xs:attribute ref="lido:type"/>
<xs:attribute ref="lido:measurementsGroup"/>
<!-- Element hinzugefügt 2017-12-10 von Jutta Lindenthal -->
<xs:element name="objectMaterialsTechWrap" id="objectMaterialsTechWrap">
......@@ -64,6 +64,10 @@ For the development of LIDO v1.1 the following criteria for taking into account
**skos:Concept**: Introduced for all elements with a concept(Mixed)ComplexType. This enables acquisitors to make an LOD reference for a term via SKOS. SKOS has been implemented as xs:any and been restricted by Schematron. Link: <>
### New attributes (and why they have been introduced)
**measurementsGroup**: Indicates the group of measurements given in multiple LIDO Measurement Set elements. Of relevance for the EODEM application profile.
### Changed content model
The following elements can contain free text only in LIDO v.1.0, but can also provide controlled terms (e.g. from authoritative data) as an alternative via conceptComplexType in LIDO v1.1:
......@@ -85,4 +89,4 @@ Definitions have generally been renamed to 'description's since they aren't defi
### Other changes
* titleSet allows for lido:pref as attribute
\ No newline at end of file
* titleSet allows for lido:pref as attribute
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment