-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BFO OWL in repository, intended as a derived product, has been edited and is now out of sync #110
Comments
Once Barry and John have sorted out the differences I will adjust the source and regenerate the BFO OWL artifacts |
My preferred resolution is to revert all the definitions of the relations that have some time semantics back to the published BFO-2020.owl definitions, modulo actual bug fixes. |
As I recall, the changes were largely for consistency, grammar, and in at least one case an incorrect variable. Let me look through the changes and provide justification before moving out. |
@alanruttenberg Not sure if you intended to mention #102 instead of or in addition to #109, or you intended to do as you did, in which case I'm unsure why you didn't mention #102, but you mentioned #109 here. |
Another aspect of divergence is between the definitions of the some time relations in temporalized vs unqualified names but same as some-time semantics in core. The definitions should be the same modulo change in name. |
@avsculley, 102 is captured by a mention in that bug. See above
That's how any other related issues will be kept track of. |
Gotcha.. thanks for the clarification. I wasn't familiar with that feature.
…________________________________
From: Alan Ruttenberg ***@***.***>
Sent: Friday, September 27, 2024 8:44 PM
To: BFO-ontology/BFO-2020 ***@***.***>
Cc: Alec Sculley ***@***.***>; Mention ***@***.***>
Subject: Re: [BFO-ontology/BFO-2020] BFO OWL in repository, intended as a derived product, has been edited and is now out of sync (Issue #110)
@avsculley<https://github.com/avsculley>, 102 is captured by a mention in that bug. See above
alanruttenberg<https://github.com/alanruttenberg> mentioned this issue 2 hours ago
Definition and domain axiom of 'member part of' are not equally restrictive #102<#102>
That's how any other related issues will be kept track of.
—
Reply to this email directly, view it on GitHub<#110 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATJNTNYOC35DU6BGJMXQRCDZYX3YLAVCNFSM6AAAAABO3VK54WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQGMZDEMRYGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The definitions in BFO-core have been edited so that they are no longer in sync with those in the ISO source, from which the generated BFO is constructed. This has introduced multiple issues. The two versions need to be synchronized.
The text was updated successfully, but these errors were encountered: