Core Component Registration vs. Serialization

["Chiusano Joseph" <chiusano_joseph@bah.com>]

All,

I'd like to offer a quick clarification for us on the issue of Core
Component registration vs. serialization (i.e. XML representation of
Core Components), as there might be some perception that the two somehow
completely overlap and are completely dependent upon each other.

These two concepts are, in some ways, orthogonal to each other.

That is, the rules for serializing Core Components in XML are - of
course - in many ways dependent on those for registering Core
Components; that is, if the registration of Core Components did not
clearly enable a serialization process to recognize an entity called a
"BCC", an entity called a "BBIE", etc., then the process would not work
well.

However, the "rules" for registering Core Components can allow for a BCC
to be registered first by itself (i.e. without being associated with an
ACC), yet the rules for serialization can (and must!) stipulate that a
BCC **cannot be serialized** without being associated with an ACC. If
this stipulation for serialization did not exist, then XML documents
could contain (for instance) only a single element called "Country.
Identifier", which is not good.

I hope this helps to clear this issue up.

Thanks,
Joe