-
Notifications
You must be signed in to change notification settings - Fork 0
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
Generate yaml for postcoordination properties #11
Comments
Yes, this past week I was trying to figure out how to add these properties. Initially I was using the ICD Schema's list of post-coordination properties. Thanks for the suggestion to use the declarations in the icd-base.owl. However, I found that the icd:Schema has additional post-coordination properties like jointInvolvementInFracture, extentOfBurnByBodySurface. I added them at the end. I used LinkML subproperty_of to indicate sub property relationship. However, the generated OWL ontology flatten everything. I still need to follow up on this. |
The following post-coordination axes are specified in the ICD Schema but not in the list object properties in the whofic-2024-01-21.owl file:
|
The postcoordination axes listed in the schema should be part of the OWL file. Not sure why they were not part of the export, maybe they were not used. I've attached the hierarchy of all postcoordination axes in a tab-indented file: |
…oordination axes - Re-organized and added ICD post-coordination axes based on https://github.com/user-attachments/files/15616287/postcoordination_axes_hierarchy.txt. Added ICHI post-coordination axes and ICF qualifiers based on Protege 3 whofic_content_model_for_icatx. This should resolve issues #11 and #16 - Regenerated owl file from yaml, and made the following manual changes: -- Delete ".owl.ttl" from the generated Ontology IRI -- Renamed IndexType#Synonym to IndexType.Synonym -- Renamed IndexType#Narrower to IndexType.Narrower -- Made IndexType a subclass of ContentModelEntity -- Deleted http://who.int/icd#WHOFICEntityModel and its subclasses
The postcoordination properties are needed to create the logical definitions. They are already extracted in the OWL file referenced below. We can include this OWL file directly in the content model, or generate the yaml, and then regenerate the OWL file..
https://github.com/who-icatx/content-migration/blob/main/script/template/icd-base.owl
The text was updated successfully, but these errors were encountered: