> For the complete documentation index, see [llms.txt](https://mims.oascities.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mims.oascities.org/exchanging-data/capabilities-and-requirements.md). # Capabilities and Requirements ## **C1: Governance rules for the data sharing ecosystem can be defined** **Requirements:** **RC1.1** The orchestrator of a data ecosystem should be able to define a governance model (e.g. a rulebook) that outlines membership rules, the roles, responsibilities and obligations of ecosystem participants, and the overall principles that govern data exchange between them. **RC1.2** Members who participate in a data ecosystem should be aware of its governance model and any changes made to it. **RC1.3** The governance model should be easily comprehensible by all ecosystem participants. ## **C2: Terms and conditions for data sharing can be defined** **Requirements:** **RC2.1** Data providers are free to define terms and conditions under which they want their data to be exchanged. *(Note: Before sharing data assets, data providers should ensure they have adequate permission from data owners.)* **RC2.2** Terms and conditions for a data exchange should be described clearly and unambiguously so that they are easily understandable for data users. **RC2.3** Terms and conditions for a data exchange should be expressed through data licences or data sharing agreements based on well-defined templates or standards. **RC2.4** Terms and conditions should be in line with the overall governance model of the data ecosystem and must not conflict with it. *(Note: A data provider can decide not to participate in a data ecosystem if the underlying governance model is too restrictive or too permissive.)* ## **C3: Compliance with data sharing terms and conditions can be validated** **Requirements:** **RC3.1** The orchestrator of a data ecosystem must be able to ascertain compliance of its participants with the underlying governance model. **RC3.2** Data providers should be able to ascertain that the use of data by a data user complies with previously agreed-upon terms and conditions. **RC3.3** Data users should be able to ascertain that the data provider's supply of data follows previously agreed-upon terms and conditions. ## **C4: Available data assets can be discovered** **Requirements:** **RC4.1** Data users should be able to discover what data is available in a data sharing ecosystem without prior knowledge of it. **RC4.2** Data assets should be adequately described with metadata so that data users can make reliable decisions about their further intended use. **RC4.3** Metadata used to describe data assets should be based on well-defined, easy-to-understand description formats that are both human- and machine-readable. ## **C5: Ecosystem participants can be discovered** **Requirements:** **RC5.1** Ecosystem participants (e.g. data users and providers) should be able to discover each other within a data-sharing ecosystem. **RC5.2** Sufficient metadata about each ecosystem participant should be available to ascertain their trustworthiness relevant for data exchange. **RC5.3** Data providers should be able to reliably identify data users who want to access their data assets and verify their metadata before granting access. **RC5.4** Data users should be able to identify data providers who share data in a data ecosystem before accessing or using that data. **RC5.5** Ecosystem participants may also choose to remain anonymous if the governance model of the data-sharing ecosystem allows for it. In this case, RC5.1 to RC5.4 can be ignored. ## **C6: Data exchange can be agreed upon** **Requirements:** **RC6.1** Data users and providers should be able to agree to a data exchange and the terms and conditions associated with it (e.g. acceptance of terms, legal signature of an agreement, or negotiation). **RC6.2** Data users and providers should be able to terminate a previously agreed-upon data exchange in accordance with the terms and conditions associated with it. **RC6.3** Where possible, electronic means for the agreement and termination of a data exchange may be provided. ## **C7: New data currently not available can be requested** **Requirements:** **RC7.1** Data users should be able to express their interest in data assets currently unavailable in the data sharing ecosystem. **RC7.2** Data providers should be able to obtain requests made by data users for new data assets. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mims.oascities.org/exchanging-data/capabilities-and-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.