Open dr-shorthair opened 5 years ago
From #19
dr-shorthair commented 5 days ago Propose making gnaf:StreetLocality the principle class in gnaf-ont - sub-class of geo:Feature and gnaf:GnafEntity. Not quite sure what gnaf:Street does
nicholascar commented 21 hours ago I remember these Street class issues, a couple of years ago now! No answers I’m afraid only I agree with your characterisation of the situation
dr-shorthair commented 20 hours ago My hunch is that you guys wanted a general 'Street' class to aggregate all the sections represented as StreetLocality, but you got a bit tangled up in the sub-classing relationships. Have added some comments for now, so we can come back to it.
Definition: a complete Street that crosses multiple localities.
NOTE: In principle, a Street is composed of several StreetLocality members, however this relationship is not present in the GNAF Ontology. Furthermore, the GNAF product definition does not contain a class for Street, only for StreetLocality. The GNAF Ontology does not therefore correspond to the GNAF product in this area, and should be reviewed and potentially revised to capture the correct alignment. In particular, in the GNAF Ontology geometry is associated with gnaf:StreetLocality, but not with gnaf:Street which means that gnaf:Street as a sub-class of geo:Feature is not Loc-I conformant.
TODO
Street
to StreetLocality
StreetLocality sub-class-of Street
StreetLocality sub-class-of geo:Feature , gnaf:GnafEntity
Street
as an aggregate of StreetLocality
individuals but note that it is not derived from GNAF productStreet sub-class-of geo:Feature
but not gnaf:GnafEntity
Is the relationship between a Street and its component StreetLocality segments explicit in the data? Is there a missing relationship in the ontology?