Schema.org ontology is inconsistent

[dillerm]

I ran the HermiT reasoner on the latest release of Schema.org and it found the ontology to be inconsistent. Unfortunately, it did not report which class(es) is inconsistent, so I recommend opening the ontology in a tool like Protege and running HermiT from there. You should be able to identify the offending class from the error report. It seems like this issue might be related to Issue #1797 and Issue #2787 , although there might be additional contradictions that need fixing.

[dr-shorthair]

Schema.org is not intended or designed to be OWL or DL consistent.

[danbri]

Simon is right; however these tools might still help flag technical implementation bugs in our definitions

…

On Sun, 13 Nov 2022 at 23:54, Simon Cox ***@***.***> wrote: Schema.org is not intended or designed to be OWL or DL consistent. — Reply to this email directly, view it on GitHub <#3212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABJSGMYF4BLNOBKPVZYAGTWIF5TXANCNFSM6AAAAAAR7E2BMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dillerm]

To clarify what I meant, the reasoner is checking whether the class- and individual-level assertions in Schema.org are consistent, not whether it's consistent with OWL or DL.

Example: the individual 'publisherImprint' is asserted to be isPartOf bib.schema.org, but the range for isPartOf is limited to 'CreativeWork' and 'Trip'. Because 'bib.schema.org' is not an instance of either 'CreativeWork' or 'Trip', this results in a contradiction.

[danbri]

Because 'bib.schema.org' is not an instance of either 'CreativeWork' or

'Trip' What supports this claim?

…

On Tue, 15 Nov 2022 at 18:22, Matthew Diller ***@***.***> wrote: To clarify what I meant, the reasoner is checking whether the class- and individual-level assertions in Schema.org are consistent, not whether it's consistent with OWL or DL. Example: the individual 'publisherImprint' is asserted to be isPartOf bib.schema.org, but the range for isPartOf is limited to 'CreativeWork' and 'Trip'. Because 'bib.schema.org' is not an instance of either 'CreativeWork' or 'Trip', this results in a contradiction. — Reply to this email directly, view it on GitHub <#3212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABJSGP726DSNPMGP7P5FUTWIPIEXANCNFSM6AAAAAAR7E2BMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[dillerm]

Ah, I just looked through the repository and found what may be a newer release (https://github.com/schemaorg/schemaorg/blob/main/data/releases/15.0/schemaorg.owl) than the most recent one uploaded to BioPortal. This release is consistent, but the one currently on BioPortal (version 3.4) is not. If you aren't too concerned with uploading a new version to BioPortal, we can close this issue.

[danbri]

Updating sounds like a good idea, although the OWL representation is rather a proof of concept

…

On Tue, 15 Nov 2022 at 21:20, Matthew Diller ***@***.***> wrote: Ah, I just looked through the repository and found what may be a newer release ( https://github.com/schemaorg/schemaorg/blob/main/data/releases/15.0/schemaorg.owl) than the most recent one uploaded to BioPortal. This release is consistent, but the one currently on BioPortal (version 3.4) is not. If you aren't too concerned with uploading a new version to BioPortal, we can close this issue. — Reply to this email directly, view it on GitHub <#3212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABJSGJ6ARGLGMLGVE6NC53WIP5AHANCNFSM6AAAAAAR7E2BMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[chrisspradling1980]

I highly recommend checking terminology discrepancies. For example: a definition of a class in real world interpretation would be a room or lab on a campus to which students learn as opposed to class in ontology which indicates to a group of object functions that create a process. There should be several that would make some difference to apply logical understanding in all languages. And please, you all forgive me if you don't mind because I'm lazy and railroaded to participate in the officiating of my scheme authorship due to the proposing proxy audit which automation hopefully would be requesting conflict of interest for a de-identification process in biomedical information technology. I can' wait either. Respectfully, Christopher Michael Spradling On Nov 13, 2022 12:36 PM, "Matthew Diller" ***@***.***> wrote: I ran the HermiT reasoner on the latest release of Schema.org and it found the ontology to be inconsistent. Unfortunately, it did not report which class(es) is inconsistent, so I recommend opening the ontology in a tool like Protege and running HermiT from there. You should be able to identify the offending class from the error report. It seems like this issue might be related to Issue #1797 <#1797> and Issue #2787 <#2787> , although there might be additional contradictions that need fixing. — Reply to this email directly, view it on GitHub <#3212>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADFVNUQHZOXS73NMKSSWBQLWIEYMXANCNFSM6AAAAAAR7E2BMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[iancappelletti]

second. i've studied meta-ontology before and would be willing to help classify these scope inconsistencies, tho i haven't worked with "reasoners" before (albeit they sound baller in theory). any suggestions on how to start?

[github-actions]

This issue is being nudged due to inactivity.

[chrisspradling1980]

How is this possible when the two are supposed to shake hands? P.S... Please don't forget about the agents. Is it not possible to have human agents someone...? Chris

…

On Mon, Mar 27, 2023, 9:23 PM github-actions[bot] ***@***.***> wrote: This issue is being nudged due to inactivity. — Reply to this email directly, view it on GitHub <#3212 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADFVNUVAJJVD43RAW7GRPEDW6JDS5ANCNFSM6AAAAAAR7E2BMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[github-actions]

This issue is being nudged due to inactivity.