-
Notifications
You must be signed in to change notification settings - Fork 21
gistCore changes to support Units of Measure and Magnitudes #1064
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
Conversation
…t of Measure reference data.
…nitude that represented Aspects. temporary changes to restrictions for consistency (will add back in)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few suggestions.
…s such as the one for GeoRegion, added hasAspect to class equivalence for Magnitude, and also added the xsd data types that are in the range of numericValue
Working on release notes. A brief guide to review the new ontology is attached: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is amazing work! I've made some comments related to improving annotations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional comments and questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nearly there.
docs/releaseNote1033.md
Outdated
- `gist:hasPrecision` | ||
- `gist:conversionFactor` | ||
- `gist:conversionOffset` | ||
- Added scripts for the migration of existing client ontologies and instance data. [TODO - add pointer] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still to add
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pointer to what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pointer to the "Added scripts for the migration of existing client ontologies and instance data" in the bullet point. I suspect Rebecca added this.
docs/releaseNote1033.md
Outdated
- `gist:conversionFactor` | ||
- `gist:conversionOffset` | ||
- Added scripts for the migration of existing client ontologies and instance data. [TODO - add pointer] | ||
- Added complete documentation on understanding and implementing the new model. [TODO - add pointer] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still to add
docs/releaseNote1033.md
Outdated
|
||
This is a major release that includes several changes which break compatibility with previous versions of gist, most notably an entirely revised model of units and magnitudes. See the [migration guide](./MajorVersionMigration.html) for documentation on updating existing gist-based ontologies and instance data. Migration scripts are included to facilitate the upgrade process. | ||
|
||
### Major Updates |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This release notes file belongs in the release notes folder.
docs/releaseNote1033.md
Outdated
- Added scripts for the migration of existing client ontologies and instance data. [TODO - add pointer] | ||
- Added complete documentation on understanding and implementing the new model. [TODO - add pointer] | ||
|
||
Import URL: <https://w3id.org/semanticarts/ontology/gistCore13.0.0>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is relevant to units revision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe these are the scripts that @philblackwood wrote in order to identify and amend UoM triples in gist users' stores using the new patterns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe these are the scripts that @philblackwood wrote in order to identify and amend UoM triples in gist users' stores using the new patterns.
Yes, I agree. There is a separate PR for the data conversion scripts,it would be appropriate to have these comments in the other PR
ontologies/gistCore.ttl
Outdated
owl:onProperty gist:hasAltitude ; | ||
owl:someValuesFrom gist:Extent ; | ||
owl:someValuesFrom [ | ||
a owl:Class ; | ||
owl:intersectionOf ( | ||
gist:Magnitude | ||
[ | ||
a owl:Restriction ; | ||
owl:onProperty gist:hasAspect ; | ||
owl:hasValue gistd:_Aspect_distance ; | ||
] | ||
) ; | ||
] ; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't the recommended pattern to use hasMagnitude and have altitude as the aspect? Here might be a good place to illustrate the pattern where altitude hasBroader distance.
ALso, latitude and longitude could be modeled as aspects that have broader aspect_radian, or some such.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently follows the same usage as gist12.
Would be better to use gistd:_Aspect_altitude in the definition. Changed.
…ition of GeoPoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@philblackwood I think the hasAltitude
property should be removed, don't you?
OK, let's remove hasAltitude. Will do. |
…o represent aspects
…, remove hasAltitude
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@philblackwood - Im not sure which changes have been made, so this may be ready to approve. Apparently I had a few comments stacked up waiting for me to submit review.
docs/releaseNote1033.md
Outdated
- `gist:hasPrecision` | ||
- `gist:conversionFactor` | ||
- `gist:conversionOffset` | ||
- Added scripts for the migration of existing client ontologies and instance data. [TODO - add pointer] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pointer to the "Added scripts for the migration of existing client ontologies and instance data" in the bullet point. I suspect Rebecca added this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me.
Co-authored-by: Michael Uschold <uscholdm@users.noreply.github.com>
# Conflicts: # ontologies/gistCore.ttl
All requested changes have been addressed.
Adding two classes and one property. Fixes #1033.
Closes #1065.