-
Notifications
You must be signed in to change notification settings - Fork 0
Description
I think we should give names to classes and named individuals even more systematically than now.
For example: in the EGAD schema (TBox) file:
https://github.com/SAWGraph/kg-construction/blob/1d6febb71ebe2cacd6694460b8f503ab4411c0ed/ontologies/egad-maine-samples/egad_sites_samples-schema-diagram.ttl
Consider the following example
### http://sawgraph.spatialai.org/v1/me-egad#sampleLocation.w
me_egad:sampleLocation.w rdf:type owl:NamedIndividual ,
me_egad:EGAD-SampleLocation ;
rdfs:label "WADING" .
I would suggest two changes:
-
Add a common class name parts (prefix/appendix) to each class that represents a controlled vocabulary. I suggest using CT at the end to allow a "natural" alphabetic order where the CT classes always appear together with the class they are used to describe:
E.g. rename the class to me_egad:EGAD-SampleLocation-CT -
If we have a class label "EGAD-SampleLocation-CT" then use the full class name as part of the URI for the individuals. That makes writing a universal script that generates URIs much easier (using the class name as the parameter)
Because individuals would then start with an upper case letter, we should precede the name with either "d" (for a data point) or "c" for a controlled term. Overall, the updated triples would be:
### http://sawgraph.spatialai.org/v1/me-egad#**c.EGAD-**sampleLocation**-CT**.w
me_egad:c.EGAD-SampleLocation-CT.w rdf:type owl:NamedIndividual ,
me_egad:EGAD-SampleLocation-CT ;
rdfs:label "WADING" .
As another example:
### http://sawgraph.spatialai.org/v1/me-egad#samplePointType.acs
me_egad:samplePointType.acs rdf:type owl:NamedIndividual ,
me_egad:EGAD-SamplePointType ;
rdfs:label "ASPHALT/CONCRETE SURFACE" .
This would change to:
### http://sawgraph.spatialai.org/v1/me-egad#c.EGAD-SamplePointType-CT.acs
me_egad:c.EGAD-SamplePointType.acs rdf:type owl:NamedIndividual ,
me_egad:EGAD-SamplePointType-CT ;
rdfs:label "ASPHALT/CONCRETE SURFACE" .