Book page

2 - Setup of ID/Trust, Catalogues and Vocabulary

Rick Santbergen
Rick Santbergen • 2 August 2024

2 - Setup of ID/Trust, Catalogues and Vocabulary

Description

Setup of ID/Trust, Catalogues and Vocabulary

L0 - Business ProcessStatus: Proposed
Associated L1s - High Level Requirements
  • 2.1 - Catalogue fields
    Simpl shall offer a list of mandatory and optional attributes ...

    See more details

  • 2.2 - Catalogues of Data/Application/Infrastructure
    Simpl shall offer a catalogue into which datasets, ...

    See more details

  • 2.3 - Support adding and publishing of vocabularies
    Simpl shall provide the means to first add the vocabulary ...

    See more details

  • 2.4 - Create properties of Data/Application/Infrastructure catalogues
    The Dataspace Governance Authority shall be able to create ...

    See more details

  • 2.5 - Manage vocabularies
    The Dataspace Governance Authority shall ...

    See more details

  • 2.6 - Update properties of Data/Application/Infrastructure catalogues
    The Dataspace Governance Authority shall be able to ...

    See more details

  • 2.7 - Catalogue of services
    Simpl shall provide a catalogue of infrastructure-related services ...

    See more details

  • 2.8 - Data/Application/Infrastructure Catalogue sharing
    The Dataspace Governance Authority shall be able to share its ...

    See more details

  • 2.9 - Provide default vocabularies
    Simpl shall provide by default a collection of widely used vocabularies ...

    See more details

  • 2.10 - Synchronization across the Federation of Catalogues
    Catalogue of Data and Application should allow for federation with ...

    See more details

     

Back to Simpl requirements overview

 

Comments (1)

Rick Santbergen
Rick Santbergen

Moderator note: Comments are from the previous discussion platform.

Submitted by Luis Carlos BU… on Mon, 25/03/2024 - 14:33
The description could be more detailed:

SIMPL should allow the provision of user-friendly IT service catalog functions to allow browsing through available services, modules, support, users …

The middleware will allow different views depending on the user role and the configuration of the Dataspace. To this end, the middleware will allow easy installation of the modules the Data Space owner decides and easy setting up of the catalog.

Submitted by Paul-Marie Abchi on Fri, 05/04/2024 - 12:19
The catalog, should be stuctured with a Scheme that helps the user to perform the searches, through well defined categories. It is very important in the design to have stackholders in touch with the final users reality.


Please log in or sign up to comment.