r/OntologyEngineering • u/Goldziher • 2d ago
Business Semantics Would you model task applicability as a relation separate from scope?
I maintain ai-rulez and hit a modeling problem while testing retrieval of workflow instructions. In a synthetic fixture, the user asks for an outbound dispatch code while looking at an inbound returns worksheet. Scope filtering correctly excludes the outbound instructions, but a related inbound workflow is still visible. The model sometimes chooses that workflow anyway.
I’m considering representing three separate facts: the requested operation is Dispatch, the worksheet is an InboundReturn, and a workflow is applicable only when it supports the requested operation and accepts the worksheet type. Matching the path would establish where to look. It would leave applicability to those other facts. If the operation or worksheet type is unknown, the system could ask for clarification instead of treating the nearest match as applicable. This is a design question, not a feature I’ve shipped.
For those of you modeling business operations, would you put that applicability relation in the ontology, use the ontology for types and a separate rule for applicability, or model it another way? I’m particularly interested in representing unknown versus explicitly incompatible inputs.










