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) (New page: category:RIMBAA Issue 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 ...) |
Rene spronk (talk | contribs) |
||
| Line 1: | Line 1: | ||
[[category:RIMBAA Issue]] | [[category:RIMBAA Issue]] | ||
| − | 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). | + | 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== | ==Analysis== | ||
Revision as of 20:26, 16 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 only serve to provide syntax, they carry no semantics, and are not used in determining the semantics of the artefact content.
