invalid binding expression error

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

invalid binding expression error

ther
Readers,

I am trying to use the xforms (version 1) function of openoffice 3.
The native file format is an archive of xml files. I created a basic
document in writer and then preceeded to extract the odt file and open
the 'content.xml' file using a text editor (because using the writer
interface is too cumbersome and obscures my understanding of xforms
syntax). Below is the file. The question I have is that writer states
that the list menu (element 'select1', equivalent to 'listbox')
contains 'an invalid binding expression', but I cannot see where the
error is in the xforms elements.

<?xml version="1.0" encoding="UTF-8"?>
<office:document-content
xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"
xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0"
xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0"
xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0"
xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0"
xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0"
xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0"
xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0"
xmlns:math="http://www.w3.org/1998/Math/MathML"
xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0"
xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0"
xmlns:ooo="http://openoffice.org/2004/office"
xmlns:ooow="http://openoffice.org/2004/writer"
xmlns:oooc="http://openoffice.org/2004/calc"
xmlns:dom="http://www.w3.org/2001/xml-events"
xmlns:xforms="http://www.w3.org/2002/xforms"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rpt="http://openoffice.org/2005/report"
xmlns:of="urn:oasis:names:tc:opendocument:xmlns:of:1.2"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:grddl="http://www.w3.org/2003/g/data-view#"
xmlns:field="urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0"
office:version="1.2"
grddl:transformation="http://docs.oasis-open.org/office/1.2/xslt/odf2rdf.xsl">
        <office:scripts/>
        <office:font-face-decls>
                <style:font-face style:name="Liberation Serif"
svg:font-family="&apos;Liberation Serif&apos;"
style:font-family-generic="roman" style:font-pitch="variable"/>
                <style:font-face style:name="Liberation Sans"
svg:font-family="&apos;Liberation Sans&apos;"
style:font-family-generic="swiss" style:font-pitch="variable"/>
                <style:font-face style:name="DejaVu Sans"
svg:font-family="&apos;DejaVu Sans&apos;"
style:font-family-generic="system" style:font-pitch="variable"/>
        </office:font-face-decls>
        <office:automatic-styles>
                <style:style style:name="P1" style:family="paragraph">
                        <style:paragraph-properties fo:text-align="start"/>
                </style:style>
                <style:style style:name="P2" style:family="paragraph">
                        <style:paragraph-properties fo:text-align="center"/>
                </style:style>
                <style:style style:name="gr1" style:family="graphic">
                        <style:graphic-properties fo:border="solid #c0c0c0"
style:wrap="run-through" style:number-wrapped-paragraphs="no-limit"
style:vertical-pos="middle" style:vertical-rel="line"
style:horizontal-pos="from-left" style:horizontal-rel="paragraph"
draw:wrap-influence-on-position="once-concurrent"
style:flow-with-text="false"/>
                </style:style>
                <style:style style:name="gr2" style:family="graphic">
                        <style:graphic-properties style:wrap="run-through"
style:number-wrapped-paragraphs="no-limit" style:vertical-pos="middle"
style:vertical-rel="line" style:horizontal-pos="from-left"
style:horizontal-rel="paragraph"
draw:wrap-influence-on-position="once-concurrent"
style:flow-with-text="false"/>
                </style:style>
        </office:automatic-styles>
        <office:body>
                <office:text>
                        <office:forms form:automatic-focus="false" form:apply-design-mode="false">
                                <xforms:model id="entriespurposeanalysis">
                                        <xforms:instance>
                                                <purpose>
                                                        <analysis type="epc">epc england</analysis>
                                                        <analysis type="epc">epc scotland</analysis>
                                                </purpose>
                                        </xforms:instance>
                                        <xforms:bind id="analysistypes" nodeset="purpose/@type" type="xsd:string"/>
                                        <xsd:schema/>
                                </xforms:model>
                                <xforms:model id="general">
                                        <xforms:instance>
                                                <generalinformation>
                                                        <generalinformation/>
                                                </generalinformation>
                                        </xforms:instance>
                                        <xforms:submission id="savepagegeneralinformation"
bind="purpose/@type" action="file://~tmp/testsubmit.xml" method="put"
indent="false" omit-xml-declaration="false" standalone="false"
replace="none"/>
                                        <xsd:schema/>
                                </xforms:model>
                                <form:form form:name="Standard" form:apply-filter="true"
form:command-type="table"
form:control-implementation="ooo:com.sun.star.form.component.Form"
office:target-frame="" xlink:href="">
                                        <form:listbox form:name="List Box 1"
form:control-implementation="ooo:com.sun.star.form.component.ListBox"
form:id="control1" form:dropdown="true" form:size="20"
form:bound-column="1" xforms:bind="analysistypes"
form:xforms-list-source="analysistypes">
                                                <form:properties>
                                                        <form:property form:property-name="DefaultControl"
office:value-type="string"
office:string-value="com.sun.star.form.control.ListBox"/>
                                                        <form:list-property form:property-name="DefaultSelection"
office:value-type="float"/>
                                                </form:properties>
                                        </form:listbox>
                                        <form:button form:name="save page button"
form:control-implementation="ooo:com.sun.star.form.component.CommandButton"
form:id="control2" form:label="save" form:button-type="submit"
office:target-frame="" xlink:href="" form:image-data=""
form:xforms-submission="save" form:delay-for-repeat="PT0.50S"
form:image-position="center">
                                                <form:properties>
                                                        <form:property form:property-name="DefaultControl"
office:value-type="string"
office:string-value="com.sun.star.form.control.CommandButton"/>
                                                </form:properties>
                                        </form:button>
                                </form:form>
                        </office:forms>
                        <text:sequence-decls>
                                <text:sequence-decl text:display-outline-level="0"
text:name="Illustration"/>
                                <text:sequence-decl text:display-outline-level="0" text:name="Table"/>
                                <text:sequence-decl text:display-outline-level="0" text:name="Text"/>
                                <text:sequence-decl text:display-outline-level="0" text:name="Drawing"/>
                        </text:sequence-decls>
                        <text:p text:style-name="Standard">General information</text:p>
                        <text:p text:style-name="Standard"/>
                        <text:p text:style-name="Standard">Purpose of analysis:
<draw:control text:anchor-type="as-char" draw:z-index="0"
draw:style-name="gr1" draw:text-style-name="P1" svg:width="4.543cm"
svg:height="0.809cm" draw:control="control1"/>
                        </text:p>
                        <text:p text:style-name="Standard"/>
                        <text:p text:style-name="Standard">
                                <draw:control text:anchor-type="as-char" draw:z-index="1"
draw:style-name="gr2" draw:text-style-name="P2" svg:width="3.497cm"
svg:height="0.809cm" draw:control="control2"/>
                        </text:p>
                </office:text>
        </office:body>
</office:document-content>

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]> wrote:

>
> On 12 Sep 2010, at 02:05 , e-letter wrote:
>
>> Readers,
>>
>> I am trying to use the xforms (version 1) function of openoffice 3.
>> The native file format is an archive of xml files. I created a basic
>> document in writer and then preceeded to extract the odt file and open
>> the 'content.xml' file using a text editor (because using the writer
>> interface is too cumbersome and obscures my understanding of xforms
>> syntax). Below is the file. The question I have is that writer states
>> that the list menu (element 'select1', equivalent to 'listbox')
>> contains 'an invalid binding expression', but I cannot see where the
>> error is in the xforms elements.
>
> If I understand you correctly, the processor is complaining about
> List Box 1.  (That's the only listbox I see.)  The attribute-value
> specification
>
>      xforms:bind="analysistypes"
>
> points to the bind element with id="analysistypes", i.e.
>
>      <xforms:bind id="analysistypes"
>          nodeset="purpose/@type"
>          type="xsd:string"/>
>
> As far as I can tell, this is an 'outermost binding element' within
> the meaning of section 7.4 Evaluation Context, so its context node
> is the document element of the instance.  Your instance is given by
>
>      <xforms:instance>
>          <purpose>
>              <analysis type="epc">epc england</analysis>
>              <analysis type="epc">epc scotland</analysis>
>          </purpose>
>      </xforms:instance>
>
> Two things strike me about the nodeset expression on your bind element:
> (1) there is no type attribute on the purpose element, so there is
> nothing
> to bind to, and (2) the purpose element in the instance is the document
> element of the instance, and thus the context element for the XPath
> expression.  So the nodeset expression is looking for an element named
> 'purpose', which should be a child of the document element, also
> named 'purpose', and then for a 'type' attribute on that purposeful
> child of a purposeful parent.  So it's not going to select anything.
>
> The XForms spec says clearly, though, that "A binding expression
> attribute
> contains an XPath expression that references zero or more nodes of
> instance
> data."  (Appears in both 1.1 and 1.0.)  So it's not clear to me that
> failure
> to select any nodes is the reason for an "invalid binding expression";
> I would have expected the control just to be marked irrelevant.
>
> But I'm not seeing any other problems.  (The fact that you have two
> models instead of one seemed like a promising source of problems for
> a bit, but if that's the cause of your error I don't currently see
> how.)
>
I was trying an equivalent to a tutorial recommendation to populate a
list menu with another model element. In writer, there is a very small
area to enter list menu items on one line, I think separated by a
comma or similar punctuation. This discouraged me so I thought it
better to populate the list menu items with another model element.

> You might try rephrasing the nodeset value to "/purpose/analysis/@type"
> or "analysis/@type" (if that is what you actually intend) and see if
> that helps at all.
>
The latter worked thank you, but I wanted the user to see the values
(i.e. epc england, epc scotland), not the attributes.

Also, the submit element does not produce the output file. Any advice please?

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

C. M. Sperberg-McQueen-2

On 12 Sep 2010, at 10:54 , e-letter wrote:

> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>  
> wrote:
>
>> You might try rephrasing the nodeset value to "/purpose/analysis/
>> @type"
>> or "analysis/@type" (if that is what you actually intend) and see if
>> that helps at all.
>>
> The latter worked thank you, but I wanted the user to see the values
> (i.e. epc england, epc scotland), not the attributes.

That's a straightforward change to the XPath expression:
/purpose/analysis/@type points to the attribute, and to
point to the analysis element you want /purpose/analysis
or (given that /purpose is the document element and thus
in this case the context node) just "analysis".


>
> Also, the submit element does not produce the output file. Any  
> advice please?

I'm not sure exactly how the Open Office forms:* attributes
are expected to work, so my first guess is a pure speculation
based on general principles:  your 'save' button needs, somehow,
to be linked to a submission element.  I'm guessing that that's
the point of the form:xforms-submission attribute.  The value
of that attribute is "form", and I'd guess that the processor
is looking for a submission element with an ID or name or
label of "save".  If so, it's not finding one, since the only
xforms:submission element in the form you showed in your
original mail has an ID of "savepagegeneralinformation".

Another possible complication is that the xforms:submission
element in your second model has

   action="file://~tmp/testsubmit.xml"

but that's not really a legal file: URL, since "~tmp" is not
a legal host name.  If your aim is to save the file on the local
file system, you want the host name to be either 'localhost'
(so you have something beginning "file://localhost/...") or the
empty string, which is probably more common (so you have
something like "file:///...").  The path part of the URL you have
may be faulty, too -- at least, it looks a little unconventional.
In systems I'm familiar with, "~tmp" typically means the home
directory of the user named "tmp".  You may want either of

   file:///tmp/testsubmit.xml
   file:///~/tmp/testsubmit.xml

instead.  (Or not -- where you want to save the file is up to
you, and where you CAN save it is up to you and your softwre,
not me.)

The bind attribute on the xforms:submission element also may
need some attention:  right now its value is "purpose/@type",
which isn't legal:  the value of 'bind' should be an IDREF, and
the identifier specified should be the ID of some 'bind' element.
You only need it if you wish the submission to submit only
part of the instance in question, rather than the entire
instance, so it may simplify the task of getting the form
working if you just delete it for now and bring it back later
if you really want it.

I hope this helps.

--
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************





Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]> wrote:

