Farrukh Najmi wrote:
> A few special cases in CCTS mapping do not obviate the need for a
> generic mapping TN that covers most domain specific mapping and 90%+
> of CCTS.
> What is the downside of doing a generic mapping document as you see it?
>
The downside is that there are dependencies on the storage for what must
be serialized on the wire. If that information is not stored as per the
generic mapping, then the whole mechanism may not work. Each artifact
has different requirements for what must be serialized on the wire.
BIE's need to know what CC they came from, they also need to know the
contexts (UUID for a set of contexts) that lead to their existence,
CC's do not need to know the BIE's spawned from them, yet do need to
know there are BIE's and provide a mechanism (Classification tree?) for
others to locate the BIE for a specific set of contexts.
The set of contexts is also another huge problem. There may be 8-10
million. One BIE may be used for a range of contexts (example - all
french speaking countries and regions). Just creating that many
classifications will crash most registry implementations I know of or
make them unmanageably slow.
These are just a few of the potential problems.
Duane
