4.6 and 4.7: the BDO must be accessible to the information management services applying policy, which must be able to find the BDO for a given data object and the data and metadata for a given BDO, and resolve every URI used; referenced data and metadata must be unambiguous and globally accessible in the data-centric environment, and embedding metadata rather than referencing it is recommended. An encapsulating BDO has BindingInformation as its document root, should contain only Data elements and must support any data type; an embedded BDO is a child of the (extensible) data object with BindingInformation as its root and should use only internal DataReference elements; a detached BDO sits outside the data it references and should use only external DataReference elements. A null DataReference URI or a base URI dereferences to the document root, and fragment identifiers follow the rules of the declared content type.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.