Closed uscholdm closed 9 months ago
How about: "Relates something to its physical location"?
The restriction seems good.
Didn't we also want a scope note to the effect that the location could be either permanent (a house) or transient (a car), and that if someone wants to specify a transient relationship they should use a temporal relation?
How about: "Relates something to its physical location"?
A definite improvement. Good idea.
Didn't we also want a scope note to the effect that the location could be either permanent (a house) or transient (a car), and that if someone wants to specify a transient relationship they should use a temporal relation?
We could, in which case, how about:
skos:scopeNote "To model changing locations, create a subclass of TemporalRelation (e.g. EstablishedLocation)" that reifies hasPhysicalLocation^^xsd:string ;
This might be setting a precedent; we don't usually say how to extend gist, that could get out of hand quickly. But it might make sense in this case. Let's see what people think.
gist:hasPhysicalLocation
a
owl:ObjectProperty ,
owl:TransitiveProperty
;
rdfs:range gist:Place ;
skos:definition "Relates something to its physical location."^^xsd:string ;
skos:prefLabel "has physical location"^^xsd:string ;
skos:scopeNote "To model changing locations, create a subclass of TemporalRelation (e.g. EstablishedLocation) that reifies hasPhysicalLocation"^^xsd:string ;
.
Oddly, EstablishedLocation
sounds to me like the permanent version.
Maybe we don't have to give explicit suggestions. How about just:
"This property includes both temporary (e.g., a car) and permanent (e.g., a house) locations of objects."
Given this was closely related to PR #941, I updated hasPhysicalLocation
as part of that PR. It currently is:
gist:hasPhysicalLocation
a
owl:ObjectProperty ,
owl:TransitiveProperty
;
rdfs:range gist:Place ;
skos:definition "Relates something to its physical location."^^xsd:string ;
skos:prefLabel "has physical location"^^xsd:string ;
skos:scopeNote "This property does not distinguish between things whose locations are stable and those whose locations change over time; e.g., a fire hydrant vs. a car."^^xsd:string ;
.
Closing - fixed in PR #941.
I propose changing the skos definition to:
ALSO: I propose adding a subclass restriction to the class,
gist:PhysicalIdentifiableItem
requiring it to have a physical location. Ie.(gist:hasPhysicalLocation some gist:Place)
. Perhaps the same forgist:PhysicalSubstance