>
> On 12 Sep 2010, at 10:54 , e-letter wrote:
>
>> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>
>> wrote:
>>
>>> You might try rephrasing the nodeset value to "/purpose/analysis/
>>> @type"
>>> or "analysis/@type" (if that is what you actually intend) and see if
>>> that helps at all.
>>>
>> The latter worked thank you, but I wanted the user to see the values
>> (i.e. epc england, epc scotland), not the attributes.
>
> That's a straightforward change to the XPath expression:
> /purpose/analysis/@type points to the attribute, and to
> point to the analysis element you want /purpose/analysis
> or (given that /purpose is the document element and thus
> in this case the context node) just "analysis".
>
Again, the latter suggestion works, thank you, but in truth I don't
understand this reference to the 'document element'. Could you point
to a relevant part of the specification that explains 'context node'
please?

>
>>
>> Also, the submit element does not produce the output file. Any
>> advice please?
>
> I'm not sure exactly how the Open Office forms:* attributes
> are expected to work, so my first guess is a pure speculation
> based on general principles:  your 'save' button needs, somehow,
> to be linked to a submission element.  I'm guessing that that's
> the point of the form:xforms-submission attribute.  The value
> of that attribute is "form", and I'd guess that the processor
> is looking for a submission element with an ID or name or
> label of "save".  If so, it's not finding one, since the only
> xforms:submission element in the form you showed in your
> original mail has an ID of "savepagegeneralinformation".
>

I tried to the bind element reference to 'savepagegeneralinformation'
but that failed, so removed the bind element in the submission element
as you subsequently described.

> Another possible complication is that the xforms:submission
> element in your second model has
>
>    action="file://~tmp/testsubmit.xml"
>
My typing mistake, sorry.

I looked at the output file 'testsubmit.xml' which appears as:

<?xml version="1.0"?>
<generalinformation>
                                                        <generalinformation/>
                                                </generalinformation>

This seems wrong to me; I was expecting the output to contain 'epc
england' if chosen from the list menu. Am I right to conclude that
this is a bug with writer?

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

C. M. Sperberg-McQueen-2
Comments interspersed.

On 13 Sep 2010, at 14:55 , e-letter wrote:

> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>  
> wrote:
>>
>> On 12 Sep 2010, at 10:54 , e-letter wrote:
>>
>>> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>
>>> wrote:
>>>
>>>> You might try rephrasing the nodeset value to "/purpose/analysis/
>>>> @type"
>>>> or "analysis/@type" (if that is what you actually intend) and see  
>>>> if
>>>> that helps at all.
>>>>
>>> The latter worked thank you, but I wanted the user to see the values
>>> (i.e. epc england, epc scotland), not the attributes.
>>
>> That's a straightforward change to the XPath expression:
>> /purpose/analysis/@type points to the attribute, and to
>> point to the analysis element you want /purpose/analysis
>> or (given that /purpose is the document element and thus
>> in this case the context node) just "analysis".
>>
> Again, the latter suggestion works, thank you, but in truth I don't
> understand this reference to the 'document element'.

In an XML document, the 'document element' is just the
outermost element of the document, the one within which all
the other elements appear.  Sometimes it's called the root
element.  The XPath spec uses the term without explanation, as
it's fairly standard XML terminology.

> Could you point
> to a relevant part of the specification that explains 'context node'
> please?

I don't see any full explanation of the idea of context node
in the XPath 1.0 or 1.1 spec -- it's not an XForms-specific
idea.

The 'context node' is the node in a document which serves
as the reference point for evaluating any context-dependent
parts of an XPath expression.  The idea is an important part
of XPath, and in order to provide an effective rule for
interpreting the XPath expressions in a form, the XForms
spec must specify how to determine the context node used
for the interpretation of any given expression.  That task is
performed by section 7.4 of the XPath 1.0 spec, 7.2 of the
1.1 spec.

If the concept is unfamiliar to you, you may find it helpful
to read some introductory tutorials on XPath.

>
>
> I looked at the output file 'testsubmit.xml' which appears as:
>
> <?xml version="1.0"?>
> <generalinformation>
> <generalinformation/>
> </generalinformation>

I think this means you got the submit to work.  Good!

> This seems wrong to me; I was expecting the output to contain 'epc
> england' if chosen from the list menu. Am I right to conclude that
> this is a bug with writer?

Probably not, as far as I can tell from the evidence I've
got.  Your submission element is a child of the second of
your two model elements, so what it submits (in the absence
of any instructions to the contrary) is the default instance
in that model, which has the shape you record above (a
generalinformation element containing another generalinformation
element).  The string 'epc england' is content in the default
instance of your *first* model, for which your form does not
currently define any submission.

I wonder if a simpler form might be easier to get started with?

HTH

Michael Sperberg-McQueen

--
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************





Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
On 13/09/2010, C. M. Sperberg-McQueen <[hidden email]> wrote:

> Comments interspersed.
>
> On 13 Sep 2010, at 14:55 , e-letter wrote:
>
>> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>
>> wrote:
>>>
>>> On 12 Sep 2010, at 10:54 , e-letter wrote:
>>>
>>>> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>
>>>> wrote:
>>>>
>>>>> You might try rephrasing the nodeset value to "/purpose/analysis/
>>>>> @type"
>>>>> or "analysis/@type" (if that is what you actually intend) and see
>>>>> if
>>>>> that helps at all.
>>>>>
>>>> The latter worked thank you, but I wanted the user to see the values
>>>> (i.e. epc england, epc scotland), not the attributes.
>>>
>>> That's a straightforward change to the XPath expression:
>>> /purpose/analysis/@type points to the attribute, and to
>>> point to the analysis element you want /purpose/analysis
>>> or (given that /purpose is the document element and thus
>>> in this case the context node) just "analysis".
>>>
>> Again, the latter suggestion works, thank you, but in truth I don't
>> understand this reference to the 'document element'.
>
> In an XML document, the 'document element' is just the
> outermost element of the document, the one within which all
> the other elements appear.  Sometimes it's called the root
> element.  The XPath spec uses the term without explanation, as
> it's fairly standard XML terminology.
>
Yes, I understood root element as I had seen reference to that term,
but never 'document element'.

>> Could you point
>> to a relevant part of the specification that explains 'context node'
>> please?
>
> I don't see any full explanation of the idea of context node
> in the XPath 1.0 or 1.1 spec -- it's not an XForms-specific
> idea.
>
> The 'context node' is the node in a document which serves
> as the reference point for evaluating any context-dependent
> parts of an XPath expression.  The idea is an important part
> of XPath, and in order to provide an effective rule for
> interpreting the XPath expressions in a form, the XForms
> spec must specify how to determine the context node used
> for the interpretation of any given expression.  That task is
> performed by section 7.4 of the XPath 1.0 spec, 7.2 of the
> 1.1 spec.
>
> If the concept is unfamiliar to you, you may find it helpful
> to read some introductory tutorials on XPath.
>
>>
>>
>> I looked at the output file 'testsubmit.xml' which appears as:
>>
>> <?xml version="1.0"?>
>> <generalinformation>
>> <generalinformation/>
>> </generalinformation>
>
> I think this means you got the submit to work.  Good!
>
>> This seems wrong to me; I was expecting the output to contain 'epc
>> england' if chosen from the list menu. Am I right to conclude that
>> this is a bug with writer?
>
> Probably not, as far as I can tell from the evidence I've
> got.  Your submission element is a child of the second of
> your two model elements, so what it submits (in the absence
> of any instructions to the contrary) is the default instance
> in that model, which has the shape you record above (a
> generalinformation element containing another generalinformation
> element).  The string 'epc england' is content in the default
> instance of your *first* model, for which your form does not
> currently define any submission.
>
> I wonder if a simpler form might be easier to get started with?
>
This concept of using two model elements originates from a writer
tutorial, advising to populate a list menu with elements from a second
model. Now I have discovered how to manipulate the writer content.xml
file without the writer user interface I will simplify the form with a
single model. Thank you!

> HTH
>
> Michael Sperberg-McQueen
>
> --
> ****************************************************************
> * C. M. Sperberg-McQueen, Black Mesa Technologies LLC
> * http://www.blackmesatech.com
> * http://cmsmcq.com/mib
> * http://balisage.net
> ****************************************************************
>
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
I have now simplified the form as shown below. Within the submission
element, I have tried to change the attribute 'replace' with values of
either 'none' or 'instance' as described in 'xforms for authors part
1', but the resultant output file is not produced. I also tried to
change the 'action' attribute with an absolute explicit path, without
success. What error have I made?

<?xml version="1.0" encoding="UTF-8"?>
<office:document-content
xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"
xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0"
xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0"
xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0"
xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0"
xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0"
xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0"
xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0"
xmlns:math="http://www.w3.org/1998/Math/MathML"
xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0"
xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0"
xmlns:ooo="http://openoffice.org/2004/office"
xmlns:ooow="http://openoffice.org/2004/writer"
xmlns:oooc="http://openoffice.org/2004/calc"
xmlns:dom="http://www.w3.org/2001/xml-events"
xmlns:xforms="http://www.w3.org/2002/xforms"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rpt="http://openoffice.org/2005/report"
xmlns:of="urn:oasis:names:tc:opendocument:xmlns:of:1.2"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:grddl="http://www.w3.org/2003/g/data-view#"
xmlns:field="urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0"
office:version="1.2"
grddl:transformation="http://docs.oasis-open.org/office/1.2/xslt/odf2rdf.xsl">
        <office:scripts/>
        <office:font-face-decls>
                <style:font-face style:name="Liberation Serif"
svg:font-family="&apos;Liberation Serif&apos;"
style:font-family-generic="roman" style:font-pitch="variable"/>
                <style:font-face style:name="Liberation Sans"
svg:font-family="&apos;Liberation Sans&apos;"
style:font-family-generic="swiss" style:font-pitch="variable"/>
                <style:font-face style:name="DejaVu Sans"
svg:font-family="&apos;DejaVu Sans&apos;"
style:font-family-generic="system" style:font-pitch="variable"/>
        </office:font-face-decls>
        <office:automatic-styles>
                <style:style style:name="P1" style:family="paragraph">
                        <style:paragraph-properties fo:text-align="start"/>
                </style:style>
                <style:style style:name="P2" style:family="paragraph">
                        <style:paragraph-properties fo:text-align="center"/>
                </style:style>
                <style:style style:name="gr1" style:family="graphic">
                        <style:graphic-properties fo:border="solid #c0c0c0"
style:wrap="run-through" style:number-wrapped-paragraphs="no-limit"
style:vertical-pos="middle" style:vertical-rel="line"
style:horizontal-pos="from-left" style:horizontal-rel="paragraph"
draw:wrap-influence-on-position="once-concurrent"
style:flow-with-text="false"/>
                </style:style>
                <style:style style:name="gr2" style:family="graphic">
                        <style:graphic-properties style:wrap="run-through"
style:number-wrapped-paragraphs="no-limit" style:vertical-pos="middle"
style:vertical-rel="line" style:horizontal-pos="from-left"
style:horizontal-rel="paragraph"
draw:wrap-influence-on-position="once-concurrent"
style:flow-with-text="false"/>
                </style:style>
        </office:automatic-styles>
        <office:body>
                <office:text>
                        <office:forms form:automatic-focus="false" form:apply-design-mode="false">
                                <xforms:model>
                                        <xforms:instance>
                                                <purpose>
                                                        <analysis type="epc">epc england</analysis>
                                                        <analysis type="epc">epc scotland</analysis>
                                                </purpose>
                                        </xforms:instance>
                                        <xforms:bind id="analysistypes" nodeset="analysis" type="xsd:string"/>
                                        <xforms:submission id="savepagegeneralinformation"
action="file://localhost/tmp/testsubmit.xml" method="put"
indent="false" omit-xml-declaration="false" standalone="false"
replace="instance"/>
                                        <xsd:schema/>
                                </xforms:model>
                                <form:form form:name="Standard" form:apply-filter="true"
form:command-type="table"
form:control-implementation="ooo:com.sun.star.form.component.Form"
office:target-frame="" xlink:href="">
                                        <form:listbox form:name="List Box 1"
form:control-implementation="ooo:com.sun.star.form.component.ListBox"
form:id="control1" form:dropdown="true" form:size="20"
form:bound-column="1" xforms:bind="analysistypes"
form:xforms-list-source="analysistypes">
                                                <form:properties>
                                                        <form:property form:property-name="DefaultControl"
office:value-type="string"
office:string-value="com.sun.star.form.control.ListBox"/>
                                                        <form:list-property form:property-name="DefaultSelection"
office:value-type="float"/>
                                                </form:properties>
                                        </form:listbox>
                                        <form:button form:name="save page button"
form:control-implementation="ooo:com.sun.star.form.component.CommandButton"
form:id="control2" form:label="save this page"
form:button-type="submit" office:target-frame="" xlink:href=""
form:image-data="" form:xforms-submission="savepagegeneralinformation"
form:delay-for-repeat="PT0.50S" form:image-position="center">
                                                <form:properties>
                                                        <form:property form:property-name="DefaultControl"
office:value-type="string"
office:string-value="com.sun.star.form.control.CommandButton"/>
                                                </form:properties>
                                        </form:button>
                                </form:form>
                        </office:forms>
                        <text:sequence-decls>
                                <text:sequence-decl text:display-outline-level="0"
text:name="Illustration"/>
                                <text:sequence-decl text:display-outline-level="0" text:name="Table"/>
                                <text:sequence-decl text:display-outline-level="0" text:name="Text"/>
                                <text:sequence-decl text:display-outline-level="0" text:name="Drawing"/>
                        </text:sequence-decls>
                        <text:p text:style-name="Standard">General information</text:p>
                        <text:p text:style-name="Standard"/>
                        <text:p text:style-name="Standard">Purpose of analysis:
<draw:control text:anchor-type="as-char" draw:z-index="0"
draw:style-name="gr1" draw:text-style-name="P1" svg:width="4.543cm"
svg:height="0.809cm" draw:control="control1"/>
                        </text:p>
                        <text:p text:style-name="Standard"/>
                        <text:p text:style-name="Standard">
                                <draw:control text:anchor-type="as-char" draw:z-index="1"
draw:style-name="gr2" draw:text-style-name="P2" svg:width="3.497cm"
svg:height="0.809cm" draw:control="control2"/>
                        </text:p>
                </office:text>
        </office:body>
</office:document-content>

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
On 14/09/2010, raja mani <[hidden email]> wrote:

> Rajamani M
> Chennai
> cell: 9791125383
>
>
> On Tue, Sep 14, 2010 at 6:23 PM, raja mani <[hidden email]> wrote:
>
>> Hi !!!
>>     Here u forgot to mention the "instance" attribute to replace the
>> instance, So u change like as below
>> <xforms:submission id="
>>>
>>> savepagegeneralinformation"
>>> action="file://localhost/tmp/testsubmit.xml" method="put"
>>> indent="false" omit-xml-declaration="false" standalone="false"
>>> replace="instance" instance="test"/>
>>
I do not understand; I do not have an element 'test'? If I remove the
attribute 'replace', according to the specification all information
should be selected, but this option fails also.

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

Swithun Crowe
Hello

e> >> <xforms:submission id="
e> >>> savepagegeneralinformation"
e> >>> action="file://localhost/tmp/testsubmit.xml" method="put"
e> >>> indent="false" omit-xml-declaration="false" standalone="false"
e> >>> replace="instance" instance="test"/>
e> >>

e> I do not understand; I do not have an element 'test'? If I remove the
e> attribute 'replace', according to the specification all information
e> should be selected, but this option fails also.

A few things may be going wrong here. I'm not sure what gets returned back
to the form from a PUT submission to the local file system. If nothing is
being sent back to the form, then there is nothing to replace anything
with.

If the @replace attribute says "instance", then the @instance attribute
says which instance to replace with whatever is returned from the
submission. If there is no @replace attribute, then I think the whole form
is replaced by whatever is returned from the submission. If nothing is
returned, the @replace should be "none".

I'm guessing that your form did have an instance called "test". If the
submission returned anything, then it would be put into this instance.

Hope this helps.

Swithun.

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

John Boyer
In reply to this post by ther

Hi everyone,

Use of the term "document element" comes right from the XML spec itself.  The document element is the root element of the XML document, the one matched by BNF rule #1 in the XML specification [1]

[1] http://www.w3.org/TR/REC-xml/#sec-well-formed

Definition 2 in [1] says "There is exactly one element, called the root, or *document element*, ..."

Note that the XForms spec may be a bit difficult to use to learn XForms, as it is first and foremost a specification for XForms processor developers.

That being said, helpful information on the context node for evaluating XPath expressions appears in Section 7 of XForms 1.1, and most notably in Sections 7.2 [2] and 7.4 [3].

[2] http://www.w3.org/TR/xforms11/#expr-eval
[3] http://www.w3.org/TR/xforms11/#expr-expression-categories

Best regards,
John Boyer



From: e-letter <[hidden email]>
To: "C. M. Sperberg-McQueen" <[hidden email]>
Cc: [hidden email]
Date: 09/13/2010 11:50 PM
Subject: Re: invalid binding expression error





On 13/09/2010, C. M. Sperberg-McQueen <[hidden email]> wrote:
> Comments interspersed.
>
> On 13 Sep 2010, at 14:55 , e-letter wrote:
>
>> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>
>> wrote:
>>>
>>> On 12 Sep 2010, at 10:54 , e-letter wrote:
>>>
>>>> On 12/09/2010, C. M. Sperberg-McQueen <[hidden email]>
>>>> wrote:
>>>>
>>>>> You might try rephrasing the nodeset value to "/purpose/analysis/
>>>>> @type"
>>>>> or "analysis/@type" (if that is what you actually intend) and see
>>>>> if
>>>>> that helps at all.
>>>>>
>>>> The latter worked thank you, but I wanted the user to see the values
>>>> (i.e. epc england, epc scotland), not the attributes.
>>>
>>> That's a straightforward change to the XPath expression:
>>> /purpose/analysis/@type points to the attribute, and to
>>> point to the analysis element you want /purpose/analysis
>>> or (given that /purpose is the document element and thus
>>> in this case the context node) just "analysis".
>>>
>> Again, the latter suggestion works, thank you, but in truth I don't
>> understand this reference to the 'document element'.
>
> In an XML document, the 'document element' is just the
> outermost element of the document, the one within which all
> the other elements appear.  Sometimes it's called the root
> element.  The XPath spec uses the term without explanation, as
> it's fairly standard XML terminology.
>
Yes, I understood root element as I had seen reference to that term,
but never 'document element'.

