Meeting minutes
Steven: the items today are all about <output mediatype=""/>
Steven to supply SVG example for <output mediatype="">
https://
Steven: A clock in SVG in an instance, where the hands are rotated from hours and minutes in another instance
Alain: OK
Erik: OK.
ACTION: Steven to add SVG example to spec
Action: Steven to propose wording for the 3-way split for output
@mediatype
https://
Alain: I have the same question about the meaning of the word 'data'
Alain: In xpath the data function yields the text
Steven: Ah, the meaning of the word 'data'.
… any suggestion on how to improve it?
… use 'content'?
Alain: Is an element 'content'?
Steven: Sure, why not?
Alain: Maybe because of the data function, misleads
Steven: How about adding 'data' to the glossary?
Alain: Works for me.
ACTION: Steven to add 'data' to glossary
Erik: Otherwise, I think it's fine, with the addition of the example.
Alain: What if the types don't match.
Steven: Let's add an explicit dispatch of output-error in that case.
ACTION: Steven update 3 way split text to include xforms-output-error
What to do when an <output> link fails
https://
Steven: New error, or use the existing submit-error?
Erik: I agree that submit-error is not good.
Steven: link-warning, identical to submit-error?
ACTION: Steven to add xforms-link-error to events.
AOB
[None]
<Steven> Next meeting: next week.
[ADJOURNED]