- From: Newton Calegari <newton@nic.br>
- Date: Thu, 7 Apr 2016 16:41:16 -0300
- To: Deirdre Lee <deirdre@derilinx.com>, Data on the Web Best Practices Working Group <public-dwbp-wg@w3.org>
- Message-ID: <5706B7DC.9040000@nic.br>
Hi Deirdre, I updated some BPs with the requirements you listed, but I didn't update all of them. If the BP name on the middle column is **bold**, it means that I included the requirement for that BP. cheers, Newton >> >> *Requirement* >> >> >> >> *BP* >> >> >> >> *Explanation* >> >> R-DataIrreproducibility >> >> >> >> Best Practice 2: Provide descriptive metadata >> >> >> >> Whether a dataset is irreproducible can be included in the metadata >> description >> >> R-DataLifecyclePrivacy >> >> >> >> Best Practice 6: Provide data provenance information >> >> Best Practice 18: Provide data unavailability reference >> >> >> >> /By providing clear provenance information, a data publisher can be >> clear they are not infringing upon individual’s intellectual property >> rights/. >> >> If there are IP rights associated with the data, a data >> unavailability reference can be used.// >> >> R-DataLifecycleStage >> >> >> >> Best Practice 6: Provide data provenance information >> >> >> >> /Provenance information can indicate the data’s lifecycle stage/// >> >> R-DataMissingIncomplete >> >> >> >> *Best Practice 7: Provide data quality information* >> >> >> >> /Via data quality dimensions, publishers can indicate if data is >> partially missing or if the dataset is incomplete/ >> >> R-GeographicalContext >> >> >> >> *Best Practice 3: Provide locale parameters metadata* >> >> Best Practice 15: Use standardized terms >> >> Best Practice 16: Reuse vocabularies >> >> >> >> /GeographicalContext can be referred to consistently through locale >> parameters and the use of standardized terms and vocabularies./ >> >> R-GranularityLevels >> >> >> >> Best Practice 17: Choose the right formalization level >> >> *Best Practice 20: Provide Subsets for Large Datasets* >> >> >> >> The level of formal semantics that fit data and applications should >> be selected for the data. >> >> APIs should make slices or filtered subsets of the data available, >> the granularity depending on the needs of the domain and the demands >> of performance in a web application. >> >> R-QualityMetrics >> >> >> >> *Best Practice 7: Provide data quality information* >> >> >> >> /Data should be associated with a set of documented, objective and, >> if available, standardized quality metrics. This set of quality >> metrics may include user-defined or domain-specific metrics/ >> >> R-TrackDataUsages >> >> >> >> *Best Practice 37: Cite the Original Publication* >> >> >> >> Indicate the source of your data in the metadata for your reuse of >> the data >> >> R-VocabOpen >> >> >> >> *Best Practice 16: Reuse vocabularies* >> >> >> >> /Vocabularies should be shared in an open way/ >> >> R-LicenseLiability >> >> >> >> Best Practice 2: Provide descriptive metadata >> >> *Best Practice 36: Follow Licensing Terms* >> >> >> >> /Liability terms associated with usage of Data on the Web should be >> clearly outlined/ >> >> R-SensitivePrivacy >> >> >> >> *Best Practice 18: Provide data unavailability reference* >> >> >> >> /(replacing Best Practice 17: Preserve people's right to privacy)/ >> >> R-SensitiveSecurity >> >> >> >> *Best Practice 18: Provide data unavailability reference* >> >> >> >> /(replacing Best Practice 17: Preserve people's right to privacy)/ >> >> >> >>
Received on Thursday, 7 April 2016 19:41:49 UTC