OntoDL Statement: define
Syntax
| DefinitionStatement | := | define TypeName ObjectName DefinitionBody | ||
| ObjectName | := | Name | ||
| DefinitionBody | := | { FullDefinition * } | ||
| | | = QualifiedConcept | |||
| | | = InternalReference | |||
| Fulldefinition | := | DefineStatement | ||
| | | DefaultStatement | |||
| | | SetStatement | |||
| | | PredicateStatement | |||
| | | SetAsTableStatement | Must be formatted as 2-column MS Word table using style "OntoDL" | ||
| SetAsTableStatement | := | PropertyName (($)? Text | The prefix "($" advises the OntoDL interpreter to consider the provided text as a string (which will not be further processed) | |
| | | PropertyName InternalReference | |||
| PropertyName | := | Name |
Description
The define statement is used for introducing a new named object to OntoDL. Upon introduction a new object is given a name and assigned a type. These properties are fixed through the define statement and cannot be changed afterwards. The immediate binding of a new object to a type is important because not only the object's behavior but even the way you may use that object within OntoDL is determined by its type. The table below lists, how you may further define objects of the defined OntoDL types.
| type | definiton | specific behavior |
|---|---|---|
| codesystem | full definition | exported as a FHIR ValueSet resource (or FHIR STU-3 Codesystem resource) |
| system | full definition, internal reference | ID and version information goes into references to external code systems |
| concept | full definition, internal reference, qualified concept | exported as part of a code system unless given a silent name |
| predicate | full definition | exported as concept reference unless given a silent name |
| property | full definition | exported as string reference unless given a silent name |