>> Could you point
>> to a relevant part of the specification that explains 'context node'
>> please?
>
> I don't see any full explanation of the idea of context node
> in the XPath 1.0 or 1.1 spec -- it's not an XForms-specific
> idea.
>
> The 'context node' is the node in a document which serves
> as the reference point for evaluating any context-dependent
> parts of an XPath expression.  The idea is an important part
> of XPath, and in order to provide an effective rule for
> interpreting the XPath expressions in a form, the XForms
> spec must specify how to determine the context node used
> for the interpretation of any given expression.  That task is
> performed by section 7.4 of the XPath 1.0 spec, 7.2 of the
> 1.1 spec.
>
> If the concept is unfamiliar to you, you may find it helpful
> to read some introductory tutorials on XPath.
>
>>
>>
>> I looked at the output file 'testsubmit.xml' which appears as:
>>
>> <?xml version="1.0"?>
>> <generalinformation>
>>                                                                                                                        <generalinformation/>
>>                                                                                                       </generalinformation>
>
> I think this means you got the submit to work.  Good!
>
>> This seems wrong to me; I was expecting the output to contain 'epc
>> england' if chosen from the list menu. Am I right to conclude that
>> this is a bug with writer?
>
> Probably not, as far as I can tell from the evidence I've
> got.  Your submission element is a child of the second of
> your two model elements, so what it submits (in the absence
> of any instructions to the contrary) is the default instance
> in that model, which has the shape you record above (a
> generalinformation element containing another generalinformation
> element).  The string 'epc england' is content in the default
> instance of your *first* model, for which your form does not
> currently define any submission.
>
> I wonder if a simpler form might be easier to get started with?
>
This concept of using two model elements originates from a writer
tutorial, advising to populate a list menu with elements from a second
model. Now I have discovered how to manipulate the writer content.xml
file without the writer user interface I will simplify the form with a
single model. Thank you!

> HTH
>
> Michael Sperberg-McQueen
>
> --
> ****************************************************************
> * C. M. Sperberg-McQueen, Black Mesa Technologies LLC
> *
http://www.blackmesatech.com
> *
http://cmsmcq.com/mib
> *
http://balisage.net
> ****************************************************************
>
>
>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
In reply to this post by Swithun Crowe
When the element 'submission' has the attribute ref="analysis/type",
the resultant output file is empty. The submission element is:

<xforms:submission id="savepagegeneralinformation"
action="file://~/tmp/testsubmit.xml" method="put" indent="false"
omit-xml-declaration="false" standalone="false"/>

When the attribute 'ref' is changed to ref="analysis" the output file is:

<?xml version="1.0"?>
<analysis type="epc">epc england</analysis>
<?xml version="1.0"?>
<analysis type="epc">epc scotland</analysis>

When the attribute 'ref' is removed, the output file is:

<?xml version="1.0"?>
<purpose>
                                                        <analysis type="epc">epc england</analysis>
                                                        <analysis type="epc">epc scotland</analysis>
                                                </purpose>

If the list menu in writer is used to choose 'epc england', the output
file should only show the element for the value of 'epc england',
correct? Also, even though the attribute 'indent' is set to 'false',
whitespace is applied.

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

John Boyer

Dear e-letter,

This is not really a forum for debugging your XForms forms, or the XPaths they contain.

It is not clear why your xforms:submission should work without adding replace="none" to it because it is a method="put" submission.  Particularly with a file scheme, I wouldn't expect anything to come back.

However, the reason you're getting nothing is that you seem to be using an element reference "type" that does not exist as a child element of "analysis".

It seems you are trying to ref the *attribute* called type, so you would have to use analysis/@type to reference that node.

That being said, XForms submissions write an XML document.  If you were to ref to analysis/@type, the result is not serializable as XML because it is only a (textual) attribute value.  So, this leaves the question of what you are trying to write.

The whole backstory thread is not available in this email and I haven't been wading through it all (due to sentence #1), but it sounds like you want to write an XML document containing only analysis elements whose type attribute matches a value like "epc".

You need to either use relevance, which may perhaps only be switched on for xforms-submit and back off for xforms-submit-done and -error, or you need to use the xforms:insert action to construct your data payload on xforms-submit.

Good luck,
John M. Boyer, Ph.D.
IBM Distinguished Engineer, Interactive Web Applications and Documents
IBM Lotus Forms Architect
Workplace, Portal and Collaboration Software
IBM Canada Software Lab, Victoria
E-Mail: [hidden email]  

Blog:
http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed:
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw




From: e-letter <[hidden email]>
To: Swithun Crowe <[hidden email]>
Cc: [hidden email]
Date: 09/14/2010 01:24 PM
Subject: Re: invalid binding expression error





When the element 'submission' has the attribute ref="analysis/type",
the resultant output file is empty. The submission element is:

<xforms:submission id="savepagegeneralinformation"
action="
file://~/tmp/testsubmit.xml" method="put" indent="false"
omit-xml-declaration="false" standalone="false"/>

When the attribute 'ref' is changed to ref="analysis" the output file is:

<?xml version="1.0"?>
<analysis type="epc">epc england</analysis>
<?xml version="1.0"?>
<analysis type="epc">epc scotland</analysis>

When the attribute 'ref' is removed, the output file is:

<?xml version="1.0"?>
<purpose>
                                                                                                                      <analysis type="epc">epc england</analysis>
                                                                                                                      <analysis type="epc">epc scotland</analysis>
                                                                                                     </purpose>

If the list menu in writer is used to choose 'epc england', the output
file should only show the element for the value of 'epc england',
correct? Also, even though the attribute 'indent' is set to 'false',
whitespace is applied.



Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

