From Dataset Exchange Working Group

Agenda for DXWG CNEG subgroup teleconference 15 August 2018 20:00 UTC (in your timezone)



  1. Check bots are running (see below)
  2. Matching everyone on IRC and Webex
  3. Remind attendees to put present+ <nickname>
  4. Appoint Scribe. Scribe should enter 'regrets+ ' followed by the names of people who have sent regrets (ideally by adding their own name to this page)

Main agenda

  1. Confirm agenda
  2. Approve minutes from last meeting –
  3. Topics
  • #8 (=GitHub 264) "Metadata about server profile support can be used for discovery and mediated traversal via content negotiation. [ID5] (5.5)" and #9 (=GitHub 265) "Enable the ability to negotiate the metadata profile via http, similar to the negotiation of metadata formats today. [ID30] (5.30).": Are those in scope for conneg or more related to profile description?
  • #10 (=GitHub 266) Return http link headers using the following relationship types: Lars' suggested rewording "There needs to be a way to encode the necessary relations using an http link header", Antoine comments "I think we should still (as part of the requirement derived from 5.30) list the "necessary relations": URL of the source document, etc (so, keeping the feature but removing the http link header that was suggested as solution)"
  • derivedfrom: The URL of the source document, containing the ISO 19139 records.
  • profile: The URI of the metadata schema used in the returned document.
  • self: The URL of the document returned by the API.
  • alternate: The URL of the current document, encoded in an alternative serialization. [ID30] (5.30)
  • #11 (=GitHub 267) "there is a need to distinguish between distributions that package the entire dataset and those that support access to specific items, queries, and packaged downloads of data. [ID51] (5.51)". There's a long discussion about this one in the google doc, whether this is a profile negotiation or a DCAT requirement.
  • There have been two emails on the comments list (1, 2). How do we react to them?
  1. AOB

Dial In details

NB These details only apply for the CNEG sub group, they are different from the joint calls

 Joining instructions: (official participants and invited guests only)
 For text discussions, minutes, joining the speaker queue, actions & issues IRC channel: #dxwgcneg 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)
 When you join the IRC channel, please immediately type 'present+ {yourname}' (this adds your name to the participants list in the minutes)
 See WebEx Best Practices for further information
  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

(Subgroup meetings may need to specify the irc e.g. /invite trackbot #dxwgdcat)

Then you can type:

trackbot, start meeting

That should invite zakim and RRSAgent and generally get things ready to go. As a reminder: the Zakim IRC bot handles things like the speaker queue, RRSAgent handles the minute-taking, present and regrets list etc.

Please note that you will see a message that Zakim does not see any meetings scheduled at this time. This is a reference to the old conference bridge (also called Zakim) that is no longer in use. Scheduling is now done under the WebEx system. If you're feeling nostalgic for the old Zakim greeting, it's archived (of course).

Once you have started the meeting, you should see all three bots running:

If any are not in the room, type /invite and then the name of the bot followed by the relevent channel e.g.

/invite Zakim #dxwgdcat

/invite rrsagent #dxwgdcat

During the meeting you may need to set the access permissions on the chat log with this command:

RRSAgent, make logs public

Then to create the minutes, type

RRSAgent, draft minutes