- From: Deirdre Lee <deirdre@derilinx.com>
- Date: Mon, 27 Jun 2016 19:13:27 +0100
- To: Data on the Web Best Practices Working Group <public-dwbp-wg@w3.org>, Annette Greiner <amgreiner@lbl.gov>
Hi, I suggest https://www.w3.org/2013/dwbp/track/issues/251 has been addressed through subsequent versions of the BP doc and can be closed? Cheers, Deirdre On 31/03/2016 23:48, Data on the Web Best Practices Working Group Issue Tracker wrote: > dwbp-ISSUE-251: [Best practices document(s)] > > http://www.w3.org/2013/dwbp/track/issues/251 > > Raised by: Annette Greiner > On product: Best practices document(s) > > Annette still has some concerns about the Data Preservation BPs [1]. I think it is important to discuss these issues with the group and try to find a solution for this. > > BP Use a trusted serialization format for preserved data dumps > To the extent that this is in scope, it is covered under the BP about using standardized formats. We could add a note to that mentioning the value for preservation. I don’t think this needs to be a separate BP. > > BP Update the status of identifiers > To the extent that this is in scope, it should be covered under versioning or unavailability. What are “preserved” datasets? Are they available on the web? If not, it is out of scope. If they are, then they are versions. > > BP Assess dataset coverage, is still written in the context of archiving data, which we have agreed was out of scope. It is valuable for the point that datasets should have minimal dependencies on external entities that may not be preserved. It needs to be rewritten to be about that rather than about assessing a dataset for its value in an archive. > > > [1] https://lists.w3.org/Archives/Public/public-dwbp-wg/2016Mar/0231.html > > > -- ------------------------------------ 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 Monday, 27 June 2016 18:14:02 UTC