Search



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

include metadata that represent each of the allocated . The representing the namespaces are arranged in a single parent hierarchy, as follows:

Figure 30. Hierarchy for: Namespace concept (namespace concept)

In the above hierarchy, |Extension Namespace A {}| , |Extension Namespace B {}| and |Extension Namespace C {}| are all child namespaces of the 373872000 |Core Namespace| (representing the which does not have a , and uses short format SCTID (data type) to identify ). Also, |Extension Namespace B {}| is the parent namespace of |Extension Namespace D {}| and |Extension Namespace E {}| .

Each may only have one parent in the 370136006 |Namespace concept| sub-hierarchy.

The namespace hierarchy is used to constrain which content can be promoted from one to another without amending the SCTID (data type). Content may be moved (without amendment of SCTID (data type)) from an released by the owner of a child namespace to an released by the owner of a parent (or ancestor) namespace, as described by the | 370136006 |Namespace concept| sub-hierarchy.

Examples:

  1. A

    with an SCTID (data type) that includes

    |Extension Namespace D {}|

    may be moved to the

    maintained by the owner of

    |Extension Namespace B {}|

    without changing its SCTID (data type) , because this is a parent of the originating namespace.
  2. A

    with an SCTID (data type) that includes

    |Extension Namespace D {}|

    must not be moved to the

    maintained by the owner of

    |Extension Namespace C {}|

    because this is not parent (or ancestor) of the originating namespace. Therefore, to make this move the original

    must be inactivated and replaced by a new component with a new SCTID (data type) in target namespace.
  3. Any

    may be moved from any

    to the

    (subject only to formal acceptance that is a valid addition for international use).

have the following characteristics:

  • They are

    (either children or

    ) of

    370136006 |Namespace concept|

    .
  • The

    of each

    has the form

    Namespace {nnnnnnn} (

    ) where nnnnnnn is the seven digit Namespace-

    .
  • A

    associated with each

    has the form

    Namespace nnnnnnn
  • Where appropriate further

    may be included to identify the nature of the responsible organization .

When requesting a from , there will be a facility to optionally specify a parent for the new namespace.

To specify a parent namespace for an existing , please contact with details of your existing and its proposed parent .

CAUTION:

Once a has be allocated a parent in this hierarchy, further changes to this hierarchical are not permitted. This restriction is imposed to avoid changes that would undermine traceability of moves between namespaces.


Feedback
  • No labels