CAAML changes from 2.2.5 to 2.2.6
---------------------------------

2004/10/08
by pascal@avisualanche.ca


CAAML_GEOG
**********

1.  removed AbstractLocationTypeBase

2.  derived AbstractLocationType from gml:AbstractFeatureType

3.  moved LOC_ABBREV to AbstractLocationTypeLocCatalog

4.  created abstract global _LOCATION_CATALOG_ELEMENT element
	- derived from AbstractLocationTypeLocCatalog
	- substitutable for gml:_Feature

5.  made all location elements (in catalog) substitutable for _LOCATION_CATALOG_ELEMENT


6.  derived LocationChildGenericType directly from gml:AssociationType by extension
    derived LocationChildMtnRangeType directly from gml:AssociationType by extension

7.  derived LocationParentGenericType directly from gml:AssociationType by extension
    derived LocationParentMtnRangeType directly from gml:AssociationType by extension

8.  simplified LocationChildrenTYpe and LocationParentsType
    created global elements of LOC_CHILDREN and LOC_PARENT


CAAML_OBS
*********

1.  derived basic AbstractObservationType from gml:AbstractFeatureType 
    (not from gml:ObservationType)

2.  created abstract global _OBSERVATION element
	- derived from AbstractObservationType
	- substitutable for gml:_Feature

3.  created the following types from AbstractObservationType (all by extension)
	- AbstractObservationTypeMultiLocRef
	- AbstractObservationTypeSingleLocRef
	- AbstractObservationTypeOptionalMultiLocRef

    !!!! this resulted in a change of order of elements !!!!
    !!!! <TIME_REPORT> is now before <LOCATION_REFERENCE> !!!!

4.  derived ObservationAssociationType directly from gml:AssociationType by extension

5.  all observation type definitions are not directly derived from one of the types under 3.

6.  all observation elements are substitutable for _OBSERVATION



CAAML
*****

1.  removed all location elements under LOCATION_INFO and replaced it with _LOCATION_CATALOG_ELEMENT
    (advantage: order of location elements does not matter)

2.  removed all observation elements under DATED_OBS and replaced it with _OBSERVATION
    (advantage: order of observation elements does not matter)

3.  added EXT_DATA element under OPERATION tag to allow external data that is not necessarily dated.
    (unique ID required, but currently not enforced)

4.  derived LINKS/LINK/OBJ element from ObservationAssociationType
    TYPE attribute is replaced by the more flexible use of xlink