Commit 64ae648b authored by mmarkus1's avatar mmarkus1
Browse files

release 1.1 public beta

parent 2a06b41a
This diff is collapsed.
This diff is collapsed.
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
schematypens="http://purl.oclc.org/dsdl/schematron"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0"
xmlns:xi="http://www.w3.org/2001/XInclude">
<teiHeader>
<fileDesc>
<titleStmt>
<title>LIDO v1.1 – Accompanying Document</title>
<author>Lindenthal, Jutta</author>
<author>Stein, Regine</author>
<author>Weidling, Michelle</author>
</titleStmt>
<publicationStmt>
<publisher>German LIDO Working Group</publisher>
<availability>
<p>Copyright 2020, German LIDO Working Group</p>
<licence target="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International (CC BY 4.0)</licence>
</availability>
</publicationStmt>
<sourceDesc>
<p>Born digital.</p>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<body>
<div xml:id="intro">
<head>LIDO v1.1 – Accompanying Document</head>
<!-- place the introductory text here. text can also be added after the listing below (e.g. a conclusion or some other
kind of outro). surround any new text block in tei:div elements. -->
<p>Here goes the text.</p>
</div>
<!-- This file imports the other accompanying documents via XInclude.
The serialization of this is handled during the serialization of the complete documentation. -->
<xi:include href="accompanying-document-terminology-recommendations" xpointer="terminology_recommendations"/>
</body>
</text>
</TEI>
This diff is collapsed.
This diff is collapsed.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:lido="http://www.lido-schema.org"
xmlns:lido-qa="http://www.lido-schema.org/quality-assurance"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:tei="http://www.tei-c.org/ns/1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xml="http://www.w3.org/XML/1998/namespace"
targetNamespace="http://www.lido-schema.org/quality-assurance" elementFormDefault="qualified"
attributeFormDefault="qualified">
<!--
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xx This is an additional schema for LIDO v1.1. It is to be understood as complementary tool for
xx assuring the quality of LIDO records. This means it is not obligatory to use this schema when
xx validating your files; some rules, however, will warn you about changes in the upcoming LIDO v2.0
xx which are not backwards compatible.
xx
xx This document implements the Schematron error roles as follows::
xx * "info": highlights elements which will be deprecated in the next LIDO version
xx * "warn": points out data values or elements that are correct according to the LIDO schema but
xx could/should be improved
xx
xx Prepared for CIDOC Working Group Data Harvesting and Interchange, CDWA Lite/museumdat Working Group,
xx Collections Trust and Deutscher Museumsbund - Fachgruppe Dokumentation by:
xx Michelle Weidling – Niedersaechsische Staats- und Universitaetsbiblithek Goettingen
xx
xx Copyright (c) 2020 ICOM-CIDOC for the Data Harvesting and Interchange Working Group.
xx These are licensed under the Creative Commens Attribution 4.0 International (CC BY 4.0) license.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-->
<xs:annotation>
<xs:appinfo>
<sch:ns uri="http://www.lido-schema.org" prefix="lido"/>
<sch:ns uri="http://www.w3.org/2002/07/owl#" prefix="owl"/>
<sch:ns uri="http://www.w3.org/2004/02/skos/core#" prefix="skos"/>
<sch:title>Abstract Schematron rules for quality assurance</sch:title>
<sch:pattern>
<sch:title>Deprecation Warning: Controlled vocabulary instead of free text</sch:title>
<sch:p>In upcoming versions of LIDO some element won't allow for free text anymore but will require terms
taken from a (local) controlled vocabulary. This should improve the interoperability of the data and recall rates
in aggregating web services.</sch:p>
<sch:rule abstract="true" id="sch_MixedContentInfo">
<sch:report
test="text()[matches(., '[\w]')]" role="info">
In upcoming versions of LIDO <sch:name/> will only allow for skos:Concept, lido:conceptID and lido:term as child elements.
The use of free text will be deprecated.
</sch:report>
</sch:rule>
</sch:pattern>
<sch:pattern>
<sch:title>@pref: Discern preferred and alternative elements</sch:title>
<sch:p>If there is more than one element holding a @pref, alternatives as well as the preferred element should be indicated.
This isn't stated clearly in the LIDO v1.0 schema documentation but should be kept in mind when indexing objects; otherwise the preferred
variant might be unclear to a data user. Also, omitting this attribute contradicts international best practices for retrieval quality.</sch:p>
<sch:rule abstract="true" id="sch_pref">
<sch:let name="current" value="current()"/>
<sch:let name="currentName" value="$current/name()"/>
<sch:let name="parent" value="$current/.."/>
<sch:let name="lang" value="$current/@xml:lang/string()"/>
<sch:let name="siblings" value="$parent/child::*[name(.) = $currentName and (@xml:lang/string() = $lang or not(@xml:lang or $current/@xml:lang))]"/>
<sch:report test="
count($siblings) gt 1 and
not($siblings/@lido:pref = 'preferred') and
not($siblings/@lido:pref = 'alternative' and $siblings/@lido:pref = 'alternate')"
role="warn">
When providing more than one <sch:name/> the preferred and alternative variant(s) should be cleary marked as such via @pref.
</sch:report>
</sch:rule>
</sch:pattern>
<sch:pattern>
<sch:title>@pref: "alternative" instead of "alternate"</sch:title>
<sch:p>LIDO v1.0 falsely suggests the value 'alternate' for the pref attribute. It is established to use 'alternative' in this context.</sch:p>
<sch:rule abstract="true" id="sch_alternate">
<sch:report test="@lido:pref = 'alternate'" role="warn">
It is established to use 'alternative' instead of 'alternate' in this context. Consider changing the attribute's value or using the corresponding
LIDO terminology, http://terminology.lido-schema.org/pref and http://terminology.lido-schema.org/alternative, instead.
</sch:report>
</sch:rule>
</sch:pattern>
<sch:pattern>
<sch:title>xs:dateTime Dates</sch:title>
<sch:p>Check if a given string complies to the ISO 8601 date convention. This pattern is used for
the cases where an element allows for xs:string in LIDO v1.0 while providing a date.</sch:p>
<sch:rule abstract="true" id="sch_DateTime">
<sch:assert role="warn" test="matches(., '-?[0-9]{4}-(0[1-9]|1[12])-([0][1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3])(:[0-5][0-9]){2}(Z|(\+|\-)(0[0-9]|1[12])(:[0-5][0-9])?)')">
The date provided in <sch:name/> should comply to the format [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm].
</sch:assert>
</sch:rule>
</sch:pattern>
<sch:pattern>
<sch:title>@lido:type for objectMeasurementsSetComplexType</sch:title>
<sch:p>Although the lido:type has been introduced for lido:objectMeasurementsSetComplexType, it should only be used for
lido:eventObjectMeasurementsSet in context of the EODEM application profile.</sch:p>
<sch:rule context="lido:objectMeasurementsSet" id="sch_objectMeasurementsSet">
<sch:assert role="warn" test="not(@lido:type)">
The only element of the complex type lido:objectMeasurementsSetComplexType holding @lido:type should be lido:eventObjectMeasurementsSet.
</sch:assert>
</sch:rule>
</sch:pattern>
<sch:pattern>
<sch:title>Avoid Providing Resource Measurements When Using IIIF</sch:title>
<sch:p>IIIF resources provide information about their measurements in their
info.json. Therefore it is redundant to also make the resource's measurements
available in lido:resourceMeasurementsSet.</sch:p>
<sch:rule context="lido:resourceRepresentation" id="sch_IIIF_Measurements">
<sch:assert role="warn"
test="
(@type = 'http://terminology.lido-schema.org/lido00911' or @type = 'http://terminology.lido-schema.org/lido00912')
and not(lido:resourceMeasurementsSet)"
> Do not set lido:resourceMeasurementsSet when providing a IIIF resource.
Resource measurements are available in the resource's info.json.
</sch:assert>
</sch:rule>
</sch:pattern>
</xs:appinfo>
</xs:annotation>
</xs:schema>
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
![LIDO logo](http://cidoc.mini.icom.museum/wp-content/uploads/sites/6/2018/12/LIDO_logo_main_240x153_bg-white_01.png "Title Text")
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.
LIDO is an XML schema intended for delivering metadata, for use in a variety of online services, from an organization’s collections database to portals of aggregated resources, as well as exposing, sharing and connecting data on the web. Its strength lies in its ability to support the typical range of descriptive information about objects of material culture. It can be used for all kinds of object, e.g. art, cultural, technology and natural science and supports multilingual portal environments.
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.
The LIDO schema is the result of a substantial redesign and enhancement of the CDWA Lite and museumdat schemas based on recommendations of the CDWA Lite/museumdat Working Group, community feedback and further CIDOC-CRM analysis. It includes additional concepts to meet SPECTRUM requirements.
For the full history of LIDO developments refer to [lido-schema.org/schema/v1.0/lido-v1.0-specification.pdf](http://www.lido-schema.org/schema/v1.0/lido-v1.0-specification.pdf), 2.3 History of the schema.
# 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/)
## Documentation
This repository contains all relevant files of the LIDO standard. The schema is described as an XML Schema Definition, the documentation and a terminology. The most recent version is **LIDO 1.1 Public Beta** and is available for download here:
- [**LIDO 1.1 Public Beta XML Schema Definition (XSD)**](http://www.lido-schema.org/schema/v1.1/lido-v1.1.xsd)
- [**LIDO 1.1 Public Beta XML Schema Definition (QA extended XSD)**](http://www.lido-schema.org/schema/v1.1/lido-v1.1.xsd) (This version extends the schema with Schematron rules to improve quality assurance)
- [**Online documentation (HTML)**](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html)
- [Printed documentation (PDF)](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.pdf)
- [Terminology (website)](http://terminology-view.lido-schema.org/)
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).
For more information please visit the [official LIDO website.](http://cidoc.mini.icom.museum/working-groups/lido/)
The LIDO Terminology is [**available online**](http://terminology-view.lido-schema.org/).
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)
## What's new in LIDO v1.1
# What's new in LIDO v1.1 Public Beta
For the development of LIDO v1.1 the following criteria for taking into account suggestions for changes and extensions have been defined:
......@@ -25,9 +28,9 @@ For the development of LIDO v1.1 the following criteria for taking into account
- 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
## General changes
#### Documentation
### Documentation
The schema docs are provided in a structured way as TEI elements as follows:
......@@ -43,20 +46,20 @@ 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.
#### Accompanying Documents
### 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**
#### Schematron
### Schematron
We introduced Schematron as a second quality assurance mechanism. This is e.g. used to ensure that dates comply to the xs:dateTime requirements.
While there are Schematron rules in the schema itself which we consider as essential for data quality, more quality assuring rules can be found in `lido-qa.xsd`. If you want these included in the validation, choose the schema `lido-v1.1.xsd`. If you do not want these to be included in the validation, choose the schema `lidov1.1-unrestricted.xsd`.
### New Elements (and Why They Have Been Introduced)
## 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.
......@@ -82,19 +85,19 @@ While there are Schematron rules in the schema itself which we consider as essen
- **vitalPlaceActor**: Allows for providing the birth/death/activity place of an actor.
### New Attributes (and Why They Have Been Introduced)
## 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.
- **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)
## 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.
- **rightsHolderComplexType**: Increases the schema's modularity. rightsHolder doesn't have to be defined fully twice.
### Changed Content Model: Mixed Content
## 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:
......@@ -111,12 +114,12 @@ The following elements can contain free text only in LIDO v.1.0, but can also pr
- scaleMeasurements
- shapeMeasurements
### Changed Descriptions
## Changed Descriptions
Definitions have generally been renamed to 'description'.
Almost all descriptions have been revised and specified for clarity.
### Other Changes
## Other Changes
The following elements can now hold additional attributes:
......@@ -130,7 +133,3 @@ 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
## 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