Class `<<CodeList>> DescriptionPurpose`

Codes used for the specification of the intended purpose/level of abstraction for a given feature or object instance, ie the reason for the existence of the GeologicFeature.
Values: Instance, TypicalNorm, IdentifyingNorm.

Local Subclasses: (none)

Attributes

Name	Bounds	From Class	Notes
typicalNorm	1..1	DescriptionPurpose	TypicalNorm -- a description that specifies properties to be expected of some occurrence associated with the GeologicEntity. This description may include many properties that are not part of the DefiningNorm. For example, the fact that granite is typically light-colored is not a defining property, but is certainly a useful typical property. These kinds of descriptions would be used to address queries like 'This area is within a polygon classified as Podunk Formation; what sort of lithology am I most likely to encounter when I start digging?' The Podunk Formation may be defined by the presence of a certain ammonite... TypicalNorm description would be constructed as a summary over many Instance descriptions.

definingNorm	1..1	DescriptionPurpose	DefiningNorm -- a description that specifies properties sufficient to identify a new occurrence as belonging to the class represented by the description. Basically these are the 'sufficient conditions' for class membership. Used when presented with a query 'I have an outcrop with these properties; which geologic unit should I assign to the outcrop?' DefiningNorm has to do with the intension of a ControlledConcept.

instance	1..1	DescriptionPurpose	Instance -- a description that is specific to a particular observed occurrence. This is 'raw data', and its classification may start out as very general. There are kinds of narrowly defined ControlledConcepts that might not allow 'instances' that are different from the DefiningNorm. It might be worth considering a different relationship between MappedFeature and an Instance GeologicEntity, with the GeologicEntity role being 'description'.

Outbound Associations

Name	Type	Multiplicity	From Class	Notes

Constraints

Constraint	Type	Status	Weight

Tagged values

Tag	Value	Notes
asDictionary	false	Values: true,false Default: false Description: implement as a dictionary instead of enumeration
byValuePropertyType	false	Values: true,false Default: false Description: enforce the 'by value' property pattern without xl
codeSpace	#NOTES#Description: URI that identifies the authority for this dictionary and its members	Description: URI that identifies the authority for this dictionary and its members
dictionaryIdentifier	#NOTES#Description: URI that identifies this dictionary	Description: URI that identifies this dictionary
isCollection	false	Values: true,false Default: false Description: attribute group gml:AggregationAttributeGroup is a
memberIdentifierStem	#NOTES#Description: URI stem used for dictionary members	Description: URI stem used for dictionary members
noPropertyType	false	Values: true,false Default: false Description: suppress automatic creation of *PropertyType compl

GML-conformant XML Implementation Details

<xs:simpleType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="DescriptionPurposeType">
    <xs:union memberTypes="gsml:DescriptionPurposeEnumerationType gsml:DescriptionPurposeOtherType"/>
</xs:simpleType>

<xs:simpleType xmlns:xs="http://www.w3.org/2001/XMLSchema" name="DescriptionPurposeEnumerationType">
    <xs:restriction base="string">
        <xs:enumeration value="typicalNorm">
            <xs:annotation>
                <xs:documentation>TypicalNorm -- a description that specifies properties to be expected of some occurrence associated with the GeologicEntity. This description may include many properties that are not part of the DefiningNorm. For example, the fact that granite is typically light-colored is not a defining property, but is certainly a useful typical property. These kinds of descriptions would be used to address queries like 'This area is within a polygon classified as Podunk Formation; what sort of lithology am I most likely to encounter when I start digging?' The Podunk Formation may be defined by the presence of a certain ammonite... TypicalNorm description would be constructed as a summary over many Instance descriptions.</xs:documentation>
            </xs:annotation>
        </xs:enumeration>
        <xs:enumeration value="definingNorm">
            <xs:annotation>
                <xs:documentation>DefiningNorm -- a description that specifies properties sufficient to identify a new occurrence as belonging to the class represented by the description. Basically these are the 'sufficient conditions' for class membership. Used when presented with a query 'I have an outcrop with these properties; which geologic unit should I assign to the outcrop?' DefiningNorm has to do with the intension of a ControlledConcept.</xs:documentation>
            </xs:annotation>
        </xs:enumeration>
        <xs:enumeration value="instance">
            <xs:annotation>
                <xs:documentation>Instance -- a description that is specific to a particular observed occurrence. This is 'raw data', and its classification may start out as very general. There are kinds of narrowly defined ControlledConcepts that might not allow 'instances' that are different from the DefiningNorm. It might be worth considering a different relationship between MappedFeature and an Instance GeologicEntity, with the GeologicEntity role being 'description'.</xs:documentation>
            </xs:annotation>
        </xs:enumeration>
    </xs:restriction>
</xs:simpleType>