Resolved: /www.w3.org/2017/04/12-sdwbp-minutes//www.w3.org/2017/04/28-sdwbp-minutes/Previous minutes approved https://www.w3.org/2017/04/26-sdwbp-minutes//www.w3.org/2017/04/28-sdwbp-minutes//www.w3.org/2017/04/12-sdwbp-minutes
jtandy: We did everything except the bits Josh was going to do in BP9
jtandy: I think having the plan like that has been helpful
… Any questions on the sprint status?
<Zakim> AndreaPerego, you wanted to say we've probably approved the wrong minutes - the last minutes should be here: https://www.w3.org/2017/04/26-sdwbp-minutes
jtandy: Not going to get a great deal of discussion as most have a PR associated with them.
jtandy: These are the 4 BP issues
jtandy: This asks whether our list of file formats should include scientific file formats
phila: DWBP avoided discussion of formats
jtandy: We discussed this in Delft - and decided to include some.
… Personally, I think that the scientific formats are difficult for general Web usage
eparsons: I don't feel strongly, but ... remembering our primary audience. For that mass of people how important are scientific formats for them?
jtandy: I agree
ChrisLittle: I suggest we put them as examples of how not to do it. Here are some formats with lots of data that are not accessible but used for good tech and historical reasons
… That might be a nudge to owners of those data sets to offer something else
eparsons: I'll be in St Johns for some of the meeting
jtandy: Chris will be there.
jtandy: I hear that we don't need to fix it right now. The wider Web community prob won't want those.
AndreaPerego: I agree that we pro shouldn't include those in the table. But I'm concerned about saying this is a worst practice as it will open a can of worms.
… Saying what you shouldn't do means providing evidence for why.
jtandy: I also don't like saying this is bad.
… What I think I hear from Chris is why you might not want to use the following list of sci formats.
jtandy: Can you make a note ChrisLittle to say that in St Johns
jtandy: This is about the ack section.
… Purely editorial.
… We can tidy up the acknowledgement section. We can decide who is and isn't on the list
jtandy: There's a PR related to this
… I put in a namespace table, Clemens suggested it wasn't very helpful.
jtandy: That's adding an id to each example so we can use it
phila: Agh! I though ReSpec added IDs to examples
jtandy: All done except the one marked for Linda to resolve.
<jtandy> [Linda] This is on dataset discovery - it's not a direct comment but can be added as an example to the relevant BP
jtandy: Linda had a look and said there wasn't really any change to make.
<AndreaPerego> I agree.
eparsons: I agree, it's more an FYI from Dan.
jtandy: Next point is to review our pending pull requests
jtandy: from earliest to newest.
jtandy: This is about namespaces and their prefixes
jtandy: If we agree with these changes,then I can merge them straight away
<jtandy> (largely) see here: https://rawgit.com/w3c/sdw/bp-edit-clemens-ns/bp/index.html#namespaces
ClemensPortele: RDF and XML namespaces are different, so I split them into 2 different sections
… I also did some corrections.
… Around GeoSPARQL and GML
… I split it into 2 sections and added an intro.
ClemensPortele: I changed the namespaces, e.g. we had two bag namespaces
jtandy: If you look at the URL I pasted, you can see the raw git
PROPOSED: To accept Clemens' pull request 870
jtandy: I think it's a good piece of work and would like it included.
Resolved: To accept Clemens' pull request 870
jtandy: That merge has been made
jtandy: 871 is about unique thing for dctems
AndreaPerego: Main issue was that we've been using 3 different prefixes for dcterms
<ChrisLittle> * Apple spell checker!
phila: Made some rambling comment about dcterms and dc not being the same - but all is well. dc:description and dcterms:description are the same
<eparsons> My DC goes to 11 !!!
jtandy: Any more questions wrt Andrea's work on this?
PROPOSED: Accept Andrea's pull request 871
<AndreaPerego> +1 (but I have a conflict of interests)
Resolved: Accept Andrea's pull request 871
jtandy: I'm now merging PR 871
jtandy: Pull Request 874
AndreaPerego: This is about an example about referring to metadata published in a Web-friendly way.
… The PR says it's about BP12 but actually it's about BP13 about metadata
… Idea is to include it there.
… It's about an API, work was done around GeoDCAT-AP
… Uses CSW interface.
… Idea is to provide an example for using your geospatial catalogue in a Web-friendly way and in RDF
jtandy: I believe the API is experimental but the practice is not.
AndreaPerego: It's a thing that can be out on top of any CSW
jtandy: We should perhaps add a note that it's only about data APIs
ClemensPortele: It seems clear with the example that we have there.
… This is editorial.
<jtandy> Add clarification about metadata API #880
jtandy: Assigned issue to Clemens
… It's editorial, so I suggest we vote on accepting this PR
PROPOSED: Accept Pull Request 874
Resolved: Accept Pull Request 874
jtandy: I am merging the pull request
jtandy: Just 2 more to go
<ClemensPortele> I have to leave now, but will vote +1 on the outstanding PRs and the release of the BP document
AndreaPerego: We have a BP about making data indexable by search engines
… We talk about using schema.org
… My proposal is to add an additional pointer to some mapping exercises
… mapping DCAT-AP and geoDCAT-AP to schema.org
… It's an example of a mapping of an RDF vocab to schema.org
jtandy: This is just an additional Green Note
jtandy: If you click on the file change it's small and self-contained
PROPOSED: Accept Pull request 875
Resolved: Accept Pull request 875
jtandy: Merging now...
jtandy: Last one is 879
tidoust: Just to satisfy PubRules. There were some markup errors and some encoding issues. We prefer Unicode Form-C apparently
… There's a mistake in my...
… There's a reference to the SKOS primer, so I forced it.
… Both minor things from a PubRules perspective
jtandy: Any questions?
PROPOSED: Accept PR 879
Resolved: Accept PR 879
jtandy: Merging now
jtandy: That's an empty list of pull requests
<jtandy> Vote to release a 'final' Working Draft of the Spatial Data on the Web Best Practice Note
phila: Is this the final, final vote?
jtandy: There are bound to be comments/typos etc. from the TC review
phila: Just clarifies - we're now in the hands of the OGC formal process for a BP doc
… There is no equivalent for this doc at W3C
jtandy: From our POV, this is the final version, modulo any substantive changes that come back from the TC process.
eparsons: We'll need to deal with those of course.
jtandy: This is like an extensive piece of outreach work
phila: So you want to publish this in /TR space
jtandy: Yes, so Scott can point to it
jtandy: Any questions about the doc in its current state?
jtandy: At the bottom of the detailed planning doc
… There's a discussion about adding ORCIDs
… We'll do that as and when
… So, again, any comments or questions?
<eparsons> PROPOSED: That the editors draft of the Best Practice doc at https://w3c.github.io/sdw/bp/ be published by W3C and OGC as Final Public Draft.
<eparsons> PROPOSED: That the editors draft of the Best Practice doc at https://w3c.github.io/sdw/bp/ be published by W3C and OGC as Final Public Working Draft\/Note
<jtandy> on behalf of Clemens, Payam, Bart, Linda, Josh and Simon :: +1
Resolved: That the editors draft of the Best Practice doc at https://w3c.github.io/sdw/bp/ be published by W3C and OGC as Final Public Working Draft/Note
<eparsons> Congratulations and Thanks to the Editors !!!
<ChrisLittle> clap clap clap!!
<LarsG> Well done, editors!
Resolved: Vote of thanks to Jeremy, Linda and the major contributors
<AndreaPerego> Many, many thanks for the hard work done by the Editors!
tidoust: Just to clarify that I'll ask for publication tomorrow for W3C
jtandy: Moans about having to use simplified English. +1 from the scribe
<jtandy> Date: 15-May-2017 Time: 14:00 UTC Videoconference: Goto Meeting
jtandy: You'll see that in order to begin the OGC TC vote, we start with a Go To Webinar
… As far as I'm aware, it's just a quick run through what the doc is?
eparsons: Think of it as an extended elevator pitch.
jtandy: That's at 14:00 UTC on Monday
jtandy: Who will try and be there?
<ChrisLittle> probably me
phila: Is very sorry but I can't
eparsons: It's not designed for us, it's for everyone else.
eparsons: I'd like to formally express thanks to you, Jeremy and Linda for all the huge amount of work you've done. That on behalf of myself and Kerry
+1 from phila
jtandy: I see no reason for another BP sub group call
jtandy: Thanks to everyone who has contributed. Notably Andrea, Clemens and Bill.