Home

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

MS Concept

• prefix: msc:
• schema: b:

Categories:

• constants
• documentation
• identities
• stores

collections:

• c:unit_set

Category: collections

Collections describe places where to fetch data. These data-sets may be very large or very small. Somewhere, your application needs products to work with. How to design your products is your art. How you want to distribute your products is also your own decision. MSI standardizes the way your decisions are denoted.

The hierarchical organization:

• some service publishes products, as response to queries;
• each product publication contains some administrative information, directly available;
• each product MAY also contain parts, which can be seen as sub-products;
• each product can be retrieved from one or more collections;
• collections MAY be wrapped in collection of collections; and
• the top-level collection is placed in publications, which are available via one or more stores.

For instance: your have a car sales company. Your products are cars. The cars are constructed on demand. In a garage (service), your customer (client) asks for information about all cars of a certain brand. The garage responds (via a publication) with five different models: five products. Those products require some parts which are distributed separately: somewhere is a collection of wheels, somewhere else are the windows and the screen wipers. Those collections of parts are to be collected from different stores. Stores usually offer multiple collections, and some collections are available from many stores.

• See the extended example expressing the CommonCrawl huge data collection.

Schema components

c:unit_set

Rules for set of b:unit objects within a c:collection.