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

Category: payloads

Usually, a b:unit has a content: the payload. This has two main variations:

• b:native payloads are (XML) message components which nicely integrate in the Unit structure. In these units, not only the wrapper, but also the payload data is defined in one of the Meshy Space schemas.
• b:content payloads produce bytes for user applications, like a picture.

Please see the examples to learn about ways to arrange the payload.

Schema components

b:alternative

The data is provided in different forms.

b:attachment

The data is transported in the same connection to the server, but as separate bytes.

b:blob

The data is included in this b:unit object itself.

b:checksum

One checksum on bytes.

b:content

Add any kind of data directly inside a unit.

b:data

Abstract base-class for various data processing elements.

b:fetch

Fetch the data from an external source, using a protocol which can be represented with a URI.

b:location

Refer to a external data source, relative to a resource or absolution.

b:native

Unpacked XML data from know namespaces.

b:packaged

Take an entry from the wrapped data.

b:param

Key-value pairs for constant parameters.

b:part

The data is composed of different parts.

b:payload

Base for different kinds of payloads: unit.type specific data.

b:preview

Some extracted information from the data, which may help performance and indexing.

b:source

Refers of the content of another b:unit to provide the requested data.