head	1.9;
access;
symbols;
locks; strict;
comment	@# @;


1.9
date	2007.06.09.12.49.46;	author WalterBerendsohn;	state Exp;
branches;
next	1.8;

1.8
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.7;

1.7
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.6;

1.6
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.5;

1.5
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.4;

1.4
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.3;

1.3
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.2;

1.2
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	1.1;

1.1
date	2007.01.09.00.00.00;	author MoinMoin;	state Exp;
branches;
next	;


desc
@Initial revision
@


1.9
log
@none
@
text
@%META:TOPICINFO{author="WalterBerendsohn" date="1181393386" format="1.1" reprev="1.9" version="1.9"}%
The following changes will only be implemented if a new major version of ABCD under a new namespace will be published. Ideally this will involve a far more modular approach towards TDWG standards (XML or otherwise), so the changes proposed below should be understood as notes rather than concrete steps to be taken. In any case, a major version change for ABCD is not expected before 2009. 
---++ General issues
Elements containing personal contact information such as e-mail addresses or phone-numbers should have a flag indicating whether the provider allows display of these elements in human readable interfaces such as web pages.

---++ Dataset level
<verbatim>/Datasets/Dataset/ContentContact</verbatim>
   Move to <verbatim>/Datasets/Dataset/Metadata</verbatim>

