Community
Participate
Working Groups
A reconciliation taxonomy scheme describes a common set of identifiers on entities/classes. For example, host name can be an identifier of a computer system described in a reconciliation taxonomy scheme. Adopters or consumers of a CMDBf framework will often need to describe a mapping between properties of a native model languages and the properties of a schema describing a reconciliation taxonomy. For example, a host name may map to one or more fields in a native model language used by an MDR. The purpose of this enhancement is to describe an efficient and simple mechanism that allows adopters to describe this mapping. A transformation engine can use the mapping to transform a CMDBf query conforming to a reconciliation taxonomy to one that uses properties of a native model language.
This will be a utility that can be leveraged by any component that intends to do a transformation of a query in reconiliation taxonomy terms to native data model terms. Except for a few assumptions, this tool will be a generic model 2 model transformation. Mark W. suggests investigating the M2M project to determine if it can be used.
At the Detroit F2F we agreed to do this enhancement request. Joel: Can we use QVT?
This is currently unassigned to an iteration. Is this on the slate for i8, or do we defer to i9?
(In reply to comment #3) > This is currently unassigned to an iteration. Is this on the slate for i8, or > do we defer to i9? > I was hoping the F2F meeting would address that question. There doesn't seem to be anything in RM that is of higher priority. Assume i8 at this point unless something else pops up.
Targeting to i10 based on AG call on Jan 16/08
Re-targeting to future based on a discussion I had with Mark on March 6th, 2008. The requirement for this is not clear at this point. More investigation is needed to determine the scope of this enhancement.
Should this be in Data Collection instead of Resource Modeling?
Reassigning to the default owner of DataCollection.
