See also: IRC log
<trackbot> Date: 20 June 2012
<Steven> code is xform
pfennell - Minutes Taker
<Steven> Scribe: pfennell
Seneca interested in support an event in using XForms for Business and Government.
Let Steven know about speakers for the event.
Philip to enquire if there are any UK people who would be interested in this event.
Event to, probably, be held at CWI.
Possible time-frame late September or beginning October.
Mike Kay confirmed usage of the function 'override' attribute.
Consensus is that this is not required for XForms 2.0. There are no good use-cases for this.
What should be the behaviour if two functions, with matching names/namespaces and arity are in scope?
<ebruchez> "It is a static error [err:XQST0034] if the expanded QName and arity (number of arguments) of the declared function are equal (as defined by the eq operator) to the expanded QName and arity of another function in function signatures."
Xquery does not have 'override'. Xquery raises a static error.
Nick wants the 'override' attribute.
<Steven> The optional override attribute defines what happens if this function has the same name and arity as a function provided by the implementer or made available in the static context using an implementation-defined mechanism. If the override attribute has the value yes, then this function is used in preference; if it has the value no, then the other function is used in preference. The default value is yes.
Does anyone object to the addition of the 'override' attribute?
There were no objects to the addition of the 'override' attribute.
Steven: The convincing case is declaring a function that's supported all but one implementation.
RESOLUTION: We will adopt @override, from XSLT 2.0, for function declarations.
Override will only apply to extension functions.
<nvdbleek> ACTION nvdbleek to specify that you can't override build-in functions
<trackbot> Created ACTION-1908 - Specify that you can't override build-in functions [on Nick Van Den Bleeken - due 2012-06-27].
<Steven> No reply from Leigh about checking schemas yet.
Erik: ID conflicts can occur if the same fragments is loaded via load/@embed
<Steven> (Sometimes I wish we had never used ID)
Steven: 'XML was not designed for
the things we use it for'.
... Could remove the xs:ID type from the @id?
Nick: 'Shadow Trees' are a possible solution to ID attribute scope.
Erik: Java has strong
encapsulation which is an example of a possible approach.
... We also need to consider the 'escape' of events.
... XForms 2.0 is defining 'simple' inclusions and more advance solutions should be added via extensions.
Steven: Where simple enclusions
have been implemented it is possible to have ID clashes.
... A helpful solution for the XForms user is to not to have to worry about ID clashes but this is at the expense of the implementer.
Repeating IDs are currently handled within xf:repeat.
Steven: To Alan, do you see any
disavantages to this?
... more discussion required for IDs.
... Hopefully the problem with requesting the first working draft for XForms 2.0 will be fixed.
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Steve/Steven/ Found Scribe: pfennell Inferring ScribeNick: pfennell Default Present: Steven, alain, +1.650.919.aaaa, ebruchez, +44.782.483.aacc, nvdbleek, Philip Present: Steven alain +1.650.919.aaaa ebruchez +44.782.483.aacc nvdbleek Philip Regrets: John Agenda: http://lists.w3.org/Archives/Public/public-forms/2012Jun/0026 Found Date: 20 Jun 2012 Guessing minutes URL: http://www.w3.org/2012/06/20-forms-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]