From Data on the Web Best Practices
Jump to: navigation, search

Agenda for DWBP teleconference 28-October-2016 13:00 UTC

Dial in details

  Joining instructions: (official participants and invited guests only)
  Join using WebEx in your browser
  Or you can dial in through +1-617-324-0000 (US Toll Number)
  Access code: 319 050 138  
  For text discussions, minutes, joining the speaker queue, actions & issues IRC channel: #dwbp on on port 6667
  Please be sure to join both IRC and WebEx and use the same nick in both (or it gets very confusing)

  • Chair: Hadley
  • Scribe:
  • Regrets:


  1. Check bots are running (see #The IRC Bots)
  2. Matching everyone on IRC and webex, by typing 'present+ name'. (It helps if you use the same name on IRC and WebEx.)
  3. Appoint Scribe
  4. Approving minutes from last call [1]

Main agenda

  • Status check on the process of gathering implementations for the BP's CR stage.

Topics to be discussed:

  • Main questions
  1. Can we include a data portal as an evidence or we should include a specific dataset from the portal? For example: worldbank, open data portal nasa.
  2. Should we have a double check on the evaluations?
  3. How many evidences are really necessary for each BP?
  4. Can we say that a dataset has machine-readable version for the metadata when it is published on a data portal that uses CKAN or Socrata?
  5. Is it enough to say that the API is REST to assume that the API uses web standards?
  6. How to get evidences (from existing datasets) for the following BPs? Maybe, most of these BPs are not implemented yet in real world scenarios. In this case, should we create oyr own datasets to show that it is possible to implement the BP?
      • Best Practice 5: Provide data provenance information (human and machine-readable)
      • Best Practice 6: Provide data quality information (human and machine-readable)
      • Best Practice 8: Provide version history (human and machine-readable)
      • Best Practice 11: Assign URIs to dataset versions and series
      • Best Practice 16: Choose the right formalization level
      • Best Practice 20: Provide real-time access (it is difficult to test if the data is available on real time)
      • Best Practice 22: Provide an explanation for data that is not available
      • Best Practice 26: Avoid Breaking Changes to Your API
      • Best Practice 27: Preserve identifiers
      • Best Practice 28: Assess dataset coverage
      • Best Practice 30: Make feedback available
      • Best Practice 31: Enrich data by generating new data
      • Best Practice 33: Provide Feedback to the Original Publisher
      • Best Practice 34: Follow Licensing Terms
  • What we did to collect evidences?
  1. We massive promoted the DWBP and asked for evidences using the (Email Template ). The list of institutions contacted is available (here).
  2. We sent messages to members or contributors from the group asking help with collecting evidences for specific BP: Annette, Christophe, Ghislain, Lewis, Nandana, Herber
  3. We sent messages to members from the group asking help with evaluating a dataset or reviewing our evaluation: Laufer (Bio2RDF) and Antoine (Europeana)
  4. Peter sent a lot messages asking for DWBP evidences (ex: Open Data Impact Map)
  5. We evaluated existing data portals or asked the community to make an evaluation of a specific dataset on the light of the DWBP: DBpedia (asked help for the DBpedia community from Brazil), Worldbank (Bernadette made the evaluation) and Open Data Impact Map (Bernadette made the evaluation)
  • Next Steps

1. To include more evidences:

  • Open government data portals
    • Open data portal - UK
    • Open data portal - USA

  • Scientific data portals

2. To implement datasets to have more evidences for BPs that not in use already 3. To contact more people and to keep in contact with members of the WG

The IRC Bots

  W3C Telecon Resources:
  Zakim instructions in English
  Basic instructions in Portuguese

To start the meeting, check that trackbot is in the IRC channel (it usually is). If not, type:

/invite trackbot

Then you can type:

trackbot, start meeting

That should invite zakim and RRSAgent and generally get things ready to go. If it fails for any reason, you'll need to do things manually that trackbot does automatically. At the start of the meeting check that the following bots are running in IRC:

If any are not in the room, type /invite and then the name of the bot

Remember that the zakim bot is not tied to the WebEx audio so it no longer automatically records who is present, can't tell you who is noisy, can't mute people etc.

If you had to invite RRSAgent manually, during the meeting you need to set the access permissions on the chat log with this command:

RRSAgent, make logs public

Everything else is automatic since we use CommonScribe


Minutes +
ScribePhil +
SubjectStatus check for BP doc +
TypeTelecon +
"Date" is a type and predefined property provided by Semantic MediaWiki to represent date values.
October 28, 2016 +