19:53:34 <RRSAgent> RRSAgent has joined #sdw
19:53:34 <RRSAgent> logging to http://www.w3.org/2016/02/17-sdw-irc
19:53:36 <trackbot> RRSAgent, make logs world
19:53:36 <Zakim> Zakim has joined #sdw
19:53:38 <trackbot> Zakim, this will be SDW
19:53:38 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
19:53:39 <trackbot> Meeting: Spatial Data on the Web Working Group Teleconference
19:53:39 <trackbot> Date: 17 February 2016
19:54:03 <eparsons> Hello Newton - welocme
19:54:12 <eparsons> RRSAgent, make logs public
19:54:22 <eparsons> agenda: https://www.w3.org/2015/spatial/wiki/Meetings:Telecon20160217
19:54:28 <kerry> present+ kerry
19:55:49 <rachel> rachel has joined #sdw
19:55:59 <eparsons> present+ eparsons
19:56:00 <AndreaPerego> AndreaPerego has joined #sdw
19:56:24 <AndreaPerego> same here.
19:56:33 <eparsons> try again I have only just connected to webex
19:57:13 <robin> robin has joined #sdw
19:57:19 <robin> present+ robin
19:57:45 <eparsons> Regrets: Clemens,Andreas, Lewis, Lars
19:57:53 <eparsons> OK let me see...
19:57:56 <Caroline> Caroline has joined #sdw
19:58:46 <eparsons> hello Caroline
19:59:00 <eparsons> webex seems to be OK noew ?
19:59:12 <ScottSimmons> ScottSimmons has joined #sdw
19:59:15 <BernadetteLoscio> BernadetteLoscio has joined #sdw
19:59:38 <ScottSimmons> present+ ScottSimmons
19:59:41 <RaulGarciaCastro> RaulGarciaCastro has joined #sdw
20:00:08 <laufer> laufer has joined #sdw
20:00:10 <eparsons> ah OK the password in wrong - will change topic
20:00:20 <phila> phila has joined #sdw
20:00:33 <eparsons> topic: Password is v4qtEh56
20:00:34 <antoine> antoine has joined #sdw
20:00:58 <antoine> present+ antoine
20:00:59 <frans> frans has joined #sdw
20:01:07 <Linda> Linda has joined #sdw
20:01:21 <rachel> present+ rachel
20:01:23 <RaulGarciaCastro> present+ RaulGarciaCastro
20:01:54 <kerry> kerry has changed the topic to: password is v4qtEh56
20:01:58 <BernadetteLoscio> present+ BernadetteLoscio
20:02:02 <frans> present+ frans
20:02:10 <AndreaPerego> present+ AndreaPerego
20:02:10 <laufer> present+ laufer
20:02:19 <joshlieberman> joshlieberman has joined #sdw
20:02:31 <Caroline> Present+ Caroline
20:02:49 <jtandy> jtandy has joined #sdw
20:03:01 <jtandy> present+ jtandy
20:03:38 <Linda> Present+ Linda
20:03:53 <joshlieberman> +joshlieberman
20:05:03 <eparsons> scribe: Kerry
20:05:14 <SimonCox_> SimonCox_ has joined #sdw
20:05:32 <kerry> scribeNick: Kerry
20:05:42 <newton> present+ newton
20:05:49 <MattPerry> MattPerry has joined #sdw
20:06:25 <eparsons> Topic : Approve last week's minutes
20:06:41 <eparsons> http://www.w3.org/2016/02/03-sdw-minutes
20:06:48 <eparsons> Proposed : Approve last week's minutes
20:06:50 <SimonCox_> present+ SimonCox
20:06:54 <Linda> +1
20:06:56 <eparsons> +1
20:06:56 <RaulGarciaCastro> +1
20:06:57 <AndreaPerego> +1
20:06:58 <ScottSimmons> _1
20:06:58 <jtandy> +1
20:07:01 <ScottSimmons> +1
20:07:06 <frans> +1
20:07:11 <robin> +1
20:07:16 <eparsons> Resolved : Approve last week's minutes
20:07:19 <kerry> resolved: approve last week minutes http://www.w3.org/2016/02/03-sdw-minutes
20:07:24 <KJanowicz_> KJanowicz_ has joined #sdw
20:07:25 <MattPerry> present+ MattPerry
20:07:41 <ChrisLittle> ChrisLittle has joined #sdw
20:07:46 <eparsons> Topic : Patent Call
20:07:54 <eparsons> https://www.w3.org/2015/spatial/wiki/Patent_Call
20:08:00 <ChrisLittle> present+ ChrisLittle
20:08:23 <kerry> no comments
20:08:30 <eparsons> Topic : Short update on F2F Meeting last week
20:08:53 <kerry> geonovum hosted, thankyou Linda and genovum
20:09:02 <kerry> ... lots of work on deliverables
20:09:30 <kerry> .... key takeaway is that we have much more territory moving forward
20:10:04 <kerry> ...weekly calls will focus on a differnt deliverable each week, multiple calls each week, all together maybe only alternate weeks
20:10:14 <kerry> ... discussed at f2f
20:10:33 <kerry> ...will pin down next week
20:10:49 <kerry> ...geonovum meeting was productive
20:10:53 <SimonCox_> And thanks to everyone who made the time and effort to attend! (AMersfoorth)
20:10:59 <eparsons> Topic : Coordination with DWBP
20:11:06 <kerry> ... anything esle must b said?
20:11:13 <BernadetteLoscio> BernadetteLoscio has joined #sdw
20:11:27 <jtandy> s/esle/else/
20:11:28 <kerry> ed: welcome to DWBP
20:11:37 <AndreaPerego> s/must b said/must be said/
20:11:38 <kerry> ... we will steal whatever content we can!
20:11:41 <Caroline> we are happy to join this call :)
20:11:44 <ChrisLittle> q+
20:11:50 <phila_> phila_ has joined #sdw
20:12:14 <kerry> .... will hand over to Jeremy and linda, our best practice editors... we want to be coordinated
20:12:29 <eparsons> ack next
20:13:11 <kerry> ChrisLittle: i want to point out that we discuss things that seem out of scope e.g. time as they  are in scope for us (not just spatial)
20:13:27 <eparsons> https://lists.w3.org/Archives/Public/public-sdw-wg/2016Feb/0060.html
20:14:00 <kerry> jtandy:  thankyou to dwbp for joining us; it is a great document now; tremendous job
20:14:22 <eparsons> here..here !
20:14:48 <kerry> ... our focus is more specific to dwbp, but we need to provide stuff that is additional for spatial data
20:14:59 <kerry> ... we will build on your work...
20:15:35 <kerry> ...the first thing "homework" was how DWBP is referencing spatail data and if they are done well
20:16:03 <kerry> ... e.g dubious use of rdf propert to reference a spatail concept
20:16:20 <kerry> ...but bp 2 6 8 9 are all using dct: spatail now
20:16:26 <kerry> ...has changed very recently
20:16:35 <Linda> S/spatail/spatial
20:16:36 <kerry> s/spatail/spatial/
20:16:51 <joshlieberman> dct:spatial <http://www.geonames.org/3399415>;
20:16:52 <BernadetteLoscio> :)
20:17:28 <kerry> ... is dct:spatial ok? I think so, what about others?
20:17:30 <phila_> q+
20:17:32 <Linda> +1 ok to me
20:17:33 <BernadetteLoscio> q+
20:17:37 <eparsons> ack next
20:18:07 <kerry> phila_:  it was dcterms: description I was worried about, not dct:spatial
20:18:26 <eparsons> ack next
20:18:36 <kerry> jtandy:  the only dcterms:descriptions are ... [missed]  nothing spatial
20:18:51 <jtandy> [dct:description "CSV distribution of the bus timetable dataset of MyCity."]
20:18:54 <kerry> BernadetteLoscio: pleasure to be here
20:19:28 <kerry> BernadetteLoscio: wanting to describe discovery metadata, temporal and spatial data about the dataset
20:19:37 <kerry> ...but you are interested in the data itself?
20:19:39 <ChrisLittle> discovery is not actually mentioned in the BP is it?
20:19:47 <RaulGarciaCastro> RaulGarciaCastro has joined #sdw
20:20:06 <kerry> jtandy: correct -- largeley the structured spatail data but also the descriptions for discovery
20:20:12 <joshlieberman> Also interested in the spatial data that is used as metadata for other datasets...
20:20:23 <kerry> ... your spatail descriptions of dataset look good to me
20:20:34 <kerry> .... one BP I will raise
20:20:36 <AndreaPerego> s/spatail/spatial/
20:20:37 <eparsons> rrsagent, draft minutes
20:20:37 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html eparsons
20:20:42 <phila> s/spatail/spatial/g
20:20:47 <kerry> ..BP16 use of standardised terms
20:20:48 <jtandy> http://w3c.github.io/dwbp/bp.html#MetadataStandardized
20:20:56 <frans> is http://www.geonames.org/3399415 an instance of dcterms:location?
20:21:10 <jtandy> "The Open Geospatial Consortium (OGC) could define the notion of granularity for geospatial datasets, while [DCAT] vocabulary provides a vocabulary reusing the same notion applied to catalogs on the Web."
20:21:59 <BernadetteLoscio> i agree!
20:22:03 <phila> +1 to jtandy on that
20:22:05 <antoine> q+
20:22:06 <BernadetteLoscio> +1
20:22:08 <kerry> ... not a statement about spatial but it looks odd referring to OGC this way, may not be useful to say a sdo should do more work
20:22:09 <eparsons> ack next
20:22:14 <kerry> ... comments?
20:22:33 <ChrisLittle> +1 to Jeremy on OGC comment
20:23:05 <kerry> antoine:  i was involved in this, will try to track history, would say you are right
20:23:18 <phila> OK if I raise an action in DWBP for you on that antoine?
20:23:45 <kerry> jtandy: that BP refers to use of standardised terms -- if we could find a codelist that does this would be good but not clear now
20:23:56 <frans> I read it as an example: a domain standards organisation can provide definitions for domain concepts
20:24:00 <kerry> antoine: is there one at the OGC?
20:24:07 <kerry> jtandy: anyone know?
20:24:17 <ChrisLittle> is granularity different from resolution?
20:24:25 <kerry> ...is there a vocab or codelist for granularity of geospatial data sets?
20:24:33 <BernadetteLoscio> q+
20:24:40 <kerry> joshlieberman:  is an iso19115 thing
20:24:41 <AndreaPerego> I would say that temporal / spatial resolution is a specific type of granularity.
20:24:58 <KJanowicz_> Agreed
20:25:00 <kerry> SimonCox_: level of detail is in citygml may be related
20:25:11 <eparsons> ack next
20:25:11 <KJanowicz_> I do not think that those terms do yet exist
20:25:12 <frans> I have seen LoD elsewhere in OGC documents too.
20:25:19 <kerry> jtandy: these codelists happen in lots of places
20:25:46 <kerry> BernadetteLoscio: I agree this needs to change, maybe present examples of codelists?
20:26:19 <kerry> jtandy: we could find an example of data refs a controoled vocab
20:26:22 <AndreaPerego> None I'm aware of.
20:26:26 <kerry> ...anyone got one?
20:26:28 <KJanowicz_> yes
20:26:33 <BernadetteLoscio> ok! thanks!
20:26:35 <KJanowicz_> See e.g., R2R
20:26:36 <kerry> ...[silence]
20:26:51 <kerry> KJanowicz_:  [cannot hear]
20:26:56 <joshlieberman> units!
20:27:17 <AndreaPerego> There's QUDT for units of measurement...
20:27:32 <kerry> KJanowicz_: ... very common use of codelists is observational data of mathematical [?] I can supply
20:27:36 <phila> Any chance of a URL in the IRC pls KJanowicz_ ?
20:27:54 <kerry> jtandy: codelist for instruments -- is it published by a recognised authority?
20:28:01 <AndreaPerego> QUDT (Quantities, Units, Dimensions and Data Types Ontologies): http://www.qudt.org/
20:28:04 <KJanowicz_> http://schema.geolink.org/voc/index.html
20:28:09 <kerry> KJanowicz_: yes -- i will provide the example
20:28:13 <BernadetteLoscio> ok! thanks!
20:28:27 <antoine> q+
20:28:29 <KJanowicz_> Just as one examplel: http://schema.geolink.org/1.0/voc/nvs/L05.html#d4e575
20:28:35 <kerry> jtandy: DWBP please let us know if this is not what you need
20:28:47 <joshlieberman> Granularity may be problematic since it is unclear that there is a single definition of spatial granularity, let alone a code list or metric.
20:28:51 <eparsons> ack next
20:28:54 <kerry> jtandy:  now wnat to show some of our BPs
20:29:03 <newton> s/wnat/want
20:29:04 <kerry> s/wnat/want/
20:29:08 <KJanowicz_> The source is: vocab.nerc.ac.uk
20:29:22 <phila> q+ to talk about normative and all that
20:29:32 <KJanowicz_> q+
20:29:45 <kerry> antoine: : content looks ok but is the authority really there? Is it a NASA official thing? or just a project result?
20:29:57 <eparsons> ack KJanowicz_
20:30:23 <kerry> KJanowicz_: it is authoritative [not sure]
20:31:04 <kerry> SimonCox_:  there are multiple groups in NASA doing units -- qudt may not be the only one from NASA
20:31:10 <jtandy> q+
20:31:18 <eparsons> ack phila
20:31:18 <Zakim> phila, you wanted to talk about normative and all that
20:31:24 <kerry> antoine: looing at second link it looks good
20:31:41 <jtandy> s/looing/looking/
20:32:01 <kerry> phila: difference between 2 groups: dwbp is rec track so hiher bar for references -- could ask Lewis to take a look for us
20:32:04 <rachel> adam leadbetter
20:32:45 <kerry> ...could look into stability, would need director approval to link to either, the NERC one looks better
20:32:54 <eparsons> ack jtandy
20:33:04 <kerry> ...as long as we are not making a normative statement it could be ok -- omnly guidance
20:33:10 <kerry> s/omnly/only/
20:33:17 <KJanowicz_> measuremen-types are a common example for shared codelists, e.g., for NitrateConcentration. another example are instrument types. Those codelists are used by large communities in data repositories such as R2R,BMO-DCO,...
20:33:27 <phila> s/hiher/higher/
20:33:35 <kerry> jtandy: asks simon about international rock types referenced by geosciml
20:34:03 <phila> present+ phila
20:34:13 <rachel> yes, rare turn up for a weds !
20:34:16 <kerry> SimonCox_: custodianship is geoscience australia  asking australian national data service, not yet stable
20:35:04 <kerry> SimonCox_:  content is stable but publication platform may not be
20:35:16 <SimonCox_> See http://resource.geosciml.org/classifier/ics/ischart/ for example
20:35:28 <Linda> What about the inspire codelists?
20:35:28 <kerry> rachel: I am on the working group for this -- is authoritative
20:36:16 <kerry> jtandy: dwbp and sdw neet tight links on some BPs
20:36:38 <kerry> ... anybody have an issue here -- BPs of DWBP that we reference?
20:36:39 <frans> q+
20:36:46 <eparsons> ack next
20:37:14 <kerry> frans: yes, the need for having indications of precision , geo coords are numbers
20:37:34 <kerry> ..does dwbp have something on precision e.g. significant digits?
20:37:56 <kerry> jtandy: e.g. we often see 15 dec places where it should be 1
20:38:00 <ChrisLittle> +1 to Frans comment
20:38:31 <phila> I don't recall seeing anything on that in DWBP
20:38:39 <kerry> frans: yes it is wrong and space-consuming -- we see it in coordinates but it could be in other data on the web
20:38:39 <KJanowicz_> This is not specific to spatial data, it is just a wrong way to report on accuracy.
20:38:51 <kerry> jtandy: not covered in dwbp now
20:38:53 <newton> q+
20:38:55 <BernadetteLoscio> q+
20:38:56 <ChrisLittle> Precision and accuracy need to be addressed
20:38:56 <eparsons> ack next
20:39:25 <BernadetteLoscio> q-
20:39:30 <kerry> newton: we do not work at this level of the data, we have not identified this requirement
20:39:34 <rachel> there is a section on data quality, and precision could be included there?
20:39:40 <antoine> q+
20:39:42 <kerry> ...we could work together for a new BP to do this
20:39:43 <phila> q+ to make ChrisLittle happy
20:39:51 <eparsons> ack next
20:40:29 <kerry> jtandy: general problem around numerical data -- beter for dwbp
20:41:04 <BernadetteLoscio> q+
20:41:20 <kerry> antoine: i am wondering where this sits in our products... we are also doing a note on the quality vocab and precision can sit here
20:41:37 <eparsons> ack next
20:41:38 <Zakim> phila, you wanted to make ChrisLittle happy
20:41:38 <kerry> ..we have not identified such precise requirements
20:41:40 <frans> precision can be expressed in metadata, but should be in the data themselves too
20:41:46 <phila> -> http://w3c.github.io/dwbp/vocab-dqg.html DQV
20:41:51 <joshlieberman> q+
20:42:14 <kerry> phila: am putting in link to dqv -- t his is the right place, but the people for this are not here now
20:42:30 <kerry> ...e.g. lawrence livermeore and pacific northwest people
20:42:35 <AndreaPerego> @Antoine, I think precision / accuracy can be indeed in scope of DQV (along with granularity)
20:42:40 <kerry> ...will raise an issue in dwbp to work on this
20:42:43 <jtandy> s/livermeore/livermore/
20:43:02 <eparsons> ack next
20:43:10 <kerry> ... those o ther vocabs also dataset usage will be useful at another time
20:43:10 <eparsons> rrsagent, draft minutes
20:43:11 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html eparsons
20:43:18 <ChrisLittle> good examples are temperature and currencies
20:43:40 <eparsons> ack next
20:44:04 <kerry> joshlieberman: say something provocative... granularity
20:44:22 <kerry> ...bp like "use an api" to enable fine-grained access
20:44:53 <phila> s/livermore/Lawrence Berkeley National Laboratory/
20:44:59 <kerry> ...but only bp is to provide that api data access  but wewant finer grained access to data elements
20:45:26 <kerry> ...is the dwbp thinking fine-grained access is not a big prblem?
20:45:29 <rachel> s/wewant/we want/
20:45:50 <kerry> s/prblem/problem/
20:46:04 <Caroline> q+
20:46:08 <kerry> phila: APIS comes up a lot -- this is not stable in BP doc
20:46:09 <eparsons> ack next
20:46:49 <BernadetteLoscio_> BernadetteLoscio_ has joined #sdw
20:47:00 <kerry> Caroline: need to work a lot on APIs , is a weakest piece, would someone here like to help?
20:47:15 <jtandy> q+ to ask what the timescales are for resolving the API-related best practices?
20:47:49 <eparsons> ack next
20:47:50 <Zakim> jtandy, you wanted to ask what the timescales are for resolving the API-related best practices?
20:48:12 <kerry> phila: suggest dwbp asks josh and SDW to review this area -- is 'any API on the web" the good scope? we have a lot of feedback from eric wilde
20:48:15 <Caroline> q+
20:48:19 <eparsons> ack next
20:48:20 <BernadetteLoscio_> present+ BernadetteLoscio
20:48:25 <kerry> phila: hoping to fgo to CR end march, ie 4 weeks
20:48:31 <kerry> s/fgo/go/
20:48:52 <kerry> Caroline: putting schedule on irc
20:49:08 <kerry> ...expect to delay another week
20:49:21 <phila> s/end/mid/
20:49:23 <Caroline> http://w3c.github.io/dwbp/bp-status.html
20:49:59 <phila> q+
20:50:01 <kerry> joshlieberman: question not whther you should use an api, but practice on granularity of data e.g. really small bits like just a latitude alone
20:50:18 <AndreaPerego> s/whther/whether/
20:50:25 <eparsons> ack next
20:50:27 <kerry> joshlieberman: we can share this for spatail and temporal
20:50:38 <AndreaPerego> s/spatail/spatial/
20:50:46 <kerry> joshlieberman: waht is the minimum granularity that is useful?
20:50:48 <KJanowicz_> q+
20:51:08 <kerry> phila: comes up more in sdw than dw -- it might be dw that handles this
20:51:12 <eparsons> ack next
20:51:22 <kerry> joshlieberman: agree, but all is connencted to everything
20:51:23 <jtandy> q+ to ask about bp26
20:51:54 <kerry> KJanowicz_: we have to stop triplifying all data--- what should be triples and what not?
20:51:58 <eparsons> ack next
20:51:59 <Zakim> jtandy, you wanted to ask about bp26
20:52:17 <eparsons> rrsagent, draft minutes
20:52:17 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html eparsons
20:52:44 <kerry> jtandy: bp 26 "use an api"' realtes to our "convenince" apis. we suggest you desing your api for a partiular purpose arounf useful questions
20:52:57 <kerry> ...we also think APIs can describe what they can give you
20:53:03 <rachel> s/realtes/relates
20:53:20 <newton> s/arounf/around/
20:53:20 <kerry> ...we also want an api search function -- give us the right resource about a plce called London
20:53:29 <RaulGarciaCastro> RaulGarciaCastro has joined #sdw
20:53:38 <kerry> .... these might also be relevant for DW API thinking
20:53:39 <BernadetteLoscio_> q+
20:53:44 <eparsons> ack next
20:53:47 <kerry> ...an additional call for APIs topic?
20:53:50 <AndreaPerego> +1
20:53:59 <ChrisLittle> q+
20:54:18 <kerry> BernadetteLoscio_: We should come back to this. As said it has been discussed but not stable.
20:54:18 <jtandy> [jtandy is happy to contribute to the further API discussions]
20:54:34 <eparsons> ack next
20:54:39 <kerry> eparsons: will organise a followup meeting
20:54:53 <jtandy> [and that follow up meeting needs to be _soon_ given their timescales]
20:55:04 <kerry> action: eparsons to organise followup meeting on APIs with Data on the Web
20:55:04 <trackbot> Created ACTION-146 - Organise followup meeting on apis with data on the web [on Ed Parsons - due 2016-02-24].
20:55:17 <KJanowicz_> +1
20:55:26 <jtandy> q+ to ask a question about Memento and BP8
20:55:28 <kerry> ChrisLittle: tilesets need differen levels of granularity -- needs to be teased out
20:55:32 <eparsons> ack next
20:55:33 <Zakim> jtandy, you wanted to ask a question about Memento and BP8
20:55:42 <kerry> ChrisLittle: [another example scribe missed]
20:56:05 <kerry> jtandy: versioning BP* makes use of memento
20:56:17 <jtandy> s/BP*/BP8/
20:56:31 <kerry> jtandy: waht is adoption of memnto that justifies this?
20:56:49 <AndreaPerego> s/memnto/Memento/
20:56:53 <BernadetteLoscio_> q+
20:56:55 <jtandy> [Best Practice 8: versioning information]
20:56:59 <eparsons> ack next
20:57:01 <kerry> phila: not a should or must -- but many people keen -- uneasy as it may not be adopted much -- may ask for comment on thi specifically
20:57:20 <kerry> BernadetteLoscio_: we tried to gove 2 examples, one without memnto and one with
20:57:24 <kerry> s/gove/give/
20:57:42 <AndreaPerego> s/memnto/Memento/
20:57:43 <kerry> BernadetteLoscio_:  we can also include other implementation approaches as examples
20:57:54 <jtandy> dct:publisher:transport-agency-mycity
20:57:55 <kerry> BernadetteLoscio_: was only to show examples
20:58:29 <ChrisLittle> ض+
20:58:31 <kerry> jtandy: turtle example had 2 colons without pred and obj -- not well formed turtle, is in a few places
20:59:02 <BernadetteLoscio_> q+
20:59:17 <eparsons> ack next
20:59:17 <rachel> q+ to suggest building on the transport example in our examples - with full geometry of routes, live bus locations etc
20:59:29 <kerry> eparsons: api meeting may be with a subset of DW team
20:59:47 <kerry> BernadetteLoscio_: identifiers: we should also discuss this as we both have something here
20:59:56 <newton> q+
20:59:59 <phila> s/DW team/SDW team/
21:00:10 <phila> zakim, close queue
21:00:10 <Zakim> ok, phila, the speaker queue is closed
21:00:22 <kerry> jtandy: ok -- running out of time--  next week? after Chris talks about time
21:00:31 <eparsons> ack next
21:00:32 <Zakim> rachel, you wanted to suggest building on the transport example in our examples - with full geometry of routes, live bus locations etc
21:00:36 <kerry> eparsons:  could be next week
21:00:52 <Caroline> we may join again next week :)
21:01:04 <kerry> rachel: yes, lets make our BPs aligned could build on our transport example, could also match naming
21:01:05 <eparsons> ack next
21:01:10 <newton> http://w3c.github.io/dwbp/bp.html#Conneg
21:01:40 <kerry> newton: bp 22 conneg, I am involved in this and will work on it tomorrow, please send email jeremy
21:01:41 <BernadetteLoscio_> +1 Rachel
21:01:59 <BernadetteLoscio_> thank you!!!
21:02:08 <kerry> eparsons: will pick this up next week too
21:02:11 <phila> RRSAgent, draft minutes
21:02:11 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html phila
21:02:15 <frans> Thank you. Getting the two WGs together was a good idea.
21:02:18 <Caroline> thank you!
21:02:20 <AndreaPerego> Thanks, and bye!
21:02:24 <newton> Thank you! Bye
21:02:26 <kerry> eparsons: will do conneg, apis and chris issues
21:02:26 <phila> RRSAgent, draft minutes
21:02:26 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html phila
21:02:26 <BernadetteLoscio_> bye!!
21:02:28 <Linda> Bye!
21:02:30 <laufer> bye...
21:02:32 <rachel> bye!
21:02:37 <eparsons> bye
21:02:37 <kerry> rrsagent, draft minutes
21:02:37 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html kerry
21:02:39 <RaulGarciaCastro> bye!
21:02:40 <KJanowicz_> bye bye
21:02:43 <phila> chair: Ed
21:02:46 <robin> Bye
21:02:49 <phila> RRSAgent, draft minutes
21:02:49 <RRSAgent> I have made the request to generate http://www.w3.org/2016/02/17-sdw-minutes.html phila
21:02:49 <kerry> rrsagent, make logs public
21:03:00 <kerry> bye!!
21:03:21 <phila> eparsons: Pls end the meeting in WebEx
21:03:32 <eparsons> wilco
21:03:41 <joshlieberman> bye
21:03:43 <joshlieberman> joshlieberman has left #sdw
22:20:53 <newton> newton has joined #sdw
23:18:25 <newton> newton has joined #sdw
23:30:46 <newton> newton has joined #sdw