- From: Annette Greiner <amgreiner@lbl.gov>
- Date: Thu, 22 Jan 2015 13:26:14 -0800
- To: Public DWBP WG <public-dwbp-wg@w3.org>
I took a closer look at the material in the BP doc that comes before the BPs. Here are some suggestions. Introduction -- "Data on the Web Best Practices have been developed to encourage . . ." should be "The best practices described below have been developed . . ." To explain which best practices we are talking about. (Otherwise, it sounds like some immutable, universal list is being referred to.) "either openly or through a paywall/firewall" should be "either openly or with controlled access" Paywalls and firewalls are not the only ways to control access. Audience -- We say "the normative element of each best practice is the intended outcome" I think the title/subtitle are normative as well. If we are going with the intended outcome alone, we definitely need to reword some of them along the lines that Antoine has suggested. The mention of secondary audience is too far away from the discussion of the primary audience. That last single sentence reads like an afterthought, and it lacks any clue as to why others would want to read it. Remember this? It fits in nicely after the second sentence: "We encourage anyone involved in the data life cycle to become familiar with them, as today’s data consumers are tomorrow’s data publishers." Lifecycle -- I'm not convinced that we need to include the data lifecycle in the best practices. I disagree with several pieces of it as it currently exists. (1) Data planning does not comprise data selection. Selecting data for use on the web should take account of many things not knowable in the planning stage (e.g., data quality, presence of PII). (2) Data publication and access describe the same moment in time. (3) The feedback box and the Refinement arrow are not quite right. I think the Feedback and access boxes are not needed. Refinement should be labeled as Feedback. Then there should be a loop to the left of Data publication that is Refinement. (4) Data archiving is not the moment when data is no longer needed. (There is no discrete moment like that, it's a long slow slide to obscurity that some would argue should have no end.) It is the moment when data is stored offline. If we want to end the lifecycle, we should call the last item "Data removal". BTW, I don't see data archiving as meeting our scoping criteria, though data removal might be in scope. I would define data removal as the moment when data is removed from the web. -Annette -- Annette Greiner NERSC Data and Analytics Services Lawrence Berkeley National Laboratory 510-495-2935
Received on Thursday, 22 January 2015 21:28:23 UTC