Commit c2503897 authored by mmarkus1's avatar mmarkus1
Browse files

update readme

parent 021b67bb
# LIDO version 1.1
![LIDO logo](http://cidoc.mini.icom.museum/wp-content/uploads/sites/6/2018/12/LIDO_logo_main_240x153_bg-white_01.png "Title Text")
## What's new in LIDO v1.1
LIDO is an XML harvesting schema. The schema is intended for delivering metadata, for use in a variety of online services, from an organization’s online collections database to portals of aggregated resources, as well as exposing, sharing and connecting data on the web. It is not intended to be used as a basis for a collection management system or to support loan and acquisition activities.
The strength of LIDO lies in its ability to support the full range of descriptive information about museum objects. It can be used for all kinds of object, e.g. art, architecture, cultural history, history of technology, and natural history.
LIDO supports multilingual portal environments. It does this by having a language attribute that can be associated with each element, or more generally, with the group of descriptive elements for fully multilingual resources.
# Get Started
This repository contains all relevant files of the LIDO standard. The schema is developed as an XML Schema Definition. The most recent version is **LIDO 1.1 public beta** and is [**available for download here (XSD)**](http://www.lido-schema.org/schema/v1.1/lido-v1.1.xsd). For more information please visit the [official LIDO website.](http://cidoc.mini.icom.museum/working-groups/lido/)
### General
## Documentation
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.xsd>.
The LIDO schema is described as an XML Schema Definition and a Terminology. The full documentation is [**available online**](http://www.lido-schema.org/schema/v1.1/lido-v1.1.html) and for [download](http://www.lido-schema.org/schema/v1.1/lido-v1.1.pdf).
The LIDO Terminology is [**available online**](http://terminology-view.lido-schema.org/).
## What's new in LIDO v1.1
For the development of LIDO v1.1 the following criteria for taking into account suggestions for changes and extensions have been defined:
- The suggestion requires modification of the schema, e.g. there is no way to express the information in the LIDO v1.0 schema.
- The suggestion is based upon a known use case from practical LIDO applications.
- The requirement is generic and in the scope of LIDO v1.0.
- The suggestion can be implemented in a backwards compatible way with LIDO v1.0.
- The suggestion requires modification of the schema, e.g. there is no way to express the information in the LIDO v1.0 schema.
- The suggestion is based upon a known use case from practical LIDO applications.
- The requirement is generic and in the scope of LIDO v1.0.
- The suggestion can be implemented in a backwards compatible way with LIDO v1.0.
### General changes
......@@ -19,24 +31,24 @@ For the development of LIDO v1.1 the following criteria for taking into account
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
- the following docs have been removed: 'How to record', 'Notes' (both outdated and largely merged into the element description)
- 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
- the following docs have been removed: 'How to record', 'Notes' (both outdated and largely merged into the element description)
Furthermore, the following additions have been made:
- machine-readable metadata is provided in a TEI header.
- 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.
- machine-readable metadata is provided in a TEI header.
- 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.
#### Accompanying Documents
Apart from the documentation elements there are accompanying documents providing further information on LIDO elements:
- a **metadata crosswalk** provides a mapping of LIDOv1.1 elements to LIDOv1.0, CDWA Lite, museumdat, and Spectrum. CIDOC-CRM equivalents are provided in `metadata-crosswalk.xml`, but are not serialized because they are not complete yet.
- **links for further information** and **terminology recommendations**
- a **metadata crosswalk** provides a mapping of LIDOv1.1 elements to LIDOv1.0, CDWA Lite, museumdat, and Spectrum. CIDOC-CRM equivalents are provided in `metadata-crosswalk.xml`, but are not serialized because they are not complete yet.
- **links for further information** and **terminology recommendations**
#### Schematron
......@@ -46,58 +58,58 @@ While there are Schematron rules in the schema itself which we consider as essen
### New Elements (and Why They Have Been Introduced)
- **applicationProfile**: Serves as an identifier for a LIDO application profile which has been developed by an institution or project.
- **applicationProfile**: Serves as an identifier for a LIDO application profile which has been developed by an institution or project.
- **conceptElementsSet**: Increases the schema's modularity.
- **conceptElementsSet**: Increases the schema's modularity.
- **displayRelatedWork**: A display element displayRelatedWork for the relatedWorkSet allows for transferring specific relationship information for presentation purposes while for the actual relationship type element (lido:relatedWorkRelType) terms from the LIDO Terminology should be used.
- **displayRelatedWork**: A display element displayRelatedWork for the relatedWorkSet allows for transferring specific relationship information for presentation purposes while for the actual relationship type element (lido:relatedWorkRelType) terms from the LIDO Terminology should be used.
- **displayRepository**: A free-text description for designation of the institution of custody and, possibly, a descriptive indication of the exact location of the object while for repositoryName and repositoryLocation authorities should be used.
- **displayRepository**: A free-text description for designation of the institution of custody and, possibly, a descriptive indication of the exact location of the object while for repositoryName and repositoryLocation authorities should be used.
- **eventObjectMeasurements**: Indicates the dimensions or other measurements of the object/work as determined with respect to the described event, for instance a part addition or removal.
- **eventObjectMeasurements**: Indicates the dimensions or other measurements of the object/work as determined with respect to the described event, for instance a part addition or removal.
- **objectDescriptionRights**: Allows for setting separate rights information for the object description.
- **objectDescriptionRights**: Allows for setting separate rights information for the object description.
- **objectMaterialsTechSet/objectMaterialsTechWrap**: Allows for materials/technique information (meant like a physical characteristic of the object) outside of events.
- **objectMaterialsTechSet/objectMaterialsTechWrap**: Allows for materials/technique information (meant like a physical characteristic of the object) outside of events.
- **sourceActorInRole**: Allows for providing source information about an actor in a certain role.
- **sourceActorInRole**: Allows for providing source information about an actor in a certain role.
- **sourceRelatedWorkSet**: Allows for providing source information about a related work.
- **sourceRelatedWorkSet**: Allows for providing source information about a related work.
- **sourceRepositorySet**: Allows for providing source information about a current or former repository.
- **sourceRepositorySet**: Allows for providing source information about a current or former repository.
- **textAttributesSet**: Increases the schema's modularity.
- **textAttributesSet**: Increases the schema's modularity.
- **vitalPlaceActor**: Allows for providing the birth/death/activity place of an actor.
- **vitalPlaceActor**: Allows for providing the birth/death/activity place of an actor.
### 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.
- **measurementsGroup**: Indicates the group of measurements given in multiple LIDO Measurement Set elements. Of relevance for the EODEM application profile.
- **mostNotableEvent**: Qualifies an eventSet as the most notable or significant event as designated by the describing institution.
- **mostNotableEvent**: Qualifies an eventSet as the most notable or significant event as designated by the describing institution.
### New Complex Types (and Why They Have Been Introduced)
- **conceptMixedComplexType**: A complexType allowing both free text and the elements defined in conceptElementsSet. This complexType is used for elements that only allowed free text in LIDO v1.0 but should be controllable with conceptID(s) and term(s) in LIDO v1.1.
- **conceptMixedComplexType**: A complexType allowing both free text and the elements defined in conceptElementsSet. This complexType is used for elements that only allowed free text in LIDO v1.0 but should be controllable with conceptID(s) and term(s) in LIDO v1.1.
- **rightsHolderComplexType**: Increases the schema's modularity. rightsHolder doesn't have to be defined fully twice.
- **rightsHolderComplexType**: Increases the schema's modularity. rightsHolder doesn't have to be defined fully twice.
### Changed Content Model: Mixed Content
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:
- attributionQualifierActor
- extentActor
- extentMaterialsTech
- extentMeasurements
- extentSubject
- formatMeasurements
- genderActor
- measurementType
- measurementUnit
- qualifierMeasurements
- scaleMeasurements
- shapeMeasurements
- attributionQualifierActor
- extentActor
- extentMaterialsTech
- extentMeasurements
- extentSubject
- formatMeasurements
- genderActor
- measurementType
- measurementUnit
- qualifierMeasurements
- scaleMeasurements
- shapeMeasurements
### Changed Descriptions
......@@ -108,13 +120,17 @@ Almost all descriptions have been revised and specified for clarity.
The following elements can now hold additional attributes:
- genderActor allows for lido:type as attribute
- objectMeasurementsSetComplexType allows for lido:type as attribute
- rightsType allows for lido:type as attribute
- titleSet allows for lido:pref as attribute
- vitalDatesActor allows for lido:type as attribute
- genderActor allows for lido:type as attribute
- objectMeasurementsSetComplexType allows for lido:type as attribute
- rightsType allows for lido:type as attribute
- titleSet allows for lido:pref as attribute
- vitalDatesActor allows for lido:type as attribute
The following other changes have been made:
- <http://schemas.opengis.net/gml/3.1.1/base/gml.xsd> is now in use for GML validation
- instead of defining objectClassificationWrap, classificationWrap, and objectWorkTypeWrap twice, a reference has been introduced
- <http://schemas.opengis.net/gml/3.1.1/base/gml.xsd> is now in use for GML validation
- instead of defining objectClassificationWrap, classificationWrap, and objectWorkTypeWrap twice, a reference has been introduced
## Previous versions of LIDO
- LIDO 1.0 is still available online. [XML Schema Definition](http://www.lido-schema.org/schema/v1.0/lido-v1.0.xsd) - [Documentation online](http://www.lido-schema.org/schema/v1.0/lido-v1.0-schema-listing.html) and for [download](http://www.lido-schema.org/schema/v1.0/lido-v1.0-specification.pdf)
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