<trackbot> Date: 01 October 2014

TPAC meeting

http://www.w3.org/2014/11/TPAC/

Steven: We'll meet on the Friday that week.

Erik: OK. It's in my calendar
... 31st
... In the morning?

Steven: That's better for me.

Erik: It's Halloween, so the kids have a parade. I'll check when

Review of Section 1-3

http://lists.w3.org/Archives/Public/public-forms/2014Sep/0016

Steven: Thank you for the review.
... I had a few typogrphic things that I didn't post.
... I did add new text for the JSON representation, as we agreed at the last meeting. object="true" stuff
... I'm happy to make the changes both of you suggested.

<scribe> ACTION: Steven to update spec section 1-3 according to emails from Alain and Erik [recorded in http://www.w3.org/2014/10/01-forms-minutes.html#action01]

<trackbot> Created ACTION-1978 - Update spec section 1-3 according to emails from alain and erik [on Steven Pemberton - due 2014-10-08].

Steven: Section 1.5 has to be properly written, which is my task
... In section 2.1 examples we use label elements, but perhaps they should be attributes

Erik: To highlight the new syntax?

Steven: Yes

Erik: Fine.

Steven: Starting in section 3.2 we have the text [doesn't support AVT]
... but we don't explain that
... I suggest adding to section 2.7

Erik: It appears often. Is there a better formulation?
... add it to section 2.7

Steven: Good

Erik: Also mention that attributes that are XPath expressions do not support AVT

Steven: Yes, good.
... I agree with finding better wording for event dispatch. I'll work on that
... In 3.2.2 The instance element
... I missed an explanation for the difference between src and resource, and I didn;t know whether we should say something about
... it

Erik: The reason was for IBM to sign the document. Inline the instance in the document, a specific use-case.
... It's to change the order which things are checked.
... The rationale is very specific, and so hard to explain.

Steven: Leave as is, or is there something better we can say?

Erik: We should explain it.

Steven: I'll try and find a wording.
... The last note in this section seems to be in the wrong place.

Erik: I agree. Remove this note.

Steven: I agree
... In the CSV section 3.2.2.3
... we don't guarantee to roundtrip the header names
... which we do do for JSON
... so I'll give that some thought to see how it is doable in a simple way
... I think the easiest solution is a header row in the instance:
... <h><n>Name</n><n>Hex value</n</h>
... that doesn't interfere with the selectors, and you can reoutput it on serialisation

Alain: you could add it to the element,

Steven: Can you give an example?

<alain> <h><Name>Name</Name><Hex_Value>Hex Value</Hex_Value></h>

Steven: Oh as the header row. That works
... great
... That's all I had.

Erik: I'm happy to help fixing them.

Steven: Want to do your points 4 and 5?

Erik: Fine.

Steven: Next week section 4, 5 and 6.

[ADJOURN]

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/TO/To/
No ScribeNick specified.  Guessing ScribeNick: Steven_
Inferring Scribes: Steven_
Default Present: Steven_, ebruchez, [IPcaller]
Present: Steven_ ebruchez [IPcaller] Alain
Agenda: http://lists.w3.org/Archives/Public/public-forms/2014Oct/0000
Found Date: 01 Oct 2014
Guessing minutes URL: http://www.w3.org/2014/10/01-forms-minutes.html
People with action items: steven