ad:AddressComponent.alternativeIdentifier
a owl:DatatypeProperty ;
rdfs:domain ad:AddressComponent ;
rdfs:range xsd:string ;
skos:definition "External, thematic identifier of the address component spatial object, which enables interoperability with existing legacy systems or applications."@en .
Since multiple systems may be working with addresscomponents, it is likely that there will be several different identifiers in use. Of course, it is necessary to recognize which identifier belongs to which application. Currently, this can be done by subtyping this property for each application.
Instead, I would suggest changing the range to a literal, so also datatypes can be used for this, as well as allowing numerical identifiers.
For example:
Since multiple systems may be working with addresscomponents, it is likely that there will be several different identifiers in use. Of course, it is necessary to recognize which identifier belongs to which application. Currently, this can be done by subtyping this property for each application.
Instead, I would suggest changing the range to a literal, so also datatypes can be used for this, as well as allowing numerical identifiers.