<verbatim>/Datasets/Dataset/TechnicalContact</verbatim>
   Remove (Is not needed in future under TAPIR (part of service metadata section in protocol schema)

<verbatim>/Datasets/Dataset/Metadata/RevisionData/DateModified</verbatim>
   Make optional. (problematic because experience shows that providers don't update this field).

<verbatim>/DataSets/DataSet/Metadata/Scope/GeoecologicalTerms/GeoEcologicalTerm</verbatim>
   Rename <verbatim>/DataSets/DataSet/Metadata/Scope/GeoecologicalTerms/GeoecologicalTerm</verbatim> (for consistency)

---++ Unit level

<verbatim>/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal</verbatim>
   Change type to <verbatim>decimalLongitude</verbatim> (new type, restricted to +180 to -180)

<verbatim>/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal</verbatim>
   Change type to <verbatim>decimalLatitude</verbatim> (new type, restricted to +90 to -90)


---++ Changes in types

<verbatim>IPRStatements [type]</verbatim> <verbatim>TermsOfUseStatements/TermsOfUse</verbatim>
   Rename to <verbatim>TermsOfUseStatements/TermsOfUseStatement</verbatim> for consistency.

<verbatim>LookupL [type]</verbatim> attribute <verbatim>Language</verbatim>
   Delete. 

<verbatim>Contact [type]</verbatim> <verbatim>URIs/URL</verbatim>
   Delete.

<verbatim>/Datasets/Dataset/Unit/HerbariumUnit/DuplicatesDistributedTo</verbatim>
   Delete (superfluous duplicate of <verbatim>/Datasets/Dataset/Unit/SpecimenUnit/DuplicatesDistributedTo</verbatim>)

<verbatim>/DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts</verbatim>
   Delete type (container element should be untyped).

<verbatim>/DataSets/DataSet/Units/Unit/CultureCollectionUnit/ FurtherStepsGrowthConditionAtomised/Temperature@@TemperatureTypes</verbatim>
   Delete.

<verbatim>/Datasets/Dataset/Unit/SpecimenUnit/Accessions/Accession/ </verbatim>
   Insert as container element for repeatable triple. Move the respective three elements.
@


1.8
log
@Revision 8
@
text
@d1 49
a49 48
The following changes will only be implemented if a new major version of ABCD under a new namespace will be published. Ideally this will involve a far more modular approach towards TDWG standards (XML or otherwise), so the changes proposed below should be understood as notes rather than concrete steps to be taken. In any case, a major version change for ABCD is not expected before 2009. 
---++ General issues
Elements containing personal contact information such as e-mail addresses or phone-numbers should have a flag indicating whether the provider allows display of these elements in human readable interfaces such as web pages.”

---++ Dataset level
<verbatim>/Datasets/Dataset/ContentContact</verbatim>
   Move to <verbatim>/Datasets/Dataset/Metadata</verbatim>

<verbatim>/Datasets/Dataset/TechnicalContact</verbatim>
   Remove (Is not needed in future under TAPIR (part of service metadata section in protocol schema)

<verbatim>/Datasets/Dataset/Metadata/RevisionData/DateModified</verbatim>
   Make optional. (problematic because experience shows that providers don’t update this field).

<verbatim>/DataSets/DataSet/Metadata/Scope/GeoecologicalTerms/GeoEcologicalTerm</verbatim>
   Rename <verbatim>/DataSets/DataSet/Metadata/Scope/GeoecologicalTerms/GeoecologicalTerm</verbatim> (for consistency)

---++ Unit level

<verbatim>/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LongitudeDecimal</verbatim>
   Change type to <verbatim>decimalLongitude</verbatim> (new type, restricted to +180 to -180)

<verbatim>/DataSets/DataSet/Units/Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLon/LatitudeDecimal</verbatim>
   Change type to <verbatim>decimalLatitude</verbatim> (new type, restricted to +90 to -90)


---++ Changes in types

<verbatim>IPRStatements [type]</verbatim> <verbatim>TermsOfUseStatements/TermsOfUse</verbatim>
   Rename to <verbatim>TermsOfUseStatements/TermsOfUseStatement</verbatim> for consistency.

<verbatim>LookupL [type]</verbatim> attribute <verbatim>Language</verbatim>
   Delete. 

<verbatim>Contact [type]</verbatim> <verbatim>URIs/URL</verbatim>
   Delete.

<verbatim>/Datasets/Dataset/Unit/HerbariumUnit/DuplicatesDistributedTo</verbatim>
   Delete (superfluous duplicate of <verbatim>/Datasets/Dataset/Unit/SpecimenUnit/DuplicatesDistributedTo</verbatim>)

<verbatim>/DataSets/DataSet/Units/Unit/Gathering/Biotope/MeasurementsOrFacts</verbatim>
   Delete type (container element should be untyped).

<verbatim>/DataSets/DataSet/Units/Unit/CultureCollectionUnit/ FurtherStepsGrowthConditionAtomised/Temperature@@TemperatureTypes</verbatim>
   Delete.

<verbatim>/Datasets/Dataset/Unit/SpecimenUnit/Accessions/Accession/ </verbatim>
   Insert as container element for repeatable triple. Move the respective three elements.
@


1.7
log
@Revision 7
@
text
@d2 2
@


1.6
log
@Revision 6
@
text
@a46 3

---++ Additional types
See <verbatim>positiveDouble</verbatim>, <verbatim>decimalLatitude</verbatim>, <verbatim>decimalLongitude</verbatim> and <verbatim>spatialFit</verbatim> under http://rs.tdwg.org/dwc/basetypes.xsd
@


1.5
log
@Revision 5
@
text
@d22 1
a22 1
   Change type to <verbatim>decimalLatitude</verbatim> (new type, restricted to +180 to -180)
@


1.4
log
@Revision 4
@
text
@d5 1
a5 1
Move to <verbatim>/Datasets/Dataset/Metadata</verbatim>
d8 1
a8 1
Remove (Is not needed in future under TAPIR (part of service metadata section in protocol schema)
d11 1
a11 1
Make optional. (problematic because experience shows that providers don’t update this field).
d14 1
a14 1
Rename <verbatim>/DataSets/DataSet/Metadata/Scope/GeoecologicalTerms/GeoecologicalTerm</verbatim> (for consistency)
d19 1
a19 2

Change type to <verbatim>decimalLongitude</verbatim> (new type, restricted to +180 to -180)
d22 1
a22 2

Change type to <verbatim>decimalLatitude</verbatim> (new type, restricted to +180 to -180)
d28 1
a28 2

Rename to <verbatim>TermsOfUseStatements/TermsOfUseStatement</verbatim> for consistency.
d31 1
a31 2

Delete. 
d34 1
a34 1
Delete.
d37 1
a37 1
Delete (superfluous duplicate of <verbatim>/Datasets/Dataset/Unit/SpecimenUnit/DuplicatesDistributedTo</verbatim>)
d40 1
a40 1
Delete type (container element should be untyped).
d43 1
a43 1
Delete.
d46 1
a46 1
Insert as container element for repeatable triple. Move the respective three elements.
@


1.3
log
@Revision 3
@
text
@d19 2
a20 1
Change type to decimalLongitude (new type, restricted to +180 to -180)
d23 2
a24 1
Change type to decimalLatitude (new type, restricted to +180 to -180)
d30 1
d34 1
d41 1
a41 1
Delete (superfluous duplicate of <verbatim>/Datasets/Dataset/Unit/SpecimenUnit/DuplicatesDistributedTo </verbatim>
d53 1
a53 1
See <verbatim>positiveDouble</verbatim>, {{decimalLatitude}}, {{decimalLongitude}} and {{spatialFit}} under http://rs.tdwg.org/dwc/basetypes.xsd
@


1.2
log
@Revision 2
@
text
@d1 1
a1 1
The following changes will only be implemented if a new major version of ABCD under a new namespace will be published. Ideally this will involve a far more modular approach towards TDWG standards (XML or otherwise), so the changes proposed below should be understood as notes rather than concrete steps to be taken. In any case, we do not expect a namespace change in ABCD before 2009. 
@


1.1
log
@Initial revision
@
text
@d3 1
a3 1
==Dataset level==
d16 1
a16 1
==Unit level==
d25 1
a25 1
==Changes in types==
d48 1
a48 1
==Additional types==
@