Re: updates to BP doc

Hello!

Thank you Annette, we indeed agree with Phil's comments.

We may put this suggestion in the Data Enrichment Section Introduction 
"this is a topic in its own right and is beyond the scope of the current 
work" if everyone agrees.

Regarding the Best Practice 33: Enrich data by generating new data, we 
suggest to change the subtitle for something like "Datasets should be 
enriched whenever possible, generating richer metadata and data when 
doing so will enhance its value."

In the Best Practice 34: Provide Complementary Presentations, the 
Intended Outcome we suggest to take out the first phrase and let only 
"Data consumers should not have to create their own tools to understand 
the meaning of the data."

Would that be okay?

Thank you! Kind regards,
Bernadette, Caroline and Newton


On 13/03/16 12:46, Phil Archer wrote:
> Thanks Annette,
>
> I've just read through those enrichment BPs in your version of the doc 
> and I like them all. The examples certainly help make it 
> understandable. Your points about labelling inferred values is 
> interesting and points to the complexity of the subject. Perhaps a 
> line such as "this is a topic in its own right and is beyond the scope 
> of the current work" might be appropriate. That would then provide a 
> potential hook to the expected member submission on the topic.
>
> I really like the last one about responsible use - a minor amendment 
> would include a pointer to the DUV ;-)
>
> Phil.
>
> On 13/03/2016 09:13, Annette Greiner wrote:
>> Hi folks,
>> I've added the BPs about subsetting and enrichment and issued a pull
>> request for those.
>>
>> I've also gotten to thinking that we ought to have something about the
>> duties of reusers of data, as this is also a type of data publishing. So
>> I wrote this up as a possible drop-in BP. It's in a separate commit for
>> ease of ignoring or merging.
>>
>> Happy trails!
>> -Annette
>>
>>
>>       7.15 Data Re-Use
>>
>> Re-using data is another way of publishing data. Data re-users have some
>> responsibilities that are unique to publishing on the web.This section
>> provides advice to be followed by people who re-use data.
>>
>>
>> *Reuse Data Respectfully*
>>
>> When reusing data, be considerate of the original publisher. Cite the
>> original dataset; give feedback when you find problems; follow licensing
>> constraints.
>>
>> *Why*
>>
>> Publishers who make data available on the web deserve acknowledgment for
>> enabling others to work with it. Citation also maintains provenance and
>> helps still others to work with the data. Providing feedback repays the
>> publishers for their efforts and allows them to improve the dataset for
>> future users. Following licensing constraints shows respect for the
>> original publisher’s work and prevents legal entanglements.
>>
>> *Intended Outcome*
>>
>> Original publishers should be acknowledged by citation. They should be
>> made aware of any known problems with the data. Datasets should not be
>> used in violation of licensing agreements.
>>
>> *Possible Approach to Implementation*
>>
>> Provide a textual citation of the source in a readily visible area of
>> the site in which it is used. Read the original license and be sure that
>> you provide any additional acknowledgments required. Follow the
>> publisher’s directions for submitting feedback about a dataset if you
>> find problems with it.
>>
>> *Example*: When publishing a visualization based on bus data from our
>> fictional transit agency, the re-user could include the text “Data
>> Source: MyCity Transport Agency” just beneath the graph and link the
>> citation text back to the original source.
>>
>> *How to Test*
>>
>> Verify that the original publisher is cited in a readily discoverable
>> place. Make sure that the licensing for the original permits the re-use
>> to which it is being applied.
>>
>>
>> *Evidence*
>>
>> Relevant requirements:: R-TrackDataUsages
>> <http://www.w3.org/TR/dwbp-ucr/#R-TrackDataUsage>, R-UsageFeedback
>> <http://www.w3.org/TR/dwbp-ucr/#R-UsageFeedback>, R-ProvAvailable
>> <http://www.w3.org/TR/dwbp-ucr/#R-ProvAvailable>
>>
>> *Benefits*
>>
>> Reuse, Trust, Discoverability
>>
>>
>