398 alignment with bfo

[dr-shorthair]

Closes #398

Preview https://raw.githack.com/w3c/sdw-sosa-ssn/398-alignment-with-bfo/ssn/index.html#BFO-alignment

[dr-shorthair]

Alignment of sosa:Procedure now consistent with the alignment of prov:Plan to CCO information content entity as given in https://github.com/BFO-Mappings/PROV-to-BFO/blob/main/prov-cco-directmappings.ttl which is the basis of Nature paper https://doi.org/10.1038/s41597-025-04580-1

I'm comfortable that this set of alignments is OK now.
@alanruttenberg might have opinions.

[dr-shorthair]

@ldesousa I checked to see if the CCO URIs dereference - I'm finding that they pull down TTL representations quite nicely
e.g. https://www.commoncoreontologies.org/ont00000958

The BFO ones go to Ontobee or OLS, except for http://purl.obolibrary.org/obo/BFO_0000057 (has participant) which is failing.

I've reported it here BFO-ontology/BFO-2020#154

[alanruttenberg]

@dr-shorthair Did a first quick browse. I noticed Generation, Usage, and Invalidation are subclass of Instantaneous Event, which looked suspicious.
In

Influence subClassOf:
(process or 'process boundary')
 and (not (process
 and 'process boundary'))

you don't need and (not (process and 'process boundary') because those are already disjoint.

When you write something like independent continuant or specifically dependent continuant or generically dependent continuant and not spatial region it allows for things that are not BFO entities, because the complement of spatial region includes owl:Things that are not BFO entities. Is there anything that isn't a BFO entity? If not the above would be better written as bfo:entity and not occurrent and not spatial region

[dr-shorthair]

Thanks @alanruttenberg .

I think your comment relates to the PROV-BFO alignment from the Nature Scientific Data paper - Figure 2, where PROV Influence is shown. We aren't responsible for that work. I just used it to provide some perspectives, since we had already aligned SSN with PROV in the 2017 edition of SSN.

What we request now is a review of the direct alignment of SSN to BFO/CCO which can be inspected in draft tabulated here and in the RDF (Turtle) representation here

[dr-shorthair]

Please note that I have erred on the generalized side in the BFO/CCO hierarchy, and @alanruttenberg may suggest some tighter alignments for e.g. sosa:Sample.

[maximelefrancois86]

very minor changes:

in html:

• order in section 4.3 is not the same as in section 7
• the alignment of Property to Quality forces Properties to be "foi specific" (see examples). I think we should open up the alignment to BFO19 (Quality) OR BFO31 (generically dependent continuent)
• sosa:implements cannot be aligned to BFO34 (function), which is a class
• can't find any object property in the version of BFO I found. and BFO55 (realizes) and BFO57 (has participant) don't dereference
• change/define style for explanation span next to rhs ? (monospaced font not justified, as the text is not part of the concept CURIE)

[dr-shorthair]

Thanks @maximelefrancois86 - I've fixed all of these except the alignment of sosa:implements - see https://raw.githack.com/w3c/sdw-sosa-ssn/398-alignment-with-bfo/ssn/index.html#BFO-alignment

@alanruttenberg do you have any suggestions for this? implements links an instance of a System (i.e. a Sensor or Actuator or Sampler) to the description of the Procedure (i.e. the recipe or specification) that it follows. We have mapped System to Independent Continuant and Procedure to Information Content Entity. What are the object-property options that tie an independent continuant to a generically dependent continuant?

[dr-shorthair]

I have suggested alignment of implements to is subject of which is a kind of generic independent continuant --> generically dependent continuant relationship.

I think this now clears all the concerns raised by @maximelefrancois86

Preview https://raw.githack.com/w3c/sdw-sosa-ssn/398-alignment-with-bfo/ssn/index.html#BFO-alignment

[dr-shorthair]

Please review this PR @maximelefrancois86 @kjano @ldesousa @oldskeptic