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

GeographicalName subtypes skos:Concept #41

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

GeographicalName subtypes skos:Concept #41

DieterDePaepe opened this issue Sep 19, 2017 · 0 comments

Comments

@DieterDePaepe
Copy link

GeographicalName is currently defined as:

gn:GeographicalName  a   owl:Class ;
        rdfs:subClassOf  skos:Concept ;
        skos:definition  "Proper noun applied to a real world entity."@en .

I believe this subclassing is done to have compatibility with locn:geographicName (see the last sentence in the comment).

locn:geographicName a rdf:Property ;
    rdfs:label "geographic name"@en ;
    rdfs:comment """
A geographic name is a proper noun applied to a spatial object. Taking the example used in the relevant INSPIRE data specification (page 18), the following are all valid geographic names for the Greek capital:
...
For INSPIRE-conformant data, provide the metadata for the geographic name using a skos:Concept as a datatype."""@en ;

However, RDF defines the term "datatype" as the datatype of a literal, of which xsd:string is an example. As such, I always assumed geographicname would be used as follows:

ex:myAdminUnitName ad:name "Brussels"^^ex:brusselsDT.

ex:brusselsDT a rdfs:Datatype ;
  rdfs:subClassOf rdfs:Literal ;
  gn:pronunciation "brʌs(ə)lz".

I am not sure if this is what core location originally intended, but it would be a more unified way since there is no mixup of GeographicalName as literal and as non-literal.

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