Skip to content

Some ranges are too restricted #43

@DieterDePaepe

Description

@DieterDePaepe

For example:

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions