- From: Deirdre Lee <deirdre@derilinx.com>
- Date: Tue, 5 Apr 2016 18:40:50 +0100
- To: Data on the Web Best Practices Working Group <public-dwbp-wg@w3.org>
- Message-ID: <5703F8A2.8030501@derilinx.com>
Hi, In response to my open action 247 to fill in the blanks in 'Use Cases Requirements x Best Practices table' http://w3c.github.io/dwbp/bp.html#requirements See suggestions below. For those requirements with BPs linked, a lot of BP numbers have since been updated. When the BP numbers have been finalised, this table should be checked again. Cheers, Deirdre *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)/ -- ------------------------------------ Deirdre Lee, CEO & Founder Derilinx - Linked & Open Data Solutions Web: www.derilinx.com Email: deirdre@derilinx.com Address: 11/12 Baggot Court, Dublin 2, D02 F891 Tel: +353 (0)1 254 4316 Mob: +353 (0)87 417 2318 Linkedin: ie.linkedin.com/in/leedeirdre/ Twitter: @deirdrelee
Received on Tuesday, 5 April 2016 17:41:24 UTC