Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some ranges are too restricted #43

Open
DieterDePaepe opened this issue Sep 19, 2017 · 0 comments
Open

Some ranges are too restricted #43

DieterDePaepe opened this issue Sep 19, 2017 · 0 comments

Comments

@DieterDePaepe
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant