Re: Best Practices Cross-Reference Section

I like this way of organizing our thoughts and intentions.



Best Regards,

Steve

Motto: "Do First, Think, Do it Again"



From:	Laufer <laufer@globo.com>
To:	DWBP WG <public-dwbp-wg@w3.org>
Date:	10/19/2015 12:49 PM
Subject:	Best Practices Cross-Reference Section



Hi, All,


We have a scope issue since the beginning of the group around the type of
thing that we should deal with our Best Practices. As Phil pointed during
the last F2F, maybe the name of the group should be different, to clarify
in a better way the things the BPS refer.


We have decided that the group will not treat things like the choice of
data, its domain, neither the way it is collected or how to guarantee data
quality, etc.. We decided, too, that we will not treat only Linked Data
Publications. Maybe a more appropriate name could be Data on the Web
Publishing Best Practices (as Phil has talked about).


We have now a long discussion about how to facilitate the reading of our
document and the term webby has been introduced by Eric. I think it is a
very good way to see the things but I also think that we have to deal with
features of a published document that are not so directed to this term.
And, again, we have to deal with not LD things, as CSV files, for example.


In our work process we have started with collecting a set of use cases and
then we listed a set of requirements that should be took into account in
the BPs. We defined a template for the BPs where we have a Why and an
Intended Outcome sections that should, in some sense, address these
requirements. But we do not have an explicit relation between the
requirements and the BPs.


I think that a way to facilitate the user that want some guidance in how to
publish a document with best practices, is to give a cross-reference of
these BPs, using some taxonomy that would consider the requirements and the
features for a webby data proposed by Eric in [1], and other
characteristics.


Each Bp has each own Why and Intended Outcome, but there are common
features (characteristics, criteria, I do not know the better term...) that
could group BPs ins a way to help a Publisher to achieve a more clear
objective.


Bernardette has listed some of these characteristics that she collected
from the BPs [2].


I made an exercise highlighting some sentences (mainly verbs) used in the
Why and Intended Outcome sections of the BPs. I think that we could make a
collective effort to define a taxonomy and create a BPs Cross-Reference
with an explanation of how to use this cross-reference section as a
guidance to the reading of BPs.


-- Erik List
Linkable
Parseable
Understandable
Linked
Usable


-- Bernadette List
Comprehension
Discoverability
Reuse
Trustworthiness
Linkability
Processibility
Interoperability
Accessibility


-- BPs Highlights
Humans Understand the Metadata
Machines Process the Metadata
Humans Understand the Nature of the Dataset
Machines Automatically Discover the Dataset
Understand and Manipulate the Data
Improve Re-Use of Data
Interpret the Meaning
Enable Automated Translation Services
Understand Internal Structure
Automatically Process the Structural Data
Assess the Usability of Data
Understand Possible Restrictions On the Use of A Distribution
Know the Origin or History of Data
Easy the Dataset Selection
Increase Chances of Re-Use
Document Data Quality
Document Quality Issues
Uniquely Identify A Dataset
How Data Changed Over Time
Understand How the Dataset Typically Changes from Version To Version
Understand How Any Two Specific Versions Differ
Enables Data Identification and Comparison
Pre-Condition For Proper Data Management and Re-Use
Datasets Must Be Discoverable and Citable Through Time
Refer to a Specific Version of a Dataset and to Concepts Such as a 'Dataset
Series' and 'the Latest Version'
Machines Easily Read and Process Data Published On the Web
Data Consumers Use Computational Tools Typically Available In the Relevant
Domain to Work With the Data
Data Consumers Re-Use of Data Without Investment in Proprietary Software
Work With the Data Without Transforming It
Enable Interoperability and Consensus Among Data Publishers and Consumers
Encourage Re-Use of the Data
Data Should Not Be More Complex to Produce and Re-Use Than Necessary
Data That Can Identify an Individual Person Must Not Be Published Without
their Consent.
Provide Access to Bulk Data
Provide Machines Data Access in a Variety of Formats
Provide Data Access Using Browser s a Client
Provide Real-Time Access to Critical Time Sensitive Data
Provide Data Up-To-Date
Explicit Update Frequency of Data
Make API Versioning Separated from Data Versioning
Keep the Old Versions of APIs
Make Possible To Read and Load a Dataset into a Database Even if its
Software is no Longer Supported
Improve the Quality of Published Data
Encourage Publication of New Data Help Data Publishers Understand Data
Consumers Needs
Enhance the Consumers' Collaborative Experience
Make Data a More Valuable Asset


[1] http://dret.github.io/webdata/


[2]
https://docs.google.com/spreadsheets/d/1IT6IEeyGUY9crIYY9hDQLgdVx4XVzzKYf21N7YQrO5s/edit?ts=560b0172&pli=1


Cheers,
Laufer


--


. . . .. . .
. . . ..
. .. .






--1__
BBF470DFF4C52A8f9e8a93df938690918c0ABBF470DFF4C52A
Content-Transfer-Encoding: quoted-printable
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body><p>I like this way of organizing our thoughts and intentions.  <br><br><br><br>Best Regards,<br><br>Steve<br><br>Motto: &quot;Do First, Think, Do it Again&quot;<br><br><img width="16" height="16" src="cid:1__=0ABBF470DFF4C52A8f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Laufer ---10/19/2015 12:49:25 PM---  Hi, All,"><font color="#424282">Laufer ---10/19/2015 12:49:25 PM---  Hi, All,</font><br><br><font size="2" color="#5F5F5F">From:        </font><font size="2">Laufer &lt;laufer@globo.com&gt;</font><br><font size="2" color="#5F5F5F">To:        </font><font size="2">DWBP WG &lt;public-dwbp-wg@w3.org&gt;</font><br><font size="2" color="#5F5F5F">Date:        </font><font size="2">10/19/2015 12:49 PM</font><br><font size="2" color="#5F5F5F">Subject:        </font><font size="2">Best Practices Cross-Reference Section</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="4" face="Times New Roman">Hi, All,</font><p><font size="4" face="Times New Roman">We have a scope issue since the beginning of the group around the type of thing that we should deal with our Best Practices. As Phil pointed during the last F2F, maybe the name of the group should be different, to clarify in a better way the things the BPS refer.</font><p><font size="4" face="Times New Roman">We have decided that the group will not treat things like the choice of data, its domain, neither the way it is collected or how to guarantee data quality, etc.. We decided, too, that we will not treat only Linked Data Publications. Maybe a more appropriate name could be Data on the Web Publishing Best Practices (as Phil has talked about).</font><p><font size="4" face="Times New Roman">We have now a long discussion about how to facilitate the reading of our document and the term webby has been introduced by Eric. I think it is a very good way to see the things but I also think that we have to deal with features of a published document that are not so directed to this term. And, again, we have to deal with not LD things, as CSV files, for example.</font><p><font size="4" face="Times New Roman">In our work process we have started with collecting a set of use cases and then we listed a set of requirements that should be took into account in the BPs. We defined a template for the BPs where we have a Why and an Intended Outcome sections that should, in some sense, address these requirements. But we do not have an explicit relation between the requirements and the BPs.</font><p><font size="4" face="Times New Roman">I think that a way to facilitate the user that want some guidance in how to publish a document with best practices, is to give a cross-reference of these BPs, using some taxonomy that would consider the requirements and the features for a webby data proposed by Eric in [1], and other characteristics.</font><p><font size="4" face="Times New Roman">Each Bp has each own Why and Intended Outcome, but there are common features (characteristics, criteria, I do not know the better term...) that could group BPs ins a way to help a Publisher to achieve a more clear objective.</font><p><font size="4" face="Times New Roman">Bernardette has listed some of these characteristics that she collected from the BPs [2].</font><p><font size="4" face="Times New Roman">I made an exercise highlighting some sentences (mainly verbs) used in the Why and Intended Outcome sections of the BPs. I think that we could make a collective effort to define a taxonomy and create a BPs Cross-Reference with an explanation of how to use this cross-reference section as a guidance to the reading of BPs.</font><p><font size="4" face="Times New Roman">-- Erik List<br>Linkable<br>Parseable<br>Understandable<br>Linked<br>Usable</font><p><font size="4" face="Times New Roman">-- Bernadette List<br>Comprehension<br>Discoverability<br>Reuse<br>Trustworthiness<br>Linkability<br>Processibility<br>Interoperability<br>Accessibility</font><p><font size="4" face="Times New Roman">-- BPs Highlights<br>Humans Understand the Metadata<br>Machines Process the Metadata<br>Humans Understand the Nature of the Dataset<br>Machines Automatically Discover the Dataset<br>Understand and Manipulate the Data<br>Improve Re-Use of Data<br>Interpret the Meaning<br>Enable Automated Translation Services<br>Understand Internal Structure<br>Automatically Process the Structural Data<br>Assess the Usability of Data<br>Understand Possible Restrictions On the Use of A Distribution<br>Know the Origin or History of Data<br>Easy the Dataset Selection<br>Increase Chances of Re-Use<br>Document Data Quality<br>Document Quality Issues<br>Uniquely Identify A Dataset<br>How Data Changed Over Time<br>Understand How the Dataset Typically Changes from Version To Version<br>Understand How Any Two Specific Versions Differ<br>Enables Data Identification and Comparison<br>Pre-Condition For Proper Data Management and Re-Use<br>Datasets Must Be Discoverable and Citable Through Time<br>Refer to a Specific Version of a Dataset and to Concepts Such as a 'Dataset Series' and 'the Latest Version'<br>Machines Easily Read and Process Data Published On the Web<br>Data Consumers Use Computational Tools Typically Available In the Relevant Domain to Work With the Data<br>Data Consumers Re-Use of Data Without Investment in Proprietary Software<br>Work With the Data Without Transforming It<br>Enable Interoperability and Consensus Among Data Publishers and Consumers<br>Encourage Re-Use of the Data<br>Data Should Not Be More Complex to Produce and Re-Use Than Necessary<br>Data That Can Identify an Individual Person Must Not Be Published Without their Consent.<br>Provide Access to Bulk Data<br>Provide Machines Data Access in a Variety of Formats<br>Provide Data Access Using Browser s a Client<br>Provide Real-Time Access to Critical Time Sensitive Data<br>Provide Data Up-To-Date<br>Explicit Update Frequency of Data<br>Make API Versioning Separated from Data Versioning<br>Keep the Old Versions of APIs<br>Make Possible To Read and Load a Dataset into a Database Even if its Software is no Longer Supported<br>Improve the Quality of Published Data<br>Encourage Publication of New Data Help Data Publishers Understand Data Consumers Needs <br>Enhance the Consumers' Collaborative Experience<br>Make Data a More Valuable Asset</font><p><font size="4" face="Times New Roman">[1] </font><font size="4" face="Times New Roman"><a href="http://dret.github.io/webdata/">http://dret.github.io/webdata/</a></font><p><font size="4" face="Times New Roman">[2] </font><font size="4" face="Times New Roman"><a href="https://docs.google.com/spreadsheets/d/1IT6IEeyGUY9crIYY9hDQLgdVx4XVzzKYf21N7YQrO5s/edit?ts=560b0172&pli=1">https://docs.google.com/spreadsheets/d/1IT6IEeyGUY9crIYY9hDQLgdVx4XVzzKYf21N7YQrO5s/edit?ts=560b0172&amp;pli=1</a></font><p><font size="4" face="Times New Roman">Cheers,<br>Laufer</font><p><font size="4" face="Times New Roman">--</font><p><font size="4" face="Times New Roman">. . . .. . . <br>. . . ..<br>. .. .</font><p><font size="4" face="Times New Roman"> </font><p><BR>
</body></html>

--1__
BBF470DFF4C52A8f9e8a93df938690918c0ABBF470DFF4C52A--


--0__
BBF470DFF4C52A8f9e8a93df938690918c0ABBF470DFF4C52A
Content-type: image/gif; 
	name="graycol.gif"
Content-Disposition: inline; filename="graycol.gif"
Content-ID: <1__
BBF470DFF4C52A8f9e8a93df938690918c0AB@>
Content-Transfer-Encoding: base64

R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu
ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7


--0__
BBF470DFF4C52A8f9e8a93df938690918c0ABBF470DFF4C52A--