Addresses::AddressComponent

: Public abstract <<featureType>> Class

Created:	10/04/2008 17:50:37
Modified:	22/02/2013 11:03:03

Project:
Author:	friisan
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{15B1EC9A-D683-486f-A56C-C4A9866C12E5}
Appears In:	Addresses, Spatial Object Types, Cross-theme Relationships

-- Definition -- Identifier or geographic name of a specific geographic area, location, or other spatial object which defines the scope of an address. -- Description -- NOTE 1 Four different subclasses of address components are defined: o Administrative unit name, which may include name of country, name of municipality, name of district o Address area name like e.g. name of village or settlement o Thoroughfare name, most often road name o Postal descriptor In order to construct an address, these subclasses are often structured hierarchically. NOTE 2 It is the combination of the address locator and the address components, which makes a specific address spatial object readable and unambiguous for the human user. EXAMPLE The combination of the locator "13" and the address components "Calle Mayor" (thoroughfare name), "Cortijo del Marqués" (address area name), "41037" (postal descriptor), "Écija", "Sevilla" and "España" (administrative unit names) makes this specific address spatial object readable and unambiguous.

Attributes
Associations To
Associations From
Tagged Values
Constraints
Other Links

Attribute

Public CharacterString
alternativeIdentifier

Details:

Alias:
Initial:
Stereotype:	<<voidable>>
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- External, thematic identifier of the address component spatial object, which enables interoperability with existing legacy systems or applications. -- Description -- NOTE Compared with a proper identifier of the address component, the alternative identifier is not necessarily persistent in the lifetime of the component spatial object. Likewise it is usually not globally unique and in general does include information on the version of the spatial object. EXAMPLE 1 National or regional sector-specific identifiers (like e.g. a number- or letter code) for administrative units, address areas (localities, villages, sub-divisions) or thoroughfare names, which are used by a number of existing legacy systems. EXAMPLE 2 In Denmark the four character municipal "road name code" (0001-9899) is only unique within the present municipality, thus if two municipalities merge, it is necessary to assign new road name codes.

Public DateTime
beginLifespanVersion

Details:

Alias:
Initial:
Stereotype:	<<voidable>>
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- Date and time at which this version of the spatial object was inserted or changed in the spatial data set. -- Description -- NOTE This date is recorded to enable the generation of change only update files.

Public DateTime
endLifespanVersion

Details:

Alias:
Initial:
Stereotype:	<<voidable>>
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- Date and time at which this version of the spatial object was superseded or retired in the spatial data set. -- Description -- NOTE This date is recorded primarily for those systems which "close" an entry in the spatial data set in the event of an attribute change.

Public Identifier
inspireId

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- External object identifier of the address component. -- Description -- NOTE 1 An external object identifier is a unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon. NOTE 2 The primary purpose of this identifier is to enable links between various sources and the address components. EXAMPLE An address component spatial object from Denmark could carry this identifier: Namespace: DK_ADR Local identifier: 0A3F507B2AB032B8E0440003BA298018 Version identifier: 12-02-2008T10:05:01+01:00

Public StatusValue
status

Details:

Alias:
Initial:
Stereotype:	<<voidable>>
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- Validity of the address component within the life-cycle (version) of the address component spatial object. -- Description -- NOTE This status relates to the address component and is not a property of the object to which the address is assigned (the addressable object).

Public DateTime
validFrom

Details:

Alias:
Initial:
Stereotype:	<<voidable>>
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- Date and time of which this version of the address component was or will be valid in the real world. -- Description -- NOTE This date and time can be set in the future for situations where an address component or a version of an address component has been decided by the appropriate authority to take effect for a future date.

Public DateTime
validTo

Details:

Alias:
Initial:
Stereotype:	<<voidable>>
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

-- Definition -- Date and time at which the address component ceased or will cease to exist in the real world.

Element	Source Role	Target Role
«featureType» Address Class	Name: component -- Definition -- Represents that the address component is engaged as a part of the address. -- Description -- EXAMPLE For the address designated "Calle Mayor 13, Cortijo del Marqués, 41037, Écija, Sevilla, España" the six address components "Calle Mayor", "Cortijo del Marqués", "41037", "Écija", "Sevilla" and "España" are engaged as address components.	Name:
Details:
«featureType» AddressComponent Class	Name: -- Definition --	Name: situatedWithin -- Definition -- Another address component within which the geographic feature represented by this address component is situated. -- Description -- NOTE 1 The association enables the application schema to express that the subtypes of address components in the dataset form a hierarchy e.g. like: thoroughfare name within municipality within region within country NOTE 2 The representation of the hierarchy facilitates queries e.g. for a specific thoroughfare name within a given municipality or postcode. It is also necessary where the application schema is used to create or update, for example , a gazetteer which is based on the hierarchical structure of the address components. NOTE 3 The multiplicity of the association allows it to express that a thoroughfare name is situated in a certain municipality and in a certain postcode. It is also possible to express, for example, that some thoroughfare names cross borders between municipalities and thus is situated within more than one municipality. EXAMPLE 1 In Spain many spatial objects of the thoroughfare name "Calle Santiago" exist. The association can express that one of the spatial objects is situated within in the municipality of Albacete. From the same example the municipality name "Albacete" is situated within the administrative name (region) of "Castilla La Mancha". EXAMPLE 2 In Denmark, several address area names entitled "Strandby" exists. In order to identify a specific spatial object it is necessary to know that the relevant spatial object is situated e.g. in the municipality of "Frederikshavn".
Details:

Element	Source Role	Target Role
«dataType» AddressLocator Class	Name:	Name: withinScopeOf -- Definition -- The address component that defines the scope within which the address locator is assigned according to rules ensuring unambiguousness. -- Description -- NOTE 1 For the assignment of unambiguous locators (e.g. address numbers) different rules exists in different countries and regions. According to the most common rule, an address number should be unique within the scope of the thoroughfare name. In other areas the address number is unique inside an address area name (e.g. the name of the village) or postal designator (e.g. the post code). In some areas even a combination of rules are applied: e.g. addresses with two locators, each of them referencing to a separate address component. NOTE 2 Locators that has the level of unit (like e.g. floor identifier and door or unit identifiers) are most often assigned so that they are unambiguous within the more narrow scope of the property or building; for these locators the association should therefore not be populated. EXAMPLE 1 In a typical European address dataset, parts of the addresses have locators which are unambiguous within the scope of the road name (thoroughfare name) while others are unambiguous within the name ogf the village or district (address area name). EXAMPLE 2 In Lithuania and Estonia a concept of "corner addresses" exists. Corner addresses have two address numbers (designators) each of them referring to a thoroughfare name (primary and secondary street name). E.g. in Vilnius the address designated "A. Stulginskio gatve 4 / A. Smetonos gatve 7" is situated on the corner of the two streets. EXAMPLE 3 In the Czech Republic in some cities an address has two locator designators: A building number which referres to the address area (district, cz: "cast obce") and a address number that referres to the thoroughfare name. As an example in Praha for address designated "Na Pankráci 1690/125, Nusle" the designator "1690" is a building number unique within the address area (cz cast obce) "Nusle", while the "125" is an address number that has the thoroughfare name as its scope.
Details:
«featureType» AddressComponent Class	Name: -- Definition --	Name: situatedWithin -- Definition -- Another address component within which the geographic feature represented by this address component is situated. -- Description -- NOTE 1 The association enables the application schema to express that the subtypes of address components in the dataset form a hierarchy e.g. like: thoroughfare name within municipality within region within country NOTE 2 The representation of the hierarchy facilitates queries e.g. for a specific thoroughfare name within a given municipality or postcode. It is also necessary where the application schema is used to create or update, for example , a gazetteer which is based on the hierarchical structure of the address components. NOTE 3 The multiplicity of the association allows it to express that a thoroughfare name is situated in a certain municipality and in a certain postcode. It is also possible to express, for example, that some thoroughfare names cross borders between municipalities and thus is situated within more than one municipality. EXAMPLE 1 In Spain many spatial objects of the thoroughfare name "Calle Santiago" exist. The association can express that one of the spatial objects is situated within in the municipality of Albacete. From the same example the municipality name "Albacete" is situated within the administrative name (region) of "Castilla La Mancha". EXAMPLE 2 In Denmark, several address area names entitled "Strandby" exists. In order to identify a specific spatial object it is necessary to know that the relevant spatial object is situated e.g. in the municipality of "Frederikshavn".
Details:

Tag	Value
byValuePropertyType	false
Details:
isCollection	false
Details:
noPropertyType	false
Details:
xsdEncodingRule	iso19136_2007_INSPIRE_Extensions
Details:

Constraint	Type	Status
EndLifeSpanVersion	OCL	Approved
Details: /* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */<br/>inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)<br/>

Object	Type	Connection	Direction	Notes
«featureType» ThoroughfareName	Class	Generalization	From
«featureType» Address	Class	Weak	To
«featureType» PostalDescriptor	Class	Generalization	From
«featureType» AddressAreaName	Class	Generalization	From
«featureType» AdminUnitName	Class	Generalization	From