ther
On 14/09/2010, John Boyer <[hidden email]> wrote:
> Dear e-letter,
>
> This is not really a forum for debugging your XForms forms, or the XPaths
> they contain.
>
May I suggest better explanation of the purpose of the mailing list is
published. I will continue in another resource elsewhere; thanks to
all.

> It is not clear why your xforms:submission should work without adding
> replace="none" to it because it is a method="put" submission. Particularly
> with a file scheme, I wouldn't expect anything to come back.
>
According to the specification, if the replace attribute is absent,
all data is submitted (my interpretation of xforms1 section3.3.3;
cited because writer complies with version1).

> However, the reason you're getting nothing is that you seem to be using an
> element reference "type" that does not exist as a child element of
> "analysis".
>
Understood

> It seems you are trying to ref the *attribute* called type, so you would
> have to use analysis/@type to reference that node.
>
Tried that causing crash, will try to repeat to see if bug with writer
or my user error.

> That being said, XForms submissions write an XML document.  If you were to
> ref to analysis/@type, the result is not serializable as XML because it is
> only a (textual) attribute value.  So, this leaves the question of what
> you are trying to write.
>
In summary, to select an option from a list menu and the save the data
value associated with that option as an xml file.

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

John Boyer

Dear e-letter,

The replace attribute describes what will be replaced, not what will be submitted.  The default is replace="all" meaning that all of an instance will be replaced by whatever comes back from the submission.  The attribute which controls what gets submitted is ref, and if you leave out the ref, then all of the data in an instance is submitted.

I didn't catch the name of the processor you are using that had the crash; maybe you could mention it again next time.  However, I suspect it crashed when you properly identified the node you were interested in *because* it is an attribute, whereas the writer is expecting to output XML.  At the end of your email you said that you wanted to select an "option" (an attribute analysis/@type) then output that option as XML.  The problem is that the serialization of an attribute does not produce a well-formed XML document and therefore I would not expect XForms processors to produce an output.  We generally expect processor implementers to trap errors that lead to crashes, so it shouldn't crash, but nor should it have produced an output.

If you want to select one analysis element that has a particular type attribute value and output the whole analysis element, then you can do that with a predicate, like this

<xf:submission ref="analysis[@type = 'some value']" ... />

Since this attempts to output an XML element, and an element is a well-formed XML document, you'd be good to go.

However, in your last email it looked like you had more than one analysis element with the same type value.  In that case, the above ref would match more than one element, in which case processors are automatically programmed to select the first one (first node rule).  You can't output multiple XML elements without a wrapping containing element.  Multiple XML elements is a well-formed external general parsed entity, but not a well-formed XML document matching BNF rule #1 in the XML spec.  So, if you did need to output multiple matching analysis elements that have the same type attribute, you'd have to match the analysis element containing document with the submission ref, then use a relevant rule to prune the analysis elements you don't want.

Finally, with regard to the purpose of the mail list, I agree the term 'technical discussions' is perhaps confusing.  The working group has technical discussions about building xforms processors, such as new features for the next version of the language or errata for existing feature specifications.  The public, who may be building xforms processors but not on the working group or who may be trying to build a solution with xforms and find language features to be missing or hard to use, can participate in those technical discussions too.  By comparison, though, the above would be considered tutorial/debugging in nature.  Maybe the working group should set up a tutorial/debuggin discussion mail list.  I'll mention it on the call today.

Cheers,
John Boyer


From: e-letter <[hidden email]>
To: John Boyer/CanWest/IBM@IBMCA
Cc: Swithun Crowe <[hidden email]>, [hidden email]
Date: 09/15/2010 02:06 AM
Subject: Re: invalid binding expression error





On 14/09/2010, John Boyer <[hidden email]> wrote:
> Dear e-letter,
>
> This is not really a forum for debugging your XForms forms, or the XPaths
> they contain.
>
May I suggest better explanation of the purpose of the mailing list is
published. I will continue in another resource elsewhere; thanks to
all.

> It is not clear why your xforms:submission should work without adding
> replace="none" to it because it is a method="put" submission. Particularly
> with a file scheme, I wouldn't expect anything to come back.
>
According to the specification, if the replace attribute is absent,
all data is submitted (my interpretation of xforms1 section3.3.3;
cited because writer complies with version1).

> However, the reason you're getting nothing is that you seem to be using an
> element reference "type" that does not exist as a child element of
> "analysis".
>
Understood

> It seems you are trying to ref the *attribute* called type, so you would
> have to use analysis/@type to reference that node.
>
Tried that causing crash, will try to repeat to see if bug with writer
or my user error.

> That being said, XForms submissions write an XML document.  If you were to
> ref to analysis/@type, the result is not serializable as XML because it is
> only a (textual) attribute value.  So, this leaves the question of what
> you are trying to write.
>
In summary, to select an option from a list menu and the save the data
value associated with that option as an xml file.



Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

Klotz, Leigh
In reply to this post by ther
On 09/15/2010 02:00 AM, e-letter wrote:
Re: invalid binding expression error


May I suggest better explanation of the purpose of the mailing list is
published. I will continue in another resource elsewhere; thanks to
all.



At the Forms WG meeting today, we discussed this topic, and will be following through with your suggestion to clarify the mailing list purpose.

Personally, I suspect that many discussions will continue to start here, simply because this list is quite visible, but we will probably encourage some discussions to move to other places once the people involved get a clearer idea of what resources are available for their problem.  Language design issues will remain here, but in particular, we'd like to encourage bug reports and support requests for particular processors to take place on the vendor's resource pages.

Here's a quick rundown of some places to go for processor-specific XForms help (alphabetical).  Not all processors are listed; in particular, I've omitted those without an easily-found mailing list. 

There are many more implementations listed at http://www.w3.org/MarkUp/Forms/wiki/XForms_Implementations

---> Implementors, please feel free to respond with your support lists here.  We will collect the information and make it available. <---

betterFORM
http://www.betterform.de/jsp/forms.jsp

EMC Formula
https://community.emc.com/docs/DOC-4345
https://community.emc.com/community/edn/xmltech?view=discussions

FormFaces
https://sourceforge.net/projects/formfaces/support

Mozilla XForms Extension
https://lists.mozilla.org/listinfo/dev-tech-xforms

Orbeon XForms
http://www.orbeon.com/forms/community

PicoForms
http://www.picoforms.com/wiki/index.php?title=PicoForms_wiki:Community_portal

IBM Lotus Forms
http://www-947.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Forms
https://www.ibm.com/developerworks/lotus/products/forms/

Ubiquity XForms
http://code.google.com/p/ubiquity-xforms/
Doesn't mention a users group yet, but I suspect they'll have one soon.

XForms WikiBook
http://en.wikibooks.org/wiki/XForms

XSLTForms
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Leigh.

Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

John Boyer

In the case of Ubiquity XForms, there is a "users" group, though it is called a Developer group [1] , as opposed to a Contributor group [2].
Contributors to the open source project help to build the processor, and XForms Developers use the processor as part of the XForms-based applications they develop but do not contribute to the processor implementation.

[1] http://groups.google.com/group/ubiquity-xforms
[2] http://groups.google.com/group/ubiquity-xforms-eng

Based on the misunderstanding, I've added "(user)" and "(users)" in key places to clear it up.

Cheers,
John Boyer




From: Leigh L Klotz Jr <[hidden email]>
To: e-letter <[hidden email]>
Cc: John Boyer/CanWest/IBM@IBMCA, Swithun Crowe <[hidden email]>, [hidden email]
Date: 09/15/2010 11:02 AM
Subject: Re: invalid binding expression error





On 09/15/2010 02:00 AM, e-letter wrote:


May I suggest better explanation of the purpose of the mailing list is

published. I will continue in another resource elsewhere; thanks to

all.



At the Forms WG meeting today, we discussed this topic, and will be following through with your suggestion to clarify the mailing list purpose.

Personally, I suspect that many discussions will continue to start here, simply because this list is quite visible, but we will probably encourage some discussions to move to other places once the people involved get a clearer idea of what resources are available for their problem.  Language design issues will remain here, but in particular, we'd like to encourage bug reports and support requests for particular processors to take place on the vendor's resource pages.

Here's a quick rundown of some places to go for processor-specific XForms help (alphabetical).  Not all processors are listed; in particular, I've omitted those without an easily-found mailing list. 

There are many more implementations listed at
http://www.w3.org/MarkUp/Forms/wiki/XForms_Implementations

---> Implementors, please feel free to respond with your support lists here.  We will collect the information and make it available. <---

betterFORM

http://www.betterform.de/jsp/forms.jsp

EMC Formula

https://community.emc.com/docs/DOC-4345
https://community.emc.com/community/edn/xmltech?view=discussions

FormFaces

https://sourceforge.net/projects/formfaces/support

Mozilla XForms Extension

https://lists.mozilla.org/listinfo/dev-tech-xforms

Orbeon XForms

http://www.orbeon.com/forms/community

PicoForms

http://www.picoforms.com/wiki/index.php?title=PicoForms_wiki:Community_portal

IBM Lotus Forms

http://www-947.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Forms
https://www.ibm.com/developerworks/lotus/products/forms/

Ubiquity XForms

http://code.google.com/p/ubiquity-xforms/
Doesn't mention a users group yet, but I suspect they'll have one soon.

XForms WikiBook

http://en.wikibooks.org/wiki/XForms

XSLTForms

https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Leigh.


Reply | Threaded
Open this post in threaded view
|

Re: invalid binding expression error

Ronald van Kuijk-4
In reply to this post by Klotz, Leigh
For  betterFORM, I'd like to suggest using something completely different than the forms examples page ;-)
 
http://www.betterform.de/product.html#sourceforge

The user mailing list can be found there as wel as the developer list. The user list is for end-users e.g. embedding the engine (working *with* it, just using it), the developer list for people working *on* the engine.

Cheers,

Ronald

From: Leigh L Klotz Jr [mailto:[hidden email]]
To: e-letter [mailto:[hidden email]]
Cc: John Boyer [mailto:[hidden email]], Swithun Crowe [mailto:[hidden email]], [hidden email]
Sent: Wed, 15 Sep 2010 20:01:35 +0200
Subject: Re: invalid binding expression error

On 09/15/2010 02:00 AM, e-letter wrote:


May I suggest better explanation of the purpose of the mailing list is
published. I will continue in another resource elsewhere; thanks to
all.



At the Forms WG meeting today, we discussed this topic, and will be following through with your suggestion to clarify the mailing list purpose.

Personally, I suspect that many discussions will continue to start here, simply because this list is quite visible, but we will probably encourage some discussions to move to other places once the people involved get a clearer idea of what resources are available for their problem.  Language design issues will remain here, but in particular, we'd like to encourage bug reports and support requests for particular processors to take place on the vendor's resource pages.

Here's a quick rundown of some places to go for processor-specific XForms help (alphabetical).  Not all processors are listed; in particular, I've omitted those without an easily-found mailing list. 

There are many more implementations listed at http://www.w3.org/MarkUp/Forms/wiki/XForms_Implementations

---> Implementors, please feel free to respond with your support lists here.  We will collect the information and make it available. <---

betterFORM
http://www.betterform.de/jsp/forms.jsp

EMC Formula
https://community.emc.com/docs/DOC-4345
https://community.emc.com/community/edn/xmltech?view=discussions

FormFaces
https://sourceforge.net/projects/formfaces/support

Mozilla XForms Extension
https://lists.mozilla.org/listinfo/dev-tech-xforms

Orbeon XForms
http://www.orbeon.com/forms/community

PicoForms
http://www.picoforms.com/wiki/index.php?title=PicoForms_wiki:Community_portal

IBM Lotus Forms
http://www-947.ibm.com/support/entry/portal/Overview/Software/Lotus/Lotus_Forms
https://www.ibm.com/developerworks/lotus/products/forms/

Ubiquity XForms
http://code.google.com/p/ubiquity-xforms/
Doesn't mention a users group yet, but I suspect they'll have one soon.

XForms WikiBook
http://en.wikibooks.org/wiki/XForms

XSLTForms
https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Leigh.