Versions Compared

Old Version 1

changes.mady.by.user Vineet Singh

Saved on

compared with

New Version Current

changes.mady.by.user Vineet Singh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Option 1: Time embedded in Data

Option 2: IDSCP2 in Apps

Option 3: Standardized App Inferface for UC

Description

  • Header in data that has details about the time constraints

  • The application is reading the data and enforcing it

  • IDSCP2 implementation to communicate between containers (metadata and headers in IDSCP2 manage usage control)

  • Other standard apart from IDSCP2 like REST

  • The interface consumes data, policy for implementation

Pros and cons

(plus)

Simplicity

(minus)

  • No possiblity to or very difficult to configure on protocol level

  • Not standardized, data format is app specific

(plus)

  • Standardized IDS messages

  • Configurable outside of app

(minus)

  • IDSCP2 implementation required within application

  • No passing of UC to apps implemented in Connectors yet, unknown effort

(plus)

  • Managable implementation effort

  • No full IDSCP2 implementation required, only REST server or similar

(minus)

  • To be standardized/ implemented, especially passing from Connector to App

Estimated effort

Status
colourGreen
titlesmall

Status
colourRed
titleVery Large

Status
colourRedYellow
titleVery Largemedium

Action items

  •  

Outcome