This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIM based ITS"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 5: | Line 5: | ||
Characteristics of instances that conform to this ITS | Characteristics of instances that conform to this ITS | ||
*All structured attributes (e.g. classCode, moodCode) have to be present in all instances | *All structured attributes (e.g. classCode, moodCode) have to be present in all instances | ||
| − | *The XML element names only serve to provide syntax, they carry no semantics, and are not used in determining the semantics of the artefact content. | + | *The XML element names (related to classNames, not attribute names) only serve to provide a syntax, they carry no semantics, and are not used in determining the semantics of the artefact content. |
==Transformation between the XML ITS R1 and the newly proposed RS XML ITS (MS-RS cell transition)== | ==Transformation between the XML ITS R1 and the newly proposed RS XML ITS (MS-RS cell transition)== | ||
Revision as of 14:08, 17 January 2009
The RS XML ITS is a term used by the RIMBAA WG for an ITS that is based on 'pure RIM semantics', i.e. an ITS that defines an XML syntax which allows for the XML to be processed solely based on its contents (and not on Class Clone names, or knowledge of templates/interactions used).
Analysis
Characteristics of instances that conform to this ITS
- All structured attributes (e.g. classCode, moodCode) have to be present in all instances
- The XML element names (related to classNames, not attribute names) only serve to provide a syntax, they carry no semantics, and are not used in determining the semantics of the artefact content.
