Issue 9168: Align mapping of tags to MOF2.0                                                                                                                                                                         (mof2idl-ftf)
Source: Fraunhofer FOKUS (Mr. Michael Soden, soden@ikv.de soden@fokus.fraunhofer.de)
Nature: Uncategorized Issue
Severity: 
Summary: The mapping of tags should state explicitly where the information modeled in a tag lands in the mapped IDL
Resolution: 
Revised Text: Resolution:
Add the role of tags in service in section 5.3.1 "Mapping of MOF and Service Mapping" on page 5 and redefine rule 40.
Added to section 5.2.1
This specification separates the mapping of core MOF2.0 concepts from those of services. Although Reflection is available in MOF2.0 Core, it is considered in the mapping as a standard service. Non standard services can be plugged into the mapping through MOF Tags.
Added to section 6.3.5
As stated earlier, tags are used to denote services provided by the generated components. Tags for standardized MOF Services such as Reflection need not to be explicitly attached to model elements.
	Standardized tags for the IDL mapping define standardized service interfaces. These interfaces are supported through facets at the component. If a non-standardized tag is attached to a model element, the component generated for that element is extended to provide a facet of the type denoted by the tag value. The name of the tag is mapped to the name of the facet.
It is the responsibility of the modeler to provide valid IDL identifiers in the name and value attributes of the tag. The facet type denoted by the tag value must be fully qualified.


Actions taken:
November 15, 2005: received issue
March 8, 2006: closed issue
Discussion: 

End of Annotations:=====
MG Issue No: [Temp21]
Title:	Align mapping of tags to MOF2.0
Source:
Michael Soden, soden@ikv.de	
Summary:
The mapping of tags should state explicitly where the information modeled in a tag lands in the mapped IDL.
 
Discussion:

Resolution:
Add the role of tags in service in section 5.3.1 .Mapping of MOF and Service Mapping. on page 5 and redefine rule 40.
Added to section 5.2.1
This specification separates the mapping of core MOF2.0 concepts from those of services. Although Reflection is available in MOF2.0 Core, it is considered in the mapping as a standard service. Non standard services can be plugged into the mapping through MOF Tags.
Added to section 6.3.5
As stated earlier, tags are used to denote services provided by the generated components. Tags for standardized MOF Services such as Reflection need not to be explicitly attached to model elements.
	Standardized tags for the IDL mapping define standardized service interfaces. These interfaces are supported through facets at the component. If a non-standardized tag is attached to a model element, the component generated for that element is extended to provide a facet of the type denoted by the tag value. The name of the tag is mapped to the name of the facet.
It is the responsibility of the modeler to provide valid IDL identifiers in the name and value attributes of the tag. The facet type denoted by the tag value must be fully qualified.

Disposition:	open
:Wq