DECOR-rules - Revision history

Kheitmann: /* element/@strength */

2017-12-19T13:01:37Z

‎element/@strength

2017-12-14T21:53:04Z

‎element/@strength

2017-09-26T08:32:26Z

‎Co-Occurance: typo

2016-05-21T16:00:26Z

2015-11-27T20:10:12Z

‎element/@id

2015-11-27T20:09:30Z

‎attribute/vocabulary/@valueSet

2015-11-27T20:05:50Z

‎element/@id

2015-11-27T20:05:31Z

‎element/@id

2015-03-29T20:35:27Z

‎element/@datatype

2015-01-22T18:22:37Z

‎constraint

@@ Line 407: / Line 407: @@
 ====element/@strength====
-This optional attribute specifies the vocabulary strength for data types that support that feature. Examples include CD, CE, CV and CO. Values are required, extensible, preferred and example. Default is required. Mismatches with required lead to validation errors (SHALL logic). Mismatches with extensible lead to validation warnings (SHOULD logic). Mismatches with preferred lead to validation information messages (MAY logic). Mismatches with example don't have any validation consequences.
+This optional attribute specifies the vocabulary strength for data types that support that feature. Examples include CD, CE, CV and CO. Values are ''required'', ''extensible'', ''preferred'' and ''example''. Default is ''required''. Mismatches with required lead to validation errors (SHALL logic). Mismatches with extensible lead to validation warnings (SHOULD logic). Mismatches with preferred lead to validation information messages (MAY logic). Mismatches with example don't have any validation consequences.
 The formerly supported values CNE (Coded No Extensibility) and CWE (Coded With Extensibility) are deprecated as of December 2017. Specification CNE is handled as required and CWE is handled as extensible.

@@ Line 407: / Line 407: @@
 ====element/@strength====
-This optional attribute specifies the vocabulary strength for data types that support that feature. Examples include CD, CE, CV and CO. Values are CNE (Coded No Extensibility) and CWE (Coded With Extensibility). Default is CNE. Mismatches with CNE lead to validation errors (SHALL logic). Mismatches with CWE lead to validation warnings (SHOULD logic)
+This optional attribute specifies the vocabulary strength for data types that support that feature. Examples include CD, CE, CV and CO. Values are required, extensible, preferred and example. Default is required. Mismatches with required lead to validation errors (SHALL logic). Mismatches with extensible lead to validation warnings (SHOULD logic). Mismatches with preferred lead to validation information messages (MAY logic). Mismatches with example don't have any validation consequences.
 ====element/@id====

@@ Line 1,411: / Line 1,411: @@
 Co-occurance means the presence of some data depending on the presence or value of some other data. There are intra-instantial co-occurances where a condition applies to one single instance, and extra-instantial co-occurances where the presence of data in an instance is influenced by external factors (outside the very same instance).
-In thsi specification, only intra-instantial co-occurances are handled.
+In this specification, only intra-instantial co-occurances are handled.
 {{BeginBlueBox|Example: Amnionicity and Chorionicity}}

@@ Line 7: / Line 7: @@
 ==Meta data of templates (rule elements)==
 The following table gives an overview of the template meta data structure.
-{| class="artdecor"
+{| class="artdecorwiki"
 | align="center" style="background:#f0f0f0;"|'''Item'''
 | align="center" style="background:#f0f0f0;"|'''DT'''
@@ Line 105: / Line 105: @@
 According to the Business Requirements for Template Registries ART-DECOR uses the following subset of status codes of a template (in bold).
-{|class=artdecor
+{|class="artdecorwiki"
 |-
 ! statusCode !! Description

@@ Line 410: / Line 410: @@
 ====element/@id====
-This optional attribute is an id that allows the element to be uniquely identified within this version of the template (template ''id'' and ''effectiveDate''). This is typically done using an OID. The id can be used link between a template element and an associated concept for example in a data set or functional model.
+This optional attribute is an id that allows the element to be uniquely identified. The same id cannot occur on any other element or attribute within this version of the template (template ''id'' and ''effectiveDate''). This is typically done using an OID. The id can be used link between a template element and an associated concept for example in a data set or functional model.
 {{BeginBlueBox|Example}}
 A CDA recordTarget has an element "cda:birthTime" that is associated with the birth time of the patient. If the birthTime template element gets an id, it can be linked to a concept representation for example in a data set that shows the functional perspective.

@@ Line 717: / Line 717: @@
 </valueSet>
 </syntaxhighlight>
 ===choice===

@@ Line 405: / Line 405: @@
 {{EndBlueBox}}
 A complete list of the supported data types can be found [[Datatypes|here]].
 ====element/@id====

@@ Line 833: / Line 833: @@
 An optional and repeatable free text, natural language and non computable description of constraints applicable in this context. May contain markup and supports the @language attribute. Occurs max once only per language. Format: string with optional HTML tagging (XHTML). Supports @language, see [[DECOR-project#@defaultLanguage|@defaultLanguage]].
-You MAY also convey the same constraints in the [[#template.2Fdesc|&lt;desc&gt;]] element but separating them out into constraints allows different rendering in your publications making the constraints stand out more than they would in &lt;desc&gt;.
+You MAY also convey the same constraints in the &lt;desc&gt; element but separating them out into constraints allows different rendering in your publications making the constraints stand out more than they would in &lt;desc&gt;.
 <syntaxhighlight lang="xml">