- From: John Bolton <sportsnetwork@gmail.com>
- Date: Fri, 31 Mar 2017 17:26:01 +0100
- To: public-openactive@w3.org
- Message-ID: <CAARBnPxsA-3nb1Dpiy4zFtKWey5nw1k2Wsraeo749+gDujVSiQ@mail.gmail.com>
Thank you for emailing link to draft specification for opportunity data. Schemas - Data liquidity For data transport, data just needs to get from sender to receiver. For data interchange, the meaning of the data needs to get from sender to receiver. To support proper interpretation by data recipients, the context of the original data point must be available along with the data. Will the metadata schema meet interchange use cases such as search, filtering, transport, identification, etc? Use of UUID (Universal Unique Identifier) rather than purely URL for identification? Effective Time Frame? Times may or may not be the same when data is self-reported by the user Matching opportunity data schema definitions with existing health schema specifications. Will there be any direct integrity constraints at schema level? Capture of device information? Use of headers re data point creation and identification / acquisition provenance. Regards John Bolton
Received on Saturday, 1 April 2017 13:06:31 UTC