diff --git a/docs/xml/index.md b/docs/xml/index.md
index 82b4885..4a1dd19 100644
--- a/docs/xml/index.md
+++ b/docs/xml/index.md
@@ -37,7 +37,7 @@ Bibliographic citation
This document provides guidelines for implementing application schemas based on [Darwin Core terms](../../terms/) using [XML](http://www.w3.org/XML/). The underlying metadata model is described (in a syntax neutral way), followed by some specific guidelines for XML implementations. Some guidance on the use of non-Darwin Core terms is also provided.
-This document does not provide guidelines for encoding Darwin Core in RDF/XML. Nor does it take a position on the relative merits of encoding metadata in "plain" XML rather than RDF/XML. This document provides guidelines in those cases where RDF/XML is not considered appropriate. For information about implementing Darwin Core as RDF, see the Darwin Core RDF Guide, .
+This document does not provide guidelines for encoding Darwin Core in RDF/XML. Nor does it take a position on the relative merits of encoding metadata in "plain" XML rather than RDF/XML. This document provides guidelines in those cases where RDF/XML is not considered appropriate.
### 1.1 Status of the content of this document
@@ -59,22 +59,21 @@ Implementors SHOULD base their XML applications on [XML Schemas](http://www.w3.o
### 2.2 XML namespaces
-Implementors SHOULD use [XML Namespaces](http://www.w3.org/TR/1999/REC-xml-names-19990114/) to uniquely identify elements. Darwin Core namespaces are defined in the [Darwin Core Namespace Policy](../../namespace/), while Dublin Core namespaces are defined in the [DCMI Namespace Recommendation](http://dublincore.org/documents/dcmi-namespace/).
+Implementors MUST use [XML Namespaces](http://www.w3.org/TR/1999/REC-xml-names-19990114/) to uniquely identify elements. Darwin Core namespaces are defined in the [Darwin Core Namespace Policy](../../namespace/), while Dublin Core namespaces are defined in the [DCMI Namespace Recommendation](http://dublincore.org/documents/dcmi-namespace/).
### 2.3 Abstract model
The Darwin Core follows the [Dublin Core Metadata Initiative Abstract Model](http://dublincore.org/documents/abstract-model/) except that the Darwin Core _record_ is roughly equivalent to the Dublin Core _resource_.
-- Darwin Core terms are either `classes` or `properties`.
-- Each `property` has at most one `class` as its domain (describes no more than one `class`).
-- A `Darwin Core record` is made up of zero or more `classes` and one or more `properties` with their associated `values`.
-- Each `value` is a literal string.
+- Darwin Core terms MUST be either `classes` or `properties`.
+- A `Darwin Core record` MUST be made up of zero or more `classes` and one or more `properties` with their associated `values`.
+- Each `value` MUST be a literal string.
- The `values` of `properties` within a `Darwin Core record` describe that record.
- A `Darwin Core record` MUST include all required `properties`, if any, and their associated `values`.
### 2.4 Properties and values
-Darwin Core follows the guidelines for expressing [Dublin Core metadata using XML](http://dublincore.org/documents/dc-xml/) except in that Darwin Core implementors MUST encode `properties` as XML elements and `values` as the content of those elements instead of having each property contain a value representation and its associated value. The name of the XML element SHOULD be an XML qualified name (QName), which associates the value given in the `Term name` attribute in the [Darwin Core Terms](../../terms/) recommendation with the appropriate namespace name. For example, use:
+Darwin Core follows the guidelines for expressing [Dublin Core metadata using XML](http://dublincore.org/documents/dc-xml/) except in that Darwin Core implementors MUST encode `properties` as XML elements and `values` as the content of those elements instead of having each property contain a value representation and its associated value. The name of the XML element MUST be an XML qualified name (QName), which associates the value given in the `Term name` attribute in the [Darwin Core Terms](../../terms/) recommendation with the appropriate namespace name. For example, use:
```xml
```
-Implementers MUST NOT use an empty string - an element with no content:
+An empty string - an element with no content - MUST NOT be used:
```xml
@@ -106,235 +105,230 @@ Implementers MUST NOT use an empty string - an element with no content:
### 2.6 Simple Darwin Core
-[Simple Darwin Core](tdwg_dwc_simple.xsd) most closely models the "flat" nature of many data sets. It is a ready-made schema for sharing information with no structure beyond properties of a _record_ (equivalent to fields in a table, or columns in a spreadsheet). It is meant to accommodate all properties except those that require further structure to be meaningful (auxilliary terms in the classes [ResourceRelationship](http://rs.tdwg.org/dwc/terms/ResourceRelationship) and [MeasurementOrFact](http://rs.tdwg.org/dwc/terms/MeasurementOrFact). The schema has no required terms and terms SHOULD NOT be repeated within a given _record_. Refer to [Simple Darwin Core](../simple/) for the rationale behind this schema.
+[Simple Darwin Core](tdwg_dwc_simple.xsd) most closely models the "flat" nature of many data sets. It is a ready-made schema for sharing information with no structure beyond properties of a _record_ (equivalent to fields in a table, or columns in a spreadsheet). It is meant to accommodate all properties except those that require further structure to be meaningful (auxilliary terms in the classes [ResourceRelationship](http://rs.tdwg.org/dwc/terms/ResourceRelationship), [MeasurementOrFact](http://rs.tdwg.org/dwc/terms/MeasurementOrFact), and [ChronometricAge](http://rs.tdwg.org/chrono/terms/ChronometricAge). The schema has no required terms and no term is repeated within a given _record_. Refer to [Simple Darwin Core](../simple/) for the rationale behind this schema.
-The term [`dcterms:type`](http://rs.tdwg.org/dwc/terms/dcterms:type) (which is controlled by the [Dublin Core Type Vocabulary](http://dublincore.org/documents/dcmi-type-vocabulary/)), gives the basic category of object (`PhysicalObject`, `StillImage`, `MovingImage`, `Sound`, `Text`) the record is about. The term [`basisOfRecord`](http://rs.tdwg.org/dwc/terms/basisOfRecord), which has a controlled vocabulary distinct from that of `dcterms:type`, shows the name of the Darwin Core class (e.g., [`LivingSpecimen`](http://rs.tdwg.org/dwc/terms/LivingSpecimen), [`PreservedSpecimen`](http://rs.tdwg.org/dwc/terms/PreservedSpecimen), [`FossilSpecimen`](http://rs.tdwg.org/dwc/terms/FossilSpecimen), [`HumanObservation`](http://rs.tdwg.org/dwc/terms/HumanObservation), [`MachineObservation`](http://rs.tdwg.org/dwc/terms/MachineObservation), [`Taxon`](http://rs.tdwg.org/dwc/terms/Taxon)) the record is about.
+The term [`dcterms:type`](http://rs.tdwg.org/dwc/terms/dcterms:type) (which is controlled by the [Dublin Core Type Vocabulary](http://dublincore.org/documents/dcmi-type-vocabulary/)), gives the basic category of object (`PhysicalObject`, `StillImage`, `MovingImage`, `Sound`, `Text`) the record is about. The term [`basisOfRecord`](http://rs.tdwg.org/dwc/terms/basisOfRecord), which has a controlled vocabulary distinct from that of `dcterms:type`, shows the name of the Darwin Core class (e.g., [`LivingSpecimen`](http://rs.tdwg.org/dwc/terms/LivingSpecimen), [`PreservedSpecimen`](http://rs.tdwg.org/dwc/terms/PreservedSpecimen), [`FossilSpecimen`](http://rs.tdwg.org/dwc/terms/FossilSpecimen), [`MaterialCitation`](http://rs.tdwg.org/dwc/terms/MaterialCitation), [`HumanObservation`](http://rs.tdwg.org/dwc/terms/HumanObservation), [`MachineObservation`](http://rs.tdwg.org/dwc/terms/MachineObservation), [`Taxon`](http://rs.tdwg.org/dwc/terms/Taxon)) the record is about.
#### 2.6.1 Simple Darwin Core example (non-normative)
-Following is a brief example of an XML document for a single specimen complying with the [Simple Darwin Core Schema](tdwg_dwc_simple.xsd)]. The [Simple Darwin Core XML example document](example_simple.xml) (if this link shows a blank page in your browser, use the View Source option to see the XML document) shows detail for a single record having a more complete set of elements.
+Following is a brief example of an XML document for a single specimen complying with the [Simple Darwin Core Schema](tdwg_dwc_simple.xsd)].
```xml
- PhysicalObject
+ PhysicalObject
2009-02-12T12:43:31
- Museum of Vertebrate Zoology
- Creative Commons License
- MVZ
- Mammals
- urn:catalog:MVZ:Mammals:14523
+ en
+ Regents of the University of California
+ http://creativecommons.org/publicdomain/zero/1.0/legalcode
PreservedSpecimen
- Argentina
- AR
- Neuquén
- 25 km al NNE de Bariloche por Ruta 40 (=237)
+ MVZ
+ Mammal specimens
+ MVZ:Mamm:14523
+ male
+ http://arctos.database.museum/guid/MVZ:Mamm:14523?seid=770093
+ United States
+ US
+ California
+ Kern County
+ 8 mi NE Bakersfield
+ 35.45038
+ -118.9092
+ epdg:4267
+ 13696
+ 1911-05-14
+
```
### 2.7 Classes and containment
-Many Darwin Core terms (`properties`) are defined as being associated with another term (a `class`). For example, [`scientificName`](http://rs.tdwg.org/dwc/terms/scientificName) and [`Taxon`](http://rs.tdwg.org/dwc/terms/Taxon) are both Darwin Core terms, but `scientificName` is a property associated with the `Taxon` class. When constructing schemas that take advantage of classes in structures, implementors are encouraged to maintain the property/class relationships defined by the terms whenever possible (refer to the `Class` attribute of the term as given in the [Quick Reference Guide](../../terms/) or the attribute `dwcattributes:organizedInClass` in the term declaration in the [`dcterms.rdf`](../rdf/dcterms.rdf) file. To promote reuse, Darwin Core provides a set of xml schemas to use as the basis of additional schemas:
+Many Darwin Core terms (`properties`) are defined as being associated with another term (a `class`). For example, [`scientificName`](http://rs.tdwg.org/dwc/terms/scientificName) and [`Taxon`](http://rs.tdwg.org/dwc/terms/Taxon) are both Darwin Core terms, but `scientificName` is a property organized within the `Taxon` class. When constructing schemas that take advantage of classes in structures, implementors SHOULD maintain the property/class organization for the terms whenever possible (refer to the grouping of the term within a class in the [Quick Reference Guide](../../terms/). To promote reuse, Darwin Core provides a set of xml schemas to use as the basis of additional schemas:
- [Terms XML Schema](tdwg_dwcterms.xsd) - property term definitions as typed global elements and named groups for all terms for a given class to be referenced. The schema makes use of substitution groups `anyClass`, `anyProperty`, `anyIdentifier` and `anyXYZTerm` for each class, e.g. `anyTaxonTerm`. This is the schema upon which the [Simple Darwin Core XML Schema](tdwg_dwc_simple.xsd) is based.
- [Class Terms XML Schema](tdwg_dwc_class_terms.xsd) - class term definitions as typed global elements with subelements referencing all corresponding property terms via their substitution group.
-It is RECOMMENDED to use classes in a normalized way to avoid deep nesting. A [Darwin Core Tools and Applications page](https://github.com/tdwg/dwc-documentation/blob/master/documentation/resources.md) has been created as an index to example schemas for the purpose of community discussions and development. An [XML schema](tdwg_dwc_classes.xsd) is provided to freely mix any Darwin Core Class in a global list and allow them to reference each other using the respective class identifier terms.
+Classes SHOULD be used in a normalized way to avoid deep nesting. An [XML schema](tdwg_dwc_classes.xsd) is provided to freely mix any Darwin Core Class in a global list and allow them to reference each other using the respective class identifier terms.
#### 2.7.1 Normalized classes examples (non-normative)
-Following is an example of using normalized classes to represent two related specimen occurrences (one of which has had a second identification) at one location following this class-based schema. Note that you can reuse the location definition here by referring to it via locationID:
+Following is an example of using a normalized class-based schema to represent two related specimen occurrences from one Event. In this example a Western garter snake collected by Gordon W Gullion in 1949 was found to have eaten a Coastal giant salamander. Note the reuse of class instances by referring to the identifiers declared in the instances of those classes:
```xml
-
-
-
- http://guid.mvz.org/sites/arg/127
- Argentina
- AR
- Neuquén
- 25 km al NNE de Bariloche por Ruta 40 (=237)
-
-
- PhysicalObject
- 2009-02-12T12:43:31
- MVZ
- Mammals
- urn:catalog:MVZ:Mammals:14523
- PreservedSpecimen
- http://guid.mvz.org/sites/arg/127
-
-
- http://guid.mvz.org/identifications/23459
- Richard Sage
- 2000
- sp.
- urn:catalog:MVZ:Mammals:14523
- urn:lsid:catalogueoflife.org:taxon:d79c11aa-29c1-102b-9a4a-00304854f820:col20120721
-
-
- urn:lsid:catalogueoflife.org:taxon:d79c11aa-29c1-102b-9a4a-00304854f820:col20120721
- Ctenomys
- genus
- ICZN
- Ctenomys
-
-
- http://guid.mvz.org/identifications/94752
- James L Patton
- 2001-09-14
- urn:catalog:MVZ:Mammals:14523
- urn:lsid:catalogueoflife.org:taxon:df0a797c-29c1-102b-9a4a-00304854f820:col20120721
-
-
- urn:lsid:catalogueoflife.org:taxon:df0a797c-29c1-102b-9a4a-00304854f820:col20120721
- urn:lsid:catalogueoflife.org:taxon:d79c11aa-29c1-102b-9a4a-00304854f820:col20120721
- Ctenomys sociabilis
- Pearson and Christie, 1985
- species
- ICZN
- Animalia; Chordata; Vertebrata; Mammalia; Theria; Eutheria; Rodentia; Hystricognatha; Hystricognathi; Ctenomyidae; Ctenomyini; Ctenomys
- Animalia
- Chordata
- Mammalia
- Rodentia
- Ctenomyidae
- Ctenomys
- sociabilis
-
-
- PhysicalObject
- 2009-02-12T12:43:31
- MVZ
- Mammals
- urn:catalog:MVZ:Mammals:14524
- PreservedSpecimen
- http://guid.mvz.org/sites/arg/127
-
-
- http://guid.mvz.org/identifications/94753
- James L Patton
- 2001-09-14
- urn:catalog:MVZ:Mammals:14524
- urn:lsid:catalogueoflife.org:taxon:df0a797c-29c1-102b-9a4a-00304854f820:col20120721
-
-
- http://guid.mvz.org/relations/23423
- urn:catalog:MVZ:Mammals:14523
- urn:catalog:MVZ:Mammals:14524
- offspring of
-
-
- http://guid.mvz.org/relations/23424
- urn:catalog:MVZ:Mammals:14524
- urn:catalog:MVZ:Mammals:14523
- mother of
-
-
-```
+
+
+
+ http://arctos.database.museum/guid/MVZ:Herp:51568?seid=525813
+ PhysicalObject
+ PreservedSpecimen
+ MVZ
+ Amphibian and reptile specimens
+ MVZ:Herp:51568
+ Gordon W. Gullion
+ http://arctos.database.museum/guid/MVZ:Herp:51568
+ 525813
+ http://arctos.database.museum/MediaSearch.cfm?collection_object_id=10513964
+ "had stomach contents":"http://arctos.database.museum/guid/MVZ:Herp:51500?seid=670405"
+
+
+ http://arctos.database.museum/guid/MVZ:Herp:51568
+ multicellular organism
+ "ate":"http://arctos.database.museum/guid/MVZ:Herp:51500"
+
+
+ 525813
+ 1949-09-02
+ 2 Sep 1949
+ https://arctos.database.museum/place.cfm?action=detail&locality_id=10754971
+
+
+ https://arctos.database.museum/place.cfm?action=detail&locality_id=10754971
+ United States
+ US
+ California
+ Humboldt County
+ Raccoon Creek, 3 mi N Willow Creek
+
+
+ Museum of Vertebrate Zoology, University of California, Berkeley
+ 1999-01-27
+ http://arctos.database.museum/guid/MVZ:Herp:51568?seid=525813
+ https://www.gbif.org/species/2457545
+
+
+ https://www.gbif.org/species/2457545
+ Thamnophis elegans (Baird & Girard, 1853)
+ species
+ Thamnophis
+ elgans
+
+
+ http://arctos.database.museum/guid/MVZ:Herp:51500?seid=670405
+ PhysicalObject
+ PreservedSpecimen
+ MVZ
+ Amphibian and reptile specimens
+ MVZ:Herp:51500
+ Gordon W. Gullion
+ 525813
+ http://arctos.database.museum/MediaSearch.cfm?collection_object_id=10513964
+ "found as stomach contents of":"http://arctos.database.museum/guid/MVZ:Herp:51568?seid=525813"
+
+
+ http://arctos.database.museum/guid/MVZ:Herp:51500
+ multicellular organism
+ "eaten by":"http://arctos.database.museum/guid/MVZ:Herp:51568"
+
+
+ Museum of Vertebrate Zoology, University of California, Berkeley
+ 1999-01-27
+ http://arctos.database.museum/guid/MVZ:Herp:51500?seid=670405
+ https://www.gbif.org/species/2432022
+
+
+ https://www.gbif.org/species/2432022
+ Dicamptodon tenebrosus (Baird & Girard, 1852)
+ species
+ Dicamptodon
+ tenebrosus
+
+
+ http://arctos.database.museum/guid/MVZ:Herp:51568
+ ate
+ http://arctos.database.museum/guid/MVZ:Herp:51500
+
+
+ http://arctos.database.museum/guid/MVZ:Herp:51500
+ eaten by
+ http://arctos.database.museum/guid/MVZ:Herp:51568
+
+```
-Here is different example demonstrating area count observations for events on two different days at one location. Note that we omit the identification class here as there is not identification related data and link via the `taxonID` directly:
+Here is an example demonstrating area count observations for Events on two different days at the same location. Note that we omit the identification class here as there is no identification-related data and link directly to the Taxon via the `taxonID`:
```xml
-
-
-
- http://guid.mvz.org/sites/arg/127
- Argentina
- AR
- Neuquén
- Valle Limay, Estancia Rincon Grande, 48 ha area with centroid at this point
- -40.97467
- -71.0734
- WGS84
- 200
-
-
- http://guid.mvz.org/events/2006/11/26/17
- area count
- 2006-11-26
- http://guid.mvz.org/sites/arg/127
-
-
- urn:catalog:AUDCLO:EBIRD:OBS64515288
- Event
- 2009-02-17T07:33:04Z
- AUDCLO
- EBIRD
- HumanObservation
- 2
- http://guid.mvz.org/events/2006/11/26/17
- urn:lsid:catalogueoflife.org:taxon:f000ee00-29c1-102b-9a4a-00304854f820:col20120721
-
-
- urn:lsid:catalogueoflife.org:taxon:f000ee00-29c1-102b-9a4a-00304854f820:col20120721
- Anthus hellmayri Hartert, 1909
- Aves
- Anthus
- hellmayri
-
-
- urn:catalog:AUDCLO:EBIRD:OBS64515286
- Event
- 2009-02-17T07:33:04Z
- AUDCLO
- EBIRD
- HumanObservation
- 1
- http://guid.mvz.org/events/2006/11/26/17
- urn:lsid:catalogueoflife.org:taxon:f000e838-29c1-102b-9a4a-00304854f820:col20120721
-
-
- urn:lsid:catalogueoflife.org:taxon:f000e838-29c1-102b-9a4a-00304854f820:col20120721
- Anthus correndera Vieillot, 1818
- Aves
- Anthus
- correndera
-
-
- http://guid.mvz.org/events/2006/11/27/6
- area count
- 2006-11-27
- http://guid.mvz.org/sites/arg/127
-
-
- urn:catalog:AUDCLO:EBIRD:OBS64515333
- Event
- 2009-02-17T07:33:04Z
- AUDCLO
- EBIRD
- HumanObservation
- 1
- http://guid.mvz.org/events/2006/11/27/6
- urn:lsid:catalogueoflife.org:taxon:f000ee00-29c1-102b-9a4a-00304854f820:col20120721
-
-
- urn:catalog:AUDCLO:EBIRD:OBS64515331
- Event
- 2009-02-17T07:33:04Z
- AUDCLO
- EBIRD
- HumanObservation
- 2
- http://guid.mvz.org/events/2006/11/27/6
- urn:lsid:catalogueoflife.org:taxon:f000ee00-29c1-102b-9a4a-00304854f820:col20120721
-
+
+
+
+ AR-NQ-LL-ERG
+ Argentina
+ AR
+ Neuquén
+ Valle Limay, Estancia Rincon Grande, 48 ha area with centroid at this point
+ -40.97467
+ -71.0734
+ WGS84
+ 200
+
+
+ JW-AR-NQ-LL-ERG/2006/11/26
+ area count
+ 2006-11-26
+ AR-NQ-LL-ERG
+
+
+ URN:catalog:CLO:EBIRD:OBS64515288
+ CLO
+ EBIRD
+ HumanObservation
+ 2
+ JW-AR-NQ-LL-ERG/2006/11/26
+ https://www.gbif.org/species/2490280
+
+
+ https://www.gbif.org/species/2490280
+ Anthus hellmayri Hartert, 1909
+ Aves
+ Anthus
+ hellmayri
+
+
+ URN:catalog:CLO:EBIRD:OBS64515286
+ CLO
+ EBIRD
+ HumanObservation
+ 4
+ JW-AR-NQ-LL-ERG/2006/11/26
+ https://www.gbif.org/species/9286490
+
+
+ https://www.gbif.org/species/9286490
+ Anthus correndera Vieillot, 1818
+ Aves
+ Anthus
+ correndera
+
+
+ JW-AR-NQ-LL-ERG/2006/11/27
+ area count
+ 2006-11-27
+ AR-NQ-LL-ERG
+
+
+ URN:catalog:CLO:EBIRD:OBS64515333
+ CLO
+ EBIRD
+ HumanObservation
+ 2
+ JW-AR-NQ-LL-ERG/2006/11/27
+ https://www.gbif.org/species/2490280
+
+
+ urn:catalog:AUDCLO:EBIRD:OBS64515331
+ CLO
+ EBIRD
+ HumanObservation
+ 4
+ JW-AR-NQ-LL-ERG/2006/11/27
+ https://www.gbif.org/species/9286490
+
```
diff --git a/docs/xml/tdwg_basetypes.xsd b/docs/xml/tdwg_basetypes.xsd
index 59da2a4..ac1db24 100644
--- a/docs/xml/tdwg_basetypes.xsd
+++ b/docs/xml/tdwg_basetypes.xsd
@@ -13,6 +13,7 @@
@@ -76,13 +77,14 @@
- The date and time expressed in a way conforming to a subset of ISO 8601. Meant to be exactly the same as DateTimeISO defined in ABCD.
+ The date and time expressed in a way conforming to a subset of ISO 8601.
+ Meant to be exactly the same as DateTimeISO defined in ABCD.
-
+
-
diff --git a/docs/xml/tdwg_dwc_class_terms.xsd b/docs/xml/tdwg_dwc_class_terms.xsd
index 27f26c5..696890a 100644
--- a/docs/xml/tdwg_dwc_class_terms.xsd
+++ b/docs/xml/tdwg_dwc_class_terms.xsd
@@ -1,14 +1,17 @@
-
- This schema redefines all darwin core classes to disallow compound
- objects - within a class no other nested class is allowed. It
- allows properties to occur in any order and as many times as needed.
+ This schema redefines all Darwin Core classes to disallow compound objects -
+ within a class no other nested class is allowed. It allows properties to
+ occur in any order and as many times as needed.
@@ -57,8 +60,6 @@
-
-
@@ -103,17 +103,6 @@
-
-
-
-
-
-
-
-
-
-
-
@@ -125,4 +114,25 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/xml/tdwg_dwc_classes.xsd b/docs/xml/tdwg_dwc_classes.xsd
index 77899eb..4b59f4a 100644
--- a/docs/xml/tdwg_dwc_classes.xsd
+++ b/docs/xml/tdwg_dwc_classes.xsd
@@ -1,14 +1,18 @@
-
-
+
- This schema defines a container for all darwin core classes with no notion of a record per se.
- All classes are treated equally.
+ This schema defines a container for all Darwin Core classes with no notion
+ of a record per se. All classes are treated equally.
@@ -19,5 +23,4 @@
-
diff --git a/docs/xml/tdwg_dwc_extensions.xsd b/docs/xml/tdwg_dwc_extensions.xsd
index f0ed398..3929d33 100644
--- a/docs/xml/tdwg_dwc_extensions.xsd
+++ b/docs/xml/tdwg_dwc_extensions.xsd
@@ -1,11 +1,15 @@
-
-
+
@@ -35,8 +39,10 @@
+
+
-
+
@@ -44,4 +50,29 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/xml/tdwg_dwc_simple.xsd b/docs/xml/tdwg_dwc_simple.xsd
index 2e63f1a..dcc7b64 100644
--- a/docs/xml/tdwg_dwc_simple.xsd
+++ b/docs/xml/tdwg_dwc_simple.xsd
@@ -1,12 +1,21 @@
-
-
-
+
+
+
This schema defines Simple Darwin Core records and record sets using the
@@ -18,7 +27,7 @@
Simple container to encode multiple darwin core records
that have no notion of which class they are. They can therefore represent
- a taxon, an observation or just a locality, for example.
+ a taxon, an observation, or just a locality, for example.
@@ -31,9 +40,9 @@
-
+
-
+
@@ -55,6 +64,7 @@
+
@@ -63,10 +73,14 @@
+
+
+
+
@@ -76,7 +90,6 @@
-
@@ -119,6 +132,7 @@
+
@@ -144,7 +158,6 @@
-
@@ -167,9 +180,11 @@
+
+
@@ -196,10 +211,14 @@
+
+
+
+
diff --git a/docs/xml/tdwg_dwcterms.xsd b/docs/xml/tdwg_dwcterms.xsd
index 809319d..ce7ba12 100644
--- a/docs/xml/tdwg_dwcterms.xsd
+++ b/docs/xml/tdwg_dwcterms.xsd
@@ -1,39 +1,56 @@
The Generic Darwin Core schema defining all property terms as global elements.
- Domain classes are not defined here, but in a separate schema (tdwg_dwcclasses.xsd) with the same namespace.
- There are two ways in which references to domains can be defined:
- a) through an abstract base term anyXXXTerm, which is derived from the type dwc:anyPropery and which all properties
- for that domain use as their substitution group. If you refer to dwc:anyXXXTerm in your schema, you will be able
- to reference any of the terms, but it will be impossible to create a sequence of all terms occurring only once.
- b) through a group of elements called XXXTerms, which reference properties exactly once as a sequence.
- This group can be used to refer to all the domain properties only once. In order to make a property required, you
- must create your own group referring to the individual dwc terms.
- If you want to specify every term once at most and in any order, you will also have to refer to the individual dwc
- term yourself - a limitation of the xs:all model.
+ Domain classes are not defined here, but in a separate schema
+ (tdwg_dwc_classes.xsd) with the same namespace. There are two ways in which
+ references to domains can be defined:
+ a) through an abstract base term anyXXXTerm, which is derived from the type
+ dwc:anyPropery and which all properties for that domain use as their
+ substitution group. If you refer to dwc:anyXXXTerm in your schema, you
+ will be able to reference any of the terms, but it will be impossible to
+ create a sequence of all terms occurring only once.
+ b) through a group of elements called XXXTerms, which reference properties
+ exactly once as a sequence. This group can be used to refer to all the
+ domain properties only once each. In order to make a property required,
+ you must create your own group referring to the individual dwc terms. If
+ you want to specify every term once at most and in any order, you will
+ also have to refer to the individual dwc term yourself - a limitation of
+ the xs:all model.
-
+
+
-
-
-
+
+
+
+
+
- Group of all Darwin Core identifier terms as a convenience to construct other schemas
+ Group of all Darwin Core class identifier terms as a
+ convenience to construct other schemas
@@ -44,15 +61,19 @@
-
+
+
+
+
+
-
+
@@ -74,9 +96,9 @@
-
+
-
+
@@ -95,6 +117,7 @@
+
@@ -102,6 +125,7 @@
+
@@ -110,11 +134,15 @@
+
+
+
+
@@ -124,6 +152,7 @@
+
@@ -132,24 +161,28 @@
+
+
+
+
+
-
@@ -157,16 +190,17 @@
-
+
+
@@ -183,9 +217,9 @@
-
+
@@ -202,13 +236,14 @@
-
+
+
@@ -229,6 +264,7 @@
+
@@ -254,7 +290,6 @@
-
@@ -274,6 +309,7 @@
+
@@ -298,10 +334,10 @@
-
+
@@ -344,28 +380,34 @@
+
+
+
+
+
+
@@ -390,10 +432,14 @@
+
+
+
+
@@ -424,10 +470,14 @@
+
+
+
+
@@ -438,6 +488,7 @@
+
@@ -462,11 +513,13 @@
+
+
@@ -475,6 +528,7 @@
+
@@ -482,4 +536,47 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+