Open dr-shorthair opened 4 years ago
GnafEntity
is a spatial-object (feature or geometry) which has some lifecycle information (created, retired) and a mandatory identifier. Should be sub-class-of geo:SpatialObject
?GnafEntity
also with equivalent-class relationships with the ASGS classes recorded somewhere. (maybe in a separate graph). gnaf:State
equivalent to asgs:StateOrTerritory
gnaf:MB_2011
and gnaf:MB_2016
sub-classes of gnaf:MeshBlock
equivalent to asgs:MeshBlock
AddressSite
, MeshblockMatch
, Alias
). gnaf:StreetLocality
the principle class in gnaf-ont - sub-class of geo:Feature
and gnaf:GnafEntity
. Not quite sure what gnaf:Street
doesrelated to: #8
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
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.
geo:Geometry
is aGnafEntity
then the sub-class relationship is incorrect.