The IDS Specifications shall consist of 2 parts the components and communication (communication guide). the communication package should be structured as follows:

  # Proposal to move ahead with our work

distinguish between different packages:

Foundation

This is the common foundation for all subsequent activities

foundational standards (references)

please list relevant things here that we use that already exist.

Information Model

One common model that is used in every other package (dcat + odrl + IDS specifics (participant, connector, contract,...))

List of information models that we use + list of IDS-specific attributes/classes/packages/. use dcat use odrl use

Identities

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Trust Frameworks

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Policies (authorization and Policy Description)

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Data Sharing (Conector)

Contract Negotiation

part of the control plane

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Data Transfer

part of the data plane. How data is exchanged with focus on communication and not on how the data plane is built.

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Catalog (Publish and query meta-data)

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Registration

messages and data types:
protocols: state machines for message flows and interaction patterns:
API binding:

Audit logging

currently out of scope

Vocabularies