Re: Custom properties

Hi Elliotte,

Further to Mark's email, note that it is in fact now intended that XForms 
can use property() to detect processor-specific functionality indicated by 
a colonized name (QNameButNotNCNAME). 
In the 1.1 spec, I gave two examples that could be implemented (locale and 
timezone).  To be honest, I added those two specific examples in the hope 
that most or all processors would add them in order to help fully test 
their ability to accept a QNameButNotNCNAME.  In the long term I hope 
these become required or recommended to implement as NCName keywords, but 
for now we are in feature lockdown, so I'll have to take what I can get 
here :-) 

Still, the nod to practical reality being in advance of standardization 
seemed desirable since at least an XForm can report when it doesn't have a 
necessary extension, for example.

Cheers,
John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer





Elliotte Harold <elharo@metalab.unc.edu> 
Sent by: www-forms-request@w3.org
07/09/2007 05:03 PM

To
www-forms@w3.org
cc

Subject
Custom properties








The XForms property XPath extension function returns the value of an 
XForms property. XForms only defines two properties, version and 
conformance-level.

Are individual XForms processors allowed to define their own properties
in addition to these basic two?

Do any do so, and if so what custom properties do they define?

-- 
Elliotte Rusty Harold  elharo@metalab.unc.edu
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/