Changes between Version 11 and Version 12 of TemplateImplementationModelling
- Timestamp:
- 07/09/09 10:19:47 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TemplateImplementationModelling
v11 v12 16 16 Those points considered agreed as implementable needs are summarised here. (Rationale leading to these are found in the discussion and comments below.) 17 17 18 A. In order to maintain the maximum potential exploitation beyond the scope of ISO15926, Part2, Part7, Part8 and Part9 will remain as unconstrained as possible, eg as close to generic modelling, first order logic and native W3C standards as practicable.18 A. In order to maintain the maximum potential exploitation beyond the scope of ISO15926, Part2, Part7, Part8 and Part9 will remain as unconstrained as possible, eg as close to generic ontological modelling, first order logic and native W3C standards as practicable. 19 19 20 20 B. In order to achieve effective, efficient, performant, reliable and manageable implementations in the ISO15926 industrial domain, constraints will be added through reference content ("RDL Items") and content rules. (''There remain choices about whether such rules are implemented in content, in functional code, or in verifiable processes. The more they can be implemented in the content itself, the less reliance there will be on code and processes, but ... '')