See also: IRC log
<magyarblip> i am +1.201 Patrick Johnston (magyarblip)
<pfps> arnaud: scribing is simple
<pfps> ...: two simple rules get you 99% of the way there
<Arnaud> PROPOSED: Approve minutes of the 20 November Telecon: http://www.w3.org/2014/11/20-shapes-minutes.html
<pfps> minutes look OK, particularly with the recent edits
<hknublau> +1
<SimonSteyskal> +1
+1
<jimkont> +1
RESOLUTION: Approve minutes of the 20 November Telecon: http://www.w3.org/2014/11/20-shapes-minutes.html
Arnaud: APPROVED
... discussing procedure for editing minutes - possible overwriting HTML if log is edited
<pfps> I'm happing with editing the IRC log, particularly as there is an original copy stored somewhere else
SimonSteyskal: Always type name of speaker into IRC logged so perl script will pick it up (avoid ...)
<SimonSteyskal> nono
<SimonSteyskal> just after a new topic
SimonSteyskal: correction, perl script only needs nickname when topic is changed
Arnaud: Always edit the IRC log, never edit the generated HTML
<pfps> agenda for today lists next meeting as today. I assume that the next meeting is next week (2014/12/11)
Arnaud: next meeting is Dec. 11
Arnaud: unable to find a date that works for everyone
<Arnaud> PROPOSED: F2F2 meeting at MIT the 17-19 February 2015
+1
<ericP> +1
<pfps> OK by me.
<SteveS> +1
<ericP> scribenick: arthur
<pfps> , but I'm not sure if I will be there physically.
RESOLUTION: F2F2 meeting at MIT the 17-19 February 2015
Arnaud: Holger raised concern about losing isses on the mailing list
... everyone should raise issues in the tracker
Arnaud: everyone should review user stories by next meeting so we can approve it next meeting
... record your concerns and we will discuss them next meeting
<Zakim> pfps, you wanted to say that putting notes in the document might be a good way to bring up concerns with the stories
<SimonSteyskal> +1
pfsp: propose that everyone should include comments in the user story documents
<Zakim> ericP, you wanted to boldly claim that the wiki probably supports CSS if we're lucky.
pfps: propose that everyone should include comments in the user story documents
ericP: suggest that we use wiki css to markup comments, need mediawiki guru
we use <arthur> blah blah </arthur>
<SHAPES> whoami
Arnaud: Karen is still discussing how Dublin Core will share their requirements
... suggest we start a wiki page for Requirements
ericP: I am OK to try to generate a requirements database extracted from the wiki
<SimonSteyskal> i could hardcode the (main) dc requirements into a wikipage
<SimonSteyskal> without fancy magic ;)
<ericP> arthur: can one embed javascript in a wiki page?
<Arnaud> http://www.w3.org/2014/10/rdfvalreqs/
<ericP> ... then the wiki page itself could render well
<hknublau> +q
<ericP> JSON source
hknublau: suggest that we establish a template so we can markup entries and then have the content parsed and displayed usefully
<ericP> playing with raw reqs in JSON
<scribe> ACTION: ericP will investigate how to get requirements into the wiki [recorded in http://www.w3.org/2014/12/04-shapes-minutes.html#action01]
<trackbot> Created ACTION-2 - Will investigate how to get requirements into the wiki [on Eric Prud'hommeaux - due 2014-12-11].
Arnaud: Holger listed the ways to associate shapes and graphs/resource/classes
<Zakim> pfps, you wanted to ask how this is related to issue-3
hknublau: summarized issue, describes use of classes for defining constraints
<SteveS> ISSUE-3?
<trackbot> ISSUE-3 -- How is a shape associated with a graph? -- open
<trackbot> http://www.w3.org/2014/data-shapes/track/issues/3
pfps: this issue should be about how to associate shapes, not what shapes are
<pfps> this issue should be about how to relate graphs to constraints, not what the endpoints of the associations can be within the graph
<Zakim> ericP, you wanted to say that we don't have to think of all the ways that shapes will be used.
ericP: describes analogy with XML Schema
... XML Schema was not prescriptive about how to apply schemas to XML documents
... this group should both define shapes and how to associate them
Arnaud: relates experience in XML WG
... e.g. LPD WG expects this WG to define association between LDP container and shapes
<hknublau> +q
hknublau: with Linked Data, we can dereference the rdf:type URI, or use owl:imports
... we should not specify mechanisms that are very specific, e.g. LPD, Hydra
... agree that we can split ISSUE-3 into orthogonal issues
<Zakim> pfps, you wanted to say that I'm willing to put my message into a wiki page for issue-3
<scribe> ACTION: hknublau will create a new issue to describe the aspect of ISSUE-3 that discuss the nature of shape resources [recorded in http://www.w3.org/2014/12/04-shapes-minutes.html#action02]
<trackbot> Created ACTION-3 - Will create a new issue to describe the aspect of issue-3 that discuss the nature of shape resources [on Holger Knublauch - due 2014-12-11].
<pfps> OK
<pfps> ACTION: pfps to create new wiki page for issue-3, seeded with his email message [recorded in http://www.w3.org/2014/12/04-shapes-minutes.html#action03]
<trackbot> Created ACTION-4 - Create new wiki page for issue-3, seeded with his email message [on Peter Patel-Schneider - due 2014-12-11].
<Arnaud> trackbot, end meeting