indication of what kind of mapping is contained, e.g. "CUF", "TUF", "basadv", ...
Applicable for: TUF, Mapping basic advanced, NE100 to eCl@ss
Tells if the equivalence lead to an incompatible change
In case of basic to advanced mapping this would be bijective
Prefix notation for expression of logical combinations without parentheses.
Apply a XQuery/XPath fn:replace regular expression on the value of the source to obtain the value of the target. subject is expected from "source"
An optional string to be added between the concatenated values
Apply a XQuery/XPath fn:replace regular expression on the value of the source before using the result. See http://www.regular-expressions.info/xpath.html
the format string used to define the value production
where to take value from and what to take as value
target application shall take the value (in the optionally specified locale).
target application shall look up a certain attribute in the dictionaryand take the string value of that attribute.
target application shall look at the numeric value (concatenacted with unit if applicable) and treat as string.
property from which the input for the formatting is taken
Apply a XQuery/XPath fn:replace regular expression on the value of the source before using the result.
Includes move / split / join
needed for move. Set types are not applicable for move:
- source is class to be moved
- target is parent class where source is moved
- new contains code where class is moved to
Instead of a type name also an IRDI may be specified for the type.
restricted to the same mapping types as in BMEcat 2005.
target_code is an accessory of source_code
target_code is a base product (i.e. the packaging neutral description) for source_code
target_code is a part of of source_code
target_code is has a different order unit but shared base product with source_code
target_code is a follow up of source_code
target_code is required to be ordered when source_code is ordered
target_code is a possible alternative to source_code (weak suggestion, no guarantee)
target_code can only be ordered when source_code is ordered
target_code is a spare part for source_code (can be replaced separately)
target_code is related to source_code with no clear meaning
mapping can be interpreted injective, surjective or bijective?
e.g. "move", "split", "join"
informative remark on the mapping
In case a release has a release Identifier it should be used.
a human readable name, e.g. "eCl@ss"
a human readable version number, e.g. "7.0"
ref as IRDI should be given whenever possible, however leaving not required for cases where there is no IRDI
Mapping code sets on both sides has weak semantics and should be avoided. However this kind of entry may be needed, e.g. for expressing CMAP many-to-many mapping cases.
Name of alternative reference, e.g. "hierarchical_position"
Value of alternative reference, e.g. "14010101"