> Which reasoner? IIRC SnomedCT uses various OWL features > The default RDFS reasoner does not include the "rdf4" rule which is a > whole-dataset rule > A ruleset tuned to needs may work better.
I tried this to only include subclass and equivalent class using the generic reasoner, but the dataset still would not load. Again, even only using the transitive reasoner (which I’ve found tends to be the most performant but haven’t run actual numbers yet) over snomed wouldn’t load the dataset. > If you want to navigate the ontology AND apply it to data, then you may need > two copies, one with and one with inference. If subclass closure has been > applied, you can’t see easily what the immediate parent of a concept is > (ontology browsing task) Yes, we plan on create a non-inferred fuseki service so that we can navigate (if we aren’t using the transitive reasoner, since it provides a direct subclass relationship) and an inferred one for all other queries. > do you need an inference engine at runtime at all? We will when we start pulling in realtime data that we want the SNOMED inference rules to help us discover new knowledge with. No PHI in Email: PointClickCare and Collective Medical, A PointClickCare Company, policies prohibit sending protected health information (PHI) by email, which may violate regulatory requirements. If sending PHI is necessary, please contact the sender for secure delivery instructions. Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
