W3C

- DRAFT -

XForms Users Community Group Teleconference

09 Jan 2019

Agenda

Attendees

Present
Erik, Steven, Philip
Regrets
Alain
Chair
Steven
Scribe
Steven

Contents


Call January 23

[Steven will be unavailable]

Steven: I propose cancelling the call 23rd Jan

ACTION-2210: Fix submission to use single item binding

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0018

Steven: Done

Glossary

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0023

<ebruchez> Definition: An atomic value is a value in the value space of an atomic type, as defined in [XML Schema]

<ebruchez> https://www.w3.org/TR/xpath20/#id-basics

Steven: My suspicion is that we do all of this, and all references to XPath via the XPath Data Model

Erik: XPath 2 has a definition of Atomic value
... we say things about atomic values, so we do need a reference

Steven: Agreed.
... I think if we can use XDM, it would be better, because then our data model is defined in one place.

<scribe> ACTION: Steven to redefine terms via XDM instead of XPath[1, 2]

<trackbot> Created ACTION-2211 - Redefine terms via xdm instead of xpath[1, 2] [on Steven Pemberton - due 2019-01-16].

References to XPath in spec

https://lists.w3.org/Archives/Public/public-xformsusers/2019Jan/0003

Steven: Document and processor conformance use different versions of XPath; surely an oversight

Erik: I don't think we should be referring to XPath 1 anymore

Steven: Maybe we should just point to the Expressions spec instead,

Erik: That makes sense.
... it's a little unclear.
... There is a case for using the split XForms/expression language is to allow updating to XPath 3 with ease

Steven: If we can achieve that, it would be perfect.

ACTION-2196: Spec up collapsing sections

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0002

Steven: In progress.

XForms in 3D

https://lists.w3.org/Archives/Public/public-xformsusers/2018Dec/0011

Steven: How should we respond?

Philip: It's difficult to get involved in...
... Forms in general are rather 2D, but XForms can do so much more
... Problem is that there is no document flow in X3D
... without getting involved in implementation work, it's not clear how much could be achieved.

Steven: So should we offer advice if they need it, and leave it at that?

Philip: I think so. It's not clear what the use cases are...
... I'll just offer them out help if they want it.

XForms and host languages

https://lists.w3.org/Archives/Public/public-xformsusers/2019Jan/0000

Steven: Any further action?

Erik: I don't think so.

AOB

Steven: My XML Prague paper got accepted, so I will be there.
... Talk next week.

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Steven to redefine terms via XDM instead of XPath[1, 2]
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/01/09 14:22:13 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Erik Steven Philip
Regrets: Alain
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2019Jan/0004
Found Date: 09 Jan 2019
People with action items: steven

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]