search

International-Data-Spaces-Association / IDS-RAM_4_0

Focusing on the generalization of concepts, functionality, and overall processes involved in the creation of a secure 'network of trusted data' , the IDS-RAM resides at a higher abstraction level than common architecture models of concrete software solutions do. The document provides an overview and dedicated architecture specifications.
Creative Commons Attribution 4.0 International
38 stars 27 forks source link

213 Differentiate broker services and standardize #214

Closed tom-rm-meyer-ISST closed 1 year ago

tom-rm-meyer-ISST commented 1 year ago

Handling of the term "metadata broker":

Note: Caps have been ignored (metadata broker, Metadata Broker)

tom-rm-meyer-ISST commented 1 year ago

Proposal to solve https://github.com/International-Data-Spaces-Association/IDS-RAM_4_0/issues/213

tom-rm-meyer-ISST commented 1 year ago

We need to agree on a uniform spelling. "Metadata Broker" vs. "metadata broker" eliminates already a huge number of previous variations :-) Proposed updates are fine with me.

That's a good point I was thinking about, too. Sometimes the text refers to components as names - therefore they were written with starting capitals (such as "Metadata Broker", "Participant Information System"). Sometimes they weren't. I just sticked to the respective chapter (well, they're written by different persons).

As a consequence, I would align on calling it Metadata Broker in uppercase.

In an additional issue, it could make sense to introduce a naming convention, couldn't it? Something like refering to names, concepts and entities of the IDS RAM as upper case (like Contract Offer, Usage Policy) and add something like a preamble to explain it. Maybe this proposal also is overengineering because it's a cosmetical issue.

ssteinbuss commented 1 year ago

Editorial changes are to be released immediately. Changelog needs to be updated.