Changes between Version 2 and Version 3 of CMDI 1.2/Cues/Localised documentation

Timestamp:

12/02/13 12:43:58 (11 years ago)

Author:

twagoo

Comment:

--

CMDI 1.2/Cues/Localised documentation

@@ -11 +11 @@
 == Proposed solutions ==
 
-Depending on how documentation texts will be represented in component specifications, add an (additional) attribute to the documented attribute, component or element (see [[CMDI 1.2/Cues/Component documentation|Documentation on Components and Attributes]]). The most elegant solution would be to refactor the current Documentation attribute into a child element with the xml:lang attribute.
+Depending on how documentation texts will be represented in component specifications, add an (additional) attribute to the documented attribute, component or element (see [[CMDI 1.2/Cues/Component documentation|Documentation on Components and Attributes]]). The most elegant solution would be to refactor the current Documentation attribute into a child element with the xml:lang attribute. In the XSD this would be transformed into an appInfo element.
 
 === Pros ===
 
-Pros of this solution
 
 === Cons ===
 
-Cons of this solution
+If using child element/appInfo approach: not so much backward compatible (place of documentation changes), relatively large change for tools (but not critical as long as they ignore the new element)
 
 === Centre impact ===
 
-* Affected tools
-* Impact on instances
+* Tools that use the documentation (presumably only editors: Arbil, Proforma?)
+* No impact on instances
 
 === Implementation examples ===
 
-* Implementation on model level
-* Implementation on instance level
+Component specification example:
+{{{#!xml
+TODO
+}}}
 
 == Tickets ==