Remove range of bf:place and bf:originPlace to provide for objects that are not typed bf:Place about bibframe-ontology HOT 6 CLOSED

Out of curiosity, can you provide an example of how this produces an undesirable entailment?

Under what circumstances would an entailment that concludes a given GeoName resource is also a bf:Place, be a problem or possibly untrue?

from bibframe-ontology.

Maybe Geonames is a bad example; geonames:Features and bf:Place definitions are pretty similar. That said, one might want to ward off class pollution and keep a clean representation of Geonames entities as they intended them to be described. A more likely situation is when a place is modeled as a skos:Concept or madsrdf:Authority, and while they are not bf:Places, a profile may want to link to them using bf:place.

from bibframe-ontology.

re: ARM related requests for changes to BF, I’ve responded above to give more context about the thought process at the time we made these requests. I've reached out to folks still affiliated ARM to consider how they want to weigh in.

Generally, the domain and range questions are a design decision... how much do you want to rely on these type assertions, how comfortable are you with assigning type to entities you didn't mint, and... many folks confuse domain and ranges for validation instead of inferencing which can lead to a chilling effect on the use of these properties.

from bibframe-ontology.

For consistency purposes, I'm adding bf:originPlace to this request. See new title

from bibframe-ontology.

PoCo also voted in favor (Dec. 2020) of removing the range of bf:Place from bf:place. This is an outcome of the final report of the PCC Task Group on Sinopia Application Profiles (https://www.loc.gov/aba/pcc/taskgroup/Sinopia-Profiles-TG-Final-Report.pdf)
From the report "The addition of ranges to BF properties introduces challenges regarding inferencing and linked data best practices. At a practical level, a range may restrict the breadth of possible vocabularies that are usable according to best practice.

from bibframe-ontology.

https://id.loc.gov/ontologies/bibframe.html#p_place
https://id.loc.gov/ontologies/bibframe.html#p_originPlace

from bibframe-ontology.