Inclusion of External Vocabularies
Copyright © 2015 Open Geospatial Consortium 37
Adopt the term and its definition Quote the term
Include the external vocabulary Suffice to say that in the context of writing SBVR rules with a conceptual schema
providing most of the vocabulary
7
these approaches essentially represent a schema import. Qualification of a term is only needed in case that the rule context of the term
does not uniquely identify the vocabulary that the term belongs to. For the example, this means that “theEvent” can be used without using “event:” as qualifier, because the core
AIXM schema does not contain a property or association named “theEvent”. Qualification can be achieved in different ways:
Using qualified names as in XML – example: event:theEvent Using a UML style – example: {DNES application schema name}::theEvent
Using a namespace identifier often used in [1] – example: theEvent [DNES namespace]
The latter may be easier to read and write for someone who is not familiar with XML. In order for a tool to recognize terms that belong to an external schema, the tool must
know that schema. In order to recognize DNES terms, the tool would therefore need to know all classes that belong to the conceptual schema of DNES, their inheritance
relationships, their attributes and associations, as well as any schemas that DNES imports. The best way to achieve this is to provide a consolidated UML model to the tool,
with all these details readily available. The consolidated model would include the core AIXM schema as well as the DNES schema plus any imported schema.