Moving Data Fabric out of community review

Dear Data Fabric people,
It is now the end of the community review period.
You have received some comments from Beth (reproduced for convenience
below).
Do you wish to update your charter based on these comments before
submission to TAB and Council?
Cheers,
Herman
I am a big fan the notion of data fabric into which services can plug
themselves, and am personally quite excited to see this come about.
Registries have well-known issues with staying current (e.g., failure of
UDDI and many other registry solutions that came about 5-8 years ago).
A different approach that doesn't suffer same centralized control
problems is to make the fabric more peer-to-peer like:* data fabric is
a minimalistic set of requirements by which services can plug into
(belong to) the fabric.*All services belonging to the Data Fabric must:
1. Be self-documenting -- a service contributes to the lifecycle of data
objects it handles and must keep track of the scientifically relevant
actions it performs on those data objects. The resulting log files are
periodically be sent to a provenance consolidator.
2. Track data objects through its service processing using one of the
well-known object identifier schemes
3. Identify itself as one type of service as drawn from an RDA- agreed
upon list of service types.
4. Implement an interface to a publish-subscribe system which serves as
the Data Fabric Control Plane. It is through the control plane that
the service broadcasts information about itself, and receives
information about the data fabric.
5. Periodically broadcast a heartbeat message. The message conveys the
timestamp, current status of the service, and the type of service that
the service provides. Service types are drawn from an agreed upon, and
minimal, list. The heartbeat message is conveyed on an
publish-subscribe system (such as AMQPhttp://www.amqp.org/) that every
service supports as minimal barrier to entry to belong to the fabric
Rules 3-5 constitute a very minimal Data Fabric Control Plane. The
Control Plane is a fibrous connectivity used only minimally to know what
is plugged into a data fabric and alive and what is not. It's not used
to move data or for services/users to interact. It's purely utilitarian
like the power grid: the power grid knows which homes are on the grid
and which are not; which currently have power and which do not. Why a
control plane? It does not suffer the currency problems known with
registries.
Finally, a minimal data fabric control plane has the nice feature of
allowing RDA to say things like*"The European Data Fabric went dark for
an hour today because of the volcanic eruption"*, and "*The
Atmospheric-Hydrology Data Fabric grew by 50% over the last 6 months we
speculate because of softening stances on climate change."*
--
Dr. ir. Herman Stehouwer
Rechenzentrum Garching @ Max Planck for Plasmaphysics
RDA Secretariat
***@***.*** 0031-619258815