Home

• explain
• schemas
  • b: ms: base
  • c: msc: concept
• contact

Explain

• Compare
• Base
• Concept

Implementation:

• Messages
• Formats

Infrastructure:

• Components
• Network

Explaining Meshy Space

Meshy Space is really different from existing concepts. It is shown not to be easy to explain to technical people, because people get easily side-tracked on details before getting the full picture.

A quick start:

• The bigger picture, a bit more about the technical motives;
• Compare Meshy Space with other protocols;
• Contact us when you want to have a full (1 hour) introduction.

Meshy Space extends existing standard ways in which services communicate with modern needs: data maintenance, storage and processing sharding, legal aspects, authentication, and privacy. It standardizes interface components required by new (EU) law.

• Mechanisms in Base (object sharing)
  • Life-cycle management of Units by the Collector;
  • Versions and revisions of data call for design decisions;
  • Namespaces and prefixes;
  • Expressions and Selectors;
  • Voting in Collection maintenance;
  • Notifications and Filters;
  • Resources and Storage;
  • TODO: Authentication and Access-rights
   
• Mechanisms in Concept (object governance)
  • Groups and personal proven identities
  • Contracts, privacy, GDPR, jurisdiction, authentication, payments, and more.
  • (Micro-)payments to finance maintenance, drive investments, and fight spam.
  • TODO: Wallets and Trusted Third Parties (TTPs)
  • TODO: Mimicking processes in your organization
   
• Implementation
  • Messages: how the client-server message are constructed;
  • Formatting of messages in XML or JSON, or any other format you prefer;
   
• Infrastructure based on multiple Collections
  • Components: the way services are organized;
  • Network dynamics
  • TODO: guide to building a service yourself