Commit b98bc657 authored by Rieks Joosten's avatar Rieks Joosten
parents 527a2450 2cc0dd1f
This diff is collapsed.
# BOC-1 - Project Summary of <!--subproject name-->
# BOC-1 - Project Summary of <!Data as Currency>
For more information, please contact:
......
# Template for Deliverable for the Pruductisation meeting of <!--your project>
# Template for Deliverable for the Productisation meeting of <!--your project>
<!--GENERAL ADVISE: Try to be brief, to the point, and concrete in your descriptions. Appropriately refer/link to your own work and/or that of others. -->
......@@ -12,12 +12,12 @@ Contact person details:
## PRODUCT PAGE
<!-- While creating contents for the following sections, please try to keep this section limited to a single page-->
### 1. Define your product
### 1. Define your product component(s)
The purpose of this section is to give readers a good idea of what you will be providing, so that they determine what you will be providing and whether or not that addresses their needs. So for each component that you will be providing, state:
- its name (so that we may refer to it)
- its function (one or two lines, and if possible, use the functions as defined in the eSSIF-Lab functional architecture)
- for every API the component provides:
- for every interface (API, protocol, ...) the component provides:
- its name
- its function
- any functionality that the component needs (to be provided by other components, which you or others may provide).
......@@ -48,8 +48,8 @@ The purpose of this section is to give readers an idea of the possibilities and
### 5. Demo
State the kind(s) of demo's that you will be providing and/or participating in to show that the interop as specified in the previous section actually works.
### 6. eSSIF-Lab Vision, Architecture, Terminology, APIs, and further Documentation
At the end of the project, a vision, architecture, terminology, APIs and other documentation should exist that results from a collaboration of the subgrantees and the project team. Currently, there is a draft vision and functional architecture that gives the readers a high-level idea of what the eSSIF-Lab infrastructure is about, and how it can be used in a business. Also, some terminology has been provisionally defined. There is little API and further documentation.
### 6. eSSIF-Lab Vision, Architecture, Terminology, interfaces, and further Documentation
At the end of the project, a vision, architecture, terminology, interfaces (APIs, protocols, ...) and other documentation should exist that results from a collaboration of the subgrantees and the project team. Currently, there is a draft vision and functional architecture that gives the readers a high-level idea of what the eSSIF-Lab infrastructure is about, and how it can be used in a business. Also, some terminology has been provisionally defined. There is little API and further documentation.
In order for this overall project deliverable to be delivered, state:
- what you think is needed (short, to the point)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment