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:alternative"

The data is provided in different forms.

Definitions

<element name="alternative" type="b:Alternative" />

<complexType name="Alternative">
  <sequence>
    <group ref="b:data" />
  </sequence>
  <attribute name="name" type="NMTOKEN" use! />
</complexType>

Description

There can be many reasons to specify alternatives, and those can be different in many, many ways. For instance:

• different protocols to fetch the same data;
• one source provides the data as single bytes, the other as part of a packages; or
• one version contains a rare encoding or compression algorithm, where the other uses none, hence is larger;

The user may give preferences for one alternative (by name), or the application MAY decide based on preference for supported algoritms and such. Basically, the automated systems will attempt the alternatives in order (until we design a better algorithm).

Examples

<unit>
  <content>
    <size>234141</size>
    <alternative name="via_http">
      <fetch>
        <location href="https://a.nl/xyz" />
      </fetch>
    <alternative>
    <alternative name="via_s3">
      <fetch>
        <location href="s3://a.nl/xyz" />
      </fetch>
    </alternative>
  </content>
</unit>