Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Structure for Communication (Guide) #55

Open
Tracked by #74
ssteinbuss opened this issue Sep 28, 2022 · 0 comments
Open
Tracked by #74

New Structure for Communication (Guide) #55

ssteinbuss opened this issue Sep 28, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request status:in-progress issue has been assigned and is currently being worked on

Comments

@ssteinbuss
Copy link
Member

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

currently out of scope

part of the system layer in RAM

What has to be realized into a solution and not part of the communication:

  • Policy enforcement would be part of the data plane to be realized and is not part of the communication
  • Cyber security assessments are part of the system architecture
  • Monitoring of policies.

Originally posted by @ssteinbuss in #45 (comment)

@ssteinbuss ssteinbuss self-assigned this Sep 28, 2022
@ssteinbuss ssteinbuss added enhancement New feature or request status:in-progress issue has been assigned and is currently being worked on labels Sep 28, 2022
@ssteinbuss ssteinbuss linked a pull request Sep 28, 2022 that will close this issue
@ssteinbuss ssteinbuss added this to the Communication Guide v2 milestone Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request status:in-progress issue has been assigned and is currently being worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant