14:07:43 <RRSAgent> RRSAgent has joined #csvw
14:07:43 <RRSAgent> logging to http://www.w3.org/2015/05/06-csvw-irc
14:07:51 <ivan> rrsagent, set log public
14:08:06 <danbri-user1> … if we had had more WG interest/expertise in this area, we might have gone deeper. Can put it on the list for 'if we get rechartered…'
14:08:25 <danbri-user1> jtandy: but we can discuss the union datatypes
14:08:36 <danbri-user1> … he says union datatypes don't address his problem
14:08:52 <JeniT> https://github.com/w3c/csvw/issues/223
14:08:53 <danbri-user1> #223 also
14:09:30 <danbri-user1> gkellogg: there's a complexity on the implementations that is at this point a major barrier. Adding this right now would be troubling for fledgling implementations.
14:09:45 <danbri-user1> … there are other ways to consider getting in multi-typing info
14:09:56 <danbri-user1> … the union types does address the same problem but not in his preferred manner
14:10:21 <danbri-user1> jenit: I agree. I'll go back to him on the xsd schemas aspect, to try to get to the bottom of it. But I don't think we need a lot more discussion here - we have some consensus.
14:10:32 <danbri-user1> jtandy: he could flesh it out and try to show how it would work
14:10:53 <danbri-user1> gkellogg: there are 2 aspects, … one is requirement that you implement the default xsd mechanism. The other is providing space to allow an unanticipated datatype.
14:11:17 <danbri-user1> Where the base could be say an IRI or a compact IRI or URI instead of one of our predefined tokens. That presumably could be added without too much pain.
14:11:26 <danbri-user1> jtandy: that doesn't support validation though?
14:11:40 <danbri-user1> gkellogg: it supports it to degree we support it for anything beyond time/numbers/booleans.
14:11:46 <danbri-user1> …(regex something)
14:12:16 <danbri-user1> jenit: if we want to support that, and it is quite a nice idea, having specialized datatypes which have names (URIs), … useful in both XML and RDF. If so, the way we should do that is an @id on the datatype …
14:12:22 <danbri-user1> gkellogg: but we have a field, it is the baes
14:12:24 <danbri-user1> base
14:12:27 <danbri-user1> jenit: that is different
14:12:41 <danbri-user1> … base tells you what kind of datatype, eg. Integer -> age
14:12:52 <danbri-user1> … min/max etc
14:13:16 <danbri-user1> jenit: having @id on datatype and using that within RDF (and or XML) conversion could be quite a nice thing
14:13:34 <danbri-user1> gkellogg: if the datatype had an ID, would be used in output otherwise use base
14:13:41 <danbri-user1> jtandy: and in json, we'd ignore it / use base
14:13:50 <danbri-user1> gkellogg: seems a reasonable extension point
14:13:58 <danbri-user1> jenit: shall i make a proposal? separate issue? ok...
14:14:14 <danbri-user1> (… will write that out after the call)
14:14:52 <danbri-user1> jenit: that would allow a named xsd datatype to be used, carried through, validated etc
14:15:01 <jtandy> [example: "datatype": {"base": "boolean", "format": "#|-", "@id": "http://example.org/mydatatype" }
14:15:06 <JeniT> https://github.com/w3c/csvw/issues/534
14:15:09 <danbri-user1> jenit: also: issue #534 from Gregg
14:15:28 <danbri-user1> gkellogg: seems to have been shot down
14:15:33 <danbri-user1> …. doesn't change any processing
14:15:48 <danbri-user1> … moves responsibility for specifics of metadata into metadata doc rather than datamodel
14:15:52 <danbri-user1> … but late in the game.
14:16:07 <danbri-user1> … maybe we need a status 'deferring for v2' label [in github]?
14:16:44 <danbri-user1> (ivan … would need to do this)
14:16:54 <danbri-user1> (label vs milestone)
14:17:13 <JeniT> ivan, please could you add a “vNext” label to Github so that we can label issues that we want to defer with it?
14:17:28 <danbri-user1> (schema.org has 'dim and distant  future, possible never' milestone: https://github.com/schemaorg/schemaorg/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22The+distant%2C+hazy+future+%28or+possibly+never%29%22 )
14:17:36 <gkellogg> And then set #534 to vNext
14:17:43 <danbri-user1> jenit: other open issues not flagged for discussion:
14:18:10 <ivan> I have created a "Deferred to Version 2" label to github
14:18:14 <danbri-user1> … waiting for I18n. Unions discussed. Changes - we know needs doing. Registration templ gone in. Data Cube 509:
14:18:20 <danbri-user1> https://github.com/w3c/csvw/issues/509
14:18:31 <danbri-user1> jtandy: done all needed doing. waited for a response, fine to close it.
14:18:34 <danbri-user1> +1 to close it
14:18:43 <danbri-user1> … could easily mark it as resolved. he's been emailed.
14:19:27 <danbri-user1> case insensitivity - close.
14:19:33 <danbri-user1> xsd - discussed
14:19:40 <danbri-user1> allowing metadata in csv files - …
14:19:47 <danbri-user1> gkellogg: we do talk about it, but don't say how
14:19:58 <danbri-user1> … just that it is a processor specific thing
14:20:59 <danbri-user1> [...]
14:21:26 <danbri-user1> gkellogg; we have made the ability to express arbitrary rdf from a csv rather general purpose
14:21:43 <danbri-user1> eg. you could have a csv that could be turned to json-ld to be a csvw metadata file
14:22:49 <danbri-user1> jtandy: net result from whatever arrangement needs to be an annotated table
14:22:56 <danbri-user1> see #534
14:23:04 <danbri-user1> gkellogg: someone could do this and be compatible
14:23:31 <danbri-user1> danbri: json-ld inside html via <script>?
14:23:45 <danbri-user1> gkellogg: "CSV" is fuzzy as needn't be actual CSV
14:23:53 <danbri-user1> tables … smiilar, considering html tables
14:24:38 <danbri-user1> jenit: afaik there is nothing in spec that stops you from saying an HTML file is a tabular data file, from which you can extract (viua some uknown process) some json metadata AND an annotated table model
14:25:15 <jtandy> s/viua/via/
14:25:27 <danbri-user1> gkellogg: if metadata is script tag w/ json-ld vfersion of our metadata
14:25:34 <danbri-user1> and table uri can be resolved to a table fragment
14:26:49 <danbri-user1> moving on,
14:26:54 <danbri-user1> #528:
14:27:04 <danbri-user1> document requirement for conneg for retrieving the context document
14:27:09 <danbri-user1> gkellogg: why to do this?
14:27:16 <danbri-user1> … an actual processor needn't have to do this
14:27:29 <danbri-user1> json-ld tool chains if used will handle this
14:27:38 <danbri-user1> not sure why we'll need to do something here
14:27:45 <jtandy> q+ to suggest that we add what gkellogg said as a note?
14:28:06 <danbri-user1> jenti: i think the issue just articulaltes reader's surprise.. .add a note?
14:28:10 <danbri-user1> gkellogg: ok, will do
14:28:14 <danbri-user1> jenit marks as editor action
14:28:16 <jtandy> q-
14:28:24 <danbri-user1> access control allow origin — ivan is doing this
14:28:27 <danbri-user1> or done
14:28:28 <jtandy> q?
14:28:36 <danbri-user1> … specifically for this context file
14:28:48 <danbri-user1> gkellogg: some q of whether it negotiates over anything but the json-ld
14:28:49 <jtandy> +1
14:28:52 <danbri-user1> jenit: can close?
14:28:53 <danbri-user1> +1
14:28:57 <danbri-user1> closed.
14:29:05 <danbri-user1> jenit: descr of line terminators. -> editor action.
14:29:16 <danbri-user1> … on the ns doc
14:29:30 <danbri-user1> gkellogg: I don't think we can close that one above. re accss control.
14:29:37 <danbri-user1> csvw vs csvw.jsonld
14:29:50 <danbri-user1> ah
14:29:56 <danbri-user1> gkellogg: sorry, it is done. Close!
14:30:00 <JeniT> https://github.com/w3c/csvw/issues/532
14:30:01 <danbri-user1> jenit: ok, closed.
14:30:17 <danbri-user1> #532 - editor action on gregg, update property definitions, line terminator, ...
14:30:33 <danbri-user1> jtandy: i took a look, don't consider it garbled. Name and then a title for that element.
14:30:47 <danbri-user1> not confusing, … but may look weird
14:31:00 <danbri-user1> jenit: description says […]
14:31:31 <danbri-user1> #534 - discussed.
14:31:47 <danbri-user1> … anything else needing progress e.g. use case doc?
14:31:58 <danbri-user1> gkellogg: also tests. I stalled out on generating a lot of new tests.
14:32:06 <danbri-user1> … probably another 100 tests, easily, if not more.
14:32:13 <danbri-user1> … a q of when to say "enough!"?
14:32:33 <danbri-user1> jenit: gkellogg, can you add issues like "add tests around section n" in github? to break up the work?
14:32:39 <danbri-user1> gkellogg: will do
14:33:04 <danbri-user1> jenit: that would be useful. Also usecase doc. Nothing back from Davide around reworking the requirements. Jeremy: can you take that on?
14:33:24 <danbri-user1> jtandy: struggling with bandwidth currently. Not a giant job to cross-ref but I would struggle to make time.
14:34:09 <danbri-user1> danbri; what exactly needs doing?
14:34:30 <jtandy> http://w3c.github.io/csvw/use-cases-and-requirements/#req
14:35:01 <danbri-user1> jtandy: 3.1 accepted requirements is blank. 3.2 candidate requirements. Consider 1st one: well formed csv check, …
14:35:37 <danbri-user1> … with most of these we have 1 liners. Felt to me as though now that we understand better what that requirement is as we've written the code, … can we flesh out meaning
14:35:59 <danbri-user1> jtandy: also a bunch that never made it out of candidate
14:36:21 <danbri-user1> jtandy: could try splitting it by the 4 sections
14:36:33 <danbri-user1> jenit: to split requirements out
14:36:48 <danbri-user1> … people then move them into either accepted, rejected, deferred
14:37:07 <danbri-user1> jtandy: lumpy distribution across sections
14:37:13 <danbri-user1> doc vs github?
14:37:17 <danbri-user1> jtandy: just do in the doc
14:37:38 <danbri-user1> jenit work in the doc directly.
14:37:59 <danbri-user1> jtandy: as a default position, all requirements listed as candidate should go into the Accepted list
14:38:10 <danbri-user1> if exception we should flag it in github for review.
14:40:51 <danbri-user1> [discussion of implementations]
14:40:52 <danbri-user1> rrsagent, please draft minutes
14:40:52 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/06-csvw-minutes.html danbri-user1
14:41:43 <danbri-user1> looking at start of meeting before rrsagent, the following text was typed:
14:41:54 <danbri-user1> JeniT https://github.com/w3c/csvw/issues/524
14:41:54 <danbri-user1> jenit: 2 issues require teleconf discussion. irc://irc.w3.org:6667/#524 re xsd schema datatypes, … …which I have tried to get some clarity on. Needs more discussion on github.
14:41:54 <danbri-user1> jtandy: seems we have someone who finds it simple to use xml schema, and perhaps doesn't appreciate how difficult others find it. But I don't want to have to make an xsd parser in e.g. Javascript.
14:41:59 <danbri-user1> rragent, please draft minutes
14:43:08 <ivan> rrsagent, draft minutes
14:43:08 <RRSAgent> I have made the request to generate http://www.w3.org/2015/05/06-csvw-minutes.html ivan
15:20:46 <danbri> danbri has joined #csvw
16:17:48 <danbri> danbri has joined #csvw
17:38:48 <JeniT> JeniT has joined #csvw
18:41:15 <betehess> betehess has joined #csvw
18:41:39 <betehess> betehess has left #csvw
19:20:36 <JeniT> JeniT has joined #csvw
20:37:52 <JeniT> JeniT has joined #csvw
22:40:33 <JeniT> JeniT has joined #csvw