<p>Data values for the <reftarget="http://schema.lido-schema.org/#relatedWorkRelType">Related Work Relationship Type</ref> element.
Recommended: LIDO Terminology. Please select a concept from the LIDO Concept Scheme
<reftarget="http://terminology.lido-schema.org/relatedWorkRelType">Related Work Relationship Type</ref>.
</p>
</div>
<divxml:id="repositorySet_type">
<p>Data values for the type attribute of the LIDO <reftarget="http://schema.lido-schema.org/#repositorySet">Custody/Repository Location Set</ref> element.
Recommended: LIDO Terminology. Please select a concept from the LIDO Concept Scheme
<reftarget="http://terminology.lido-schema.org/repositorySet_type">Custody/Repository Location Set type</ref>.
</p>
</div>
<divxml:id="resourceRepresentation_type">
<p>Data values for the type attribute of the LIDO <reftarget="http://schema.lido-schema.org/#resourceRepresentation">Resource Representation</ref> element.
Recommended: LIDO Terminology. Please select a concept from the LIDO Concept Scheme
@@ -8,7 +8,7 @@ Experimental Draft version of proposed elements/attributes to address issues wit
### General
The schema is developed at https://gitlab.gwdg.de/lido/development. The most recent draft version can be found at https://gitlab.gwdg.de/lido/development/-/blob/develop/1.1/lido-v1.1-draft.xsd.
The schema is developed at <https://gitlab.gwdg.de/lido/development>. The most recent draft version can be found at <https://gitlab.gwdg.de/lido/development/-/blob/develop/1.1/lido-v1.1-draft.xsd>.
For the development of LIDO v1.1 the following criteria for taking into account suggestions for changes and extensions have been defined:
...
...
@@ -19,69 +19,74 @@ For the development of LIDO v1.1 the following criteria for taking into account
### General changes
*The schema and the docs are provided in a single XSD document from which different outputs (HTML, PDF, parsed-down XSD [TBD]) are serialized.
*The schema docs are provided in a structured way as TEI elements as follows:
- the element description
- the element's label
- elements from other schemas to which the respective LIDO element is equivalent
- a note where a user can find more context about the element (this often refers to CDWA FULL, as LIDO elements are largely based on LIDO's predecessor CDWA Lite)
- recommended data values for controlled terms
- cross-links between LIDO elements
- though provided in the docs, the following aspect will not be serialized in the PDF and HTML: 'How to record', 'Notes' (both outdated and largely merged into the element description), CIDOC CRM equivalents (not compiled yet)
*We introduced Schematron as a second quality assurance mechanism. This is e.g. used to ensure that dates comply to the xs:dateTime requirements.
*Added the TEI header into the schema. *This solution is tentative, and the header is yet to be updated.*
*Each LIDO element/complexType/attribute is now referenceable by an ID. This ID is (in most cases) identical to its name and comes in handy for developing application profiles.
* The schema and the docs are provided in a single XSD document from which different outputs (HTML, PDF, parsed-down XSD [TBD]) are serialized.
* The schema docs are provided in a structured way as TEI elements as follows:
* the element description
* the element's label
* elements from other schemas to which the respective LIDO element is equivalent
* a note where a user can find more context about the element (this often refers to CDWA FULL, as LIDO elements are largely based on LIDO's predecessor CDWA Lite)