This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Blocked Context Conduction Incomplete"
Jump to navigation
Jump to search
(Created page with "{{MnM Open Hot Topic}}") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{MnM Open Hot Topic}} | {{MnM Open Hot Topic}} | ||
| + | '''BlockedContextConduction''' attributes in the RIM are currently (4/2013) unusable without further methodology rules for: | ||
| + | #The RIM constraint is currently a ConceptDomain; need to constrain that and bind it to the "default" conductible attributes; | ||
| + | #How can such a constraint be modified downstream (presume it is '''only''' by reducing the value set in question (or is it by adding???) | ||
| + | #These attributes are not currently properly constrained in the schemas, particularly as regards the enumerated type definition for a repeating XML attribute | ||
Latest revision as of 21:54, 10 April 2013
This page documents an Open MnM Hot Topic, i.e. a methodology issue requiring a resolution from Modeling and Methodology.
BlockedContextConduction attributes in the RIM are currently (4/2013) unusable without further methodology rules for:
- The RIM constraint is currently a ConceptDomain; need to constrain that and bind it to the "default" conductible attributes;
- How can such a constraint be modified downstream (presume it is only by reducing the value set in question (or is it by adding???)
- These attributes are not currently properly constrained in the schemas, particularly as regards the enumerated type definition for a repeating XML attribute
