Home

• explain
• command-line
• schemas
  • b: ms: base
  • c: msc: concept
• contact

MS Base

• prefix: ms:
• schema: b:

Categories (Data):

• constants
• documentation
• definitions
• payloads
• units
• values

Categories (Governance):

• collections
• namespaces
• rules
• server

payloads:

• b:alternative
• b:attachment
• b:blob
• b:checksum
• b:content
• b:data
• b:fetch
• b:location
• b:native
• b:packaged
• b:param
• b:part
• b:payload
• b:preview
• b:source

Schema element "b:data"

Abstract base-class for various data processing elements.

Definitions

<group name="data">
  <sequence>
    <group   ref="b:mediatype" />
    <element name="license" type="b:Constant"   [0..1] />
    <element name="size"    type="unsignedLong" [0..1] />
    <element ref="b:checksum"  [0..∞] />
    <!-- element ref="b:signature" [0..∞] TBD -->
    <!-- element ref="b:encrypted" [0..∞] TBD -->
    <choice>
      <element ref="b:blob"       />
      <element ref="b:fetch"      />
      <element ref="b:source"     />
      <element ref="b:packaged"   />
      <element ref="b:attachment"  [1..∞] />
      <element ref="b:alternative" [1..∞] />
      <element ref="b:part"        [1..∞] />
    </choice>
    <element ref="b:preview" [0..1] />
  </sequence>
</group>

Description

Elements which extend this describe processing actions needed to undo transport wrappings. Processors have hard-coded algorithms to perform these tasks.

The meta-data, size, checksum, signatures, and encrypted facts describe the result of the data-apply or data-source activities.

• b:fetch, download via a browser-like user agent;
• b:resource, contained in another Unit;
• b:blob, inlined in this Unit; and
• b:attachment, transmitted as bytes in the same connection, but outside a Unit wrapper. Especially: it is not serialized as XML or JSON.
• b:alternatives, describes multiple versions of the same content data. The user must make a choice based on its own features and the data presented.