ems:Map
Metric entities:
ems:Measure,
ems:MeasureDistribution,
ems:FactTable,
ems:FactDistributionTable,
ems:Map,
ems:WorkBreakdownStructure
Description
Some key dimensions may define standard dimension member URIs which are used for data interchange. However, users may wish to use custom values. The ems:Map resource lets you define how custom values are mapped to standard URIs. You can include an ems:Map resource in the description of a dimension column of a fact table.
We make the simplifying assumption that this mapping is many-to-one, that is, one or more custom dimension values may be mapped to the same standard dimension value. A map may contain one or more of these mappings, but each custom dimension value must map to exactly one standard dimension value.
Properties
An ems:Map resource has the following properties:
Property |
Range |
Type |
Occurrence |
Edits |
Description |
dcterms:title |
datatype |
xhtml:span |
exactly-one |
read-write |
A short title for the map. |
ems:mapping |
local inline resource |
ems:Mapping |
one-or-more |
read-write |
The mapping from a custom to a standard dimension value. |
ems:Mapping
An ems:Mapping resource has the following properties:
Property |
Range |
Type |
Occurrence |
Edits |
Description |
ems:from |
datatype |
xsd:string |
exactly-one |
read-write |
The custom dimension value being mapped. |
ems:to |
resource |
ems:DimensionMember |
exactly-one |
read-write |
The standard dimension value that the custom dimension value is mapped to. |
ems:from
The value of ems:from MUST be unique within its enclosing ems:Map resource.
Example
For example, when describing effort, role is a key dimension. In order to simplify the interchange of effort estimates and measurements, EMS 1.0 defines a small set of
standard roles. However, software estimation tools may support a larger set of roles, or allow users to define new roles. The effort associated with these custom roles will be mapped to the standard roles for purposes of interchange. We refer to a mapping of custom roles to standard roles as a role map.
For example, suppose a customer uses the custom roles Development Manager and Product Manager, and maps these both to the standard role Manager. In addition, the customer uses the custom roles Functional Tester, Performance Tester, and System Tester and maps these to the standard role Tester. The RDF/XML representation of this role map is as follows:
<?xml version="1.0"?>
<ems:Map xmlns:ems="http://open-services.net/ns/ems#"
xmlns:dcterms="http://purl.org/dc/terms/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<dcterms:title rdf:parseType="Literal">Map from Custom to Standard Roles
</dcterms:title>
<ems:mapping>
<ems:Mapping>
<ems:from>Development Manager</ems:from>
<ems:to
rdf:resource="http://open-services.net/ns/ems/dimension-member#Manager" />
</ems:Mapping>
</ems:mapping>
<ems:mapping>
<ems:Mapping>
<ems:from>Product Manager</ems:from>
<ems:to
rdf:resource="http://open-services.net/ns/ems/dimension-member#Manager" />
</ems:Mapping>
</ems:mapping>
<ems:mapping>
<ems:Mapping>
<ems:from>Functional Tester</ems:from>
<ems:to
rdf:resource="http://open-services.net/ns/ems/dimension-member#Tester" />
</ems:Mapping>
</ems:mapping>
<ems:mapping>
<ems:Mapping>
<ems:from>Performance Tester</ems:from>
<ems:to
rdf:resource="http://open-services.net/ns/ems/dimension-member#Tester" />
</ems:Mapping>
</ems:mapping>
<ems:mapping>
<ems:Mapping>
<ems:from>System Tester</ems:from>
<ems:to
rdf:resource="http://open-services.net/ns/ems/dimension-member#Tester" />
</ems:Mapping>
</ems:mapping>
</ems:Map>
Comments
Add your comments here: