Nabble - w3.org - www-forms

RE: Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

2009-12-10T00:49:39Z

I could see this being useful for “context aware” applications, e.g. different help/hint for different users e.g. Internal users vs. External, expert vs. novice users.

----------------------------------------------------------------------------------------------------------------

Dharmesh Mistry

Chief Technology & Operations Officer, edge IPK

E: dharmesh@...

M: +44 (0) 7789 222 015

T +44 (0) 1635 231 231 (ext 221)

F +44 (0) 1488 685 160

B: http://dharmeshmistry.wordpress.com

W: www.edgeipk.com

I am running the 2010 Virgin London Marathon and raising funds: Action For Children,

You can support me at: http://www.justgiving.com/dharmeshmistry2010

3 Station Yard, Station Road, Hungerford, Berkshire RG17 0DY

------------------------------------------------------------------------------------------------------------------------------
This message may contain information which is confidential or privileged.
If you are not the intended recipient, please advise the sender immediately by reply
e-mail and delete this message and any attachments without retaining a copy.

edge IPK Limited

Registered in England No. 4286817

From: www-forms-request@... [mailto:www-forms-request@...] On Behalf Of Joern Turner
Sent: 10 December 2009 08:21
To: John Boyer
Cc: www-forms@...
Subject: Re: Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

On 10.12.2009, at 01:33, John Boyer <boyerj@...> wrote:

Forwarding to public discussion list www-forms so that this question is also available to non-WG implementers and authors.

From:

"Klotz, Leigh" <Leigh.Klotz@...>

To:

<www-forms-editor@...>

Cc:

<public-forms@...>

Date:

12/09/2009 01:48 PM

Subject:

Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

In XForms 1.1 [1] the inline content model and linked schemas allow a plurality of help, hint, and alert elements per form control.
For example, at the end of section [2]:

Content Set Minimal Content Model
UI Common (help|hint|alert|Action)*

The Recommendation text gives no indication what more than one would do.

I raised this issue today [3] in the Forms WG teleconference.

In the past, there was group discussion about the advisability of using multiple label elements distinguished by xml:lang attributes, and we decided to support only one label element. One argument was that I18N best practice calls for external references.

As far as I can tell, we had no discussion about multiple help, hint, or alert elements, and I believe their allowance is a result of insufficient precision in the inline content model.

We have proposed that a future erratum for XForms 1.1 note in the prose that multiple such elements per form control is at best not interoperable, and further that the schema definitions for which it can be conveniently disallowed be changed to do so.

Are any implementors assigning special meaning to multiple help, hint, and alert elements?

No, in Chiba we support only one of each kind.

Leigh.

[1] http://www.w3.org/TR/2009/REC-xforms-20091020/
[2] http://www.w3.org/TR/2009/REC-xforms-20091020/#N74868
[3] http://lists.w3.org/Archives/Public/public-forms/2009Dec/att-0021/2009-12-09-v2.html#topic5

Re: Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

2009-12-10T00:20:31Z

On 10.12.2009, at 01:33, John Boyer <boyerj@...> wrote:

Forwarding to public discussion list www-forms so that this question is also available to non-WG implementers and authors.

From: "Klotz, Leigh" <Leigh.Klotz@...>
To: <www-forms-editor@...>
Cc: <public-forms@...>
Date: 12/09/2009 01:48 PM
Subject: Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

In XForms 1.1 [1] the inline content model and linked schemas allow a plurality of help, hint, and alert elements per form control. For example, at the end of section [2]: Content Set Minimal Content Model UI Common (help|hint|alert|Action)* The Recommendation text gives no indication what more than one would do. I raised this issue today [3] in the Forms WG teleconference. In the past, there was group discussion about the advisability of using multiple label elements distinguished by xml:lang attributes, and we decided to support only one label element. One argument was that I18N best practice calls for external references. As far as I can tell, we had no discussion about multiple help, hint, or alert elements, and I believe their allowance is a result of insufficient precision in the inline content model. We have proposed that a future erratum for XForms 1.1 note in the prose that multiple such elements per form control is at best not interoperable, and further that the schema definitions for which it can be conveniently disallowed be changed to do so. Are any implementors assigning special meaning to multiple help, hint, and alert elements?

No, in Chiba we support only one of each kind.

Leigh. [1]http://www.w3.org/TR/2009/REC-xforms-20091020/[2]http://www.w3.org/TR/2009/REC-xforms-20091020/#N74868[3]http://lists.w3.org/Archives/Public/public-forms/2009Dec/att-0021/2009-12-09-v2.html#topic5

Re: Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

2009-12-09T16:33:36Z

Forwarding to public discussion list www-forms so that this question is also available to non-WG implementers and authors.

From:	"Klotz, Leigh" <Leigh.Klotz@...>
To:	<www-forms-editor@...>
Cc:	<public-forms@...>
Date:	12/09/2009 01:48 PM
Subject:	Question to XForms authors and implementors: Multiple help, hint, alert elements per form control?

In XForms 1.1 [1] the inline content model and linked schemas allow a plurality of help, hint, and alert elements per form control. For example, at the end of section [2]: Content Set Minimal Content Model UI Common (help|hint|alert|Action)* The Recommendation text gives no indication what more than one would do. I raised this issue today [3] in the Forms WG teleconference. In the past, there was group discussion about the advisability of using multiple label elements distinguished by xml:lang attributes, and we decided to support only one label element. One argument was that I18N best practice calls for external references. As far as I can tell, we had no discussion about multiple help, hint, or alert elements, and I believe their allowance is a result of insufficient precision in the inline content model. We have proposed that a future erratum for XForms 1.1 note in the prose that multiple such elements per form control is at best not interoperable, and further that the schema definitions for which it can be conveniently disallowed be changed to do so. Are any implementors assigning special meaning to multiple help, hint, and alert elements? Leigh. [1]http://www.w3.org/TR/2009/REC-xforms-20091020/[2]http://www.w3.org/TR/2009/REC-xforms-20091020/#N74868[3]http://lists.w3.org/Archives/Public/public-forms/2009Dec/att-0021/2009-12-09-v2.html#topic5

Re: Javascript implementation limitation

2009-12-04T09:06:15Z

Joern will correct me if I am wrong, but my understanding is that Chiba and Orbeon have a similar approach and that in Chiba as well most of serious the XForms processing is done on the server.

-Erik

On Fri, Dec 4, 2009 at 4:21 AM, Mats Eklund <mats.eklund@...> wrote:

btw, I'm not familiar with chiba. how much of the processing is done client-side in chiba? one reason I'm prefering client-side solution is for responsiveness of the ui. other server side implementations introduce a lag which is not acceptable for my app.

--- On Fri, 12/4/09, Joern Turner <joernturner@...> wrote:

From: Joern Turner <joernturner@...>
Subject: Re: Javascript implementation limitation
To: "Mats Eklund" <mats.eklund@...>
Cc: www-forms@...
Date: Friday, December 4, 2009, 10:00 AM

Mats,

On Dec 3, 2009, at 10:21 PM, Mats Eklund wrote:

> Hi,
>
>
> I'm weighing pros and cons of two xforms implementations, one is a server side implementation and the other is a browser side implementation in javascript. It appears to me that one inherent limitation of a javascript implementation is that xforms submissions with replace="all" is impossible to achieve. Any insights welcome?
>
That's not right. In Chiba we support submission/@replace="all". Though it comes to the price of having an additional URI param on the resulting URL. On the other hand you can always substitute a replace all with a combination of submission and load.

Regards,

Joern

>
> Thanks,
>
> Mats
>
>

Re: Javascript implementation limitation

2009-12-04T04:21:26Z

btw, I'm not familiar with chiba. how much of the processing is done client-side in chiba? one reason I'm prefering client-side solution is for responsiveness of the ui. other server side implementations introduce a lag which is not acceptable for my app.

--- On Fri, 12/4/09, Joern Turner <joernturner@...> wrote:

From: Joern Turner <joernturner@...>
Subject: Re: Javascript implementation limitation
To: "Mats Eklund" <mats.eklund@...>
Cc: www-forms@...
Date: Friday, December 4, 2009, 10:00 AM

Mats,

On Dec 3, 2009, at 10:21 PM, Mats Eklund wrote:

> Hi,
>
>
> I'm weighing pros and cons of two xforms implementations, one is a server side implementation and the other is a browser side implementation in javascript. It appears to me that one inherent limitation of a javascript implementation is that xforms submissions with replace="all" is impossible to achieve. Any insights welcome?
>
That's not right. In Chiba we support submission/@replace="all". Though it comes to the price of having an additional URI param on the resulting URL. On the other hand you can always substitute a replace all with a combination of submission and load.

Regards,

Joern

>
> Thanks,
>
> Mats
>
>

Re: Javascript implementation limitation

2009-12-04T04:07:48Z

submission then load is how I currently do it, however, this requires the server to be tweaked to respond with a redirect in a non-conventional way. By conventional I'm referring to the "PRG pattern" (http://en.wikipedia.org/wiki/Post/Redirect/Get). As long as this pattern isn't used, there is no problem. Maybe xforms was not intended to be used with this pattern...?

--- On Fri, 12/4/09, Joern Turner <joernturner@...> wrote:

From: Joern Turner <joernturner@...>
Subject: Re: Javascript implementation limitation
To: "Mats Eklund" <mats.eklund@...>
Cc: www-forms@...
Date: Friday, December 4, 2009, 10:00 AM

Mats,

On Dec 3, 2009, at 10:21 PM, Mats Eklund wrote:

> Hi,
>
>
> I'm weighing pros and cons of two xforms implementations, one is a server side implementation and the other is a browser side implementation in javascript. It appears to me that one inherent limitation of a javascript implementation is that xforms submissions with replace="all" is impossible to achieve. Any insights welcome?
>
That's not right. In Chiba we support submission/@replace="all". Though it comes to the price of having an additional URI param on the resulting URL. On the other hand you can always substitute a replace all with a combination of submission and load.

Regards,

Joern

>
> Thanks,
>
> Mats
>
>

RE: Javascript implementation limitation

2009-12-04T03:44:49Z

Hi Mats,

I'm in charge of XSLTForms project and I agree with you about this problem.

Have a look at http://old.nabble.com/A-new-submit-method-for-implementing-replace%3D%22all%22-with-Javascript----td20638952.html

Best regards,
Alain Couthures
<agenceXML>
Bordeaux, France
http://www.agencexml.com/xsltforms

Hi,

I'm weighing pros and cons of two xforms implementations, one is a server side implementation and the other is a browser side implementation in javascript. It appears to me that one inherent limitation of a javascript implementation is that xforms submissions with replace="all" is impossible to achieve. Any insights welcome?

Thanks,
Mats

Re: Javascript implementation limitation

2009-12-04T01:00:59Z

Mats,

On Dec 3, 2009, at 10:21 PM, Mats Eklund wrote:

> Hi,
>
>
> I'm weighing pros and cons of two xforms implementations, one is a
> server side implementation and the other is a browser side
> implementation in javascript. It appears to me that one inherent
> limitation of a javascript implementation is that xforms submissions
> with replace="all" is impossible to achieve. Any insights welcome?
>
That's not right. In Chiba we support submission/@replace="all".
Though it comes to the price of having an additional URI param on the
resulting URL. On the other hand you can always substitute a replace
all with a combination of submission and load.

Regards,

Joern

>
> Thanks,
>
> Mats
>
>

Javascript implementation limitation

2009-12-03T13:21:24Z

Hi,

I'm weighing pros and cons of two xforms implementations, one is a server side implementation and the other is a browser side implementation in javascript. It appears to me that one inherent limitation of a javascript implementation is that xforms submissions with replace="all" is impossible to achieve. Any insights welcome?

Thanks,

Mats

Need better usage of QName datatypes in XForms submissions

2009-11-23T16:41:07Z

The current XForms submission has an attribute called includenamespacesprefixes.

If you leave out this attribute, the submitted instance may receive numerous namespaces declarations from the containing document that are not declared on the root element of the instance itself.

If you add includenamespaceprefixes="", then the list of namespaces added to the root element is attenuated to those that are *visibly utilized*.

If you add a space separated list, e.g. includenamespaceprefixes="xforms xf xsd", then the namespaces added to those declared on the root element is the set of inherited namespaces that are *visibly utilized* plus those listed prefixes (if they do indeed exist as defined namespace prefixes).

The term *visibly utilized* was borrowed from exclusive canonicalization and refers to the namespace prefix being used in an element or attribute declaration.

A namespace prefix may also be used in an attribute value or other content. In this case, the prefix is not visibly utilized in the XML sense but is still needed in order for the submitted instance data to be reasonably interpreted. Indeed we added includenamespaceprefixes as an attempt to address this problem.

As we continue to write more mature products that interact with XForms-produced data, we're seeing some gaps here. An important case in point is the xsi:type attribute. It may contain a value like "xforms:date", but the prefix xforms is not visibly utilized, and so the submission data does not have the prefix if one has used includenamespaceprefixes="". This makes the data unusable by schema validating server-side modules.

In this case, we could make authors fix the problem by setting includenamespaceprefixes="xf xforms xsd" or some such, but making the form author fix the problem is a bandage solution that will become less tenable over time as we go further into componentization.

In the long run, it would be better to have our own definition of "visibly utilizing" an XML namespace that accommodates any QName datatype assignments. For example, xsi:type is defined as a QName in the XML schema schema. Generally, if the datatype of a node is QName, either from a type MIP or an available schema, then the XForms submission should look at the value of that node for additional namespace prefixes that may be in use.

We could even adopt a cheeky name for our new concept, such as "visibly using" the namespace, since after all you should use utilize when you can reasonably utilize use.

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

Short term req for XForms needed ASAP

2009-11-02T14:48:32Z

Hi,

I have a short term requirement for XForms in Greenbelt, MD (close to DC) and this is a contract position.

Duration: Initially 3 months ...(may extend another 3 months)

Visa status: US Citizen

If anybody is interested , please send your resume to Mulpuru1@... with your rate/hr and availablilty.

Thanks

Srini

Re: Inserting attributes from one instance to another

2009-10-23T13:22:17Z

Thanks for the update.
-Winona

On Fri, Oct 23, 2009 at 2:49 PM, John Boyer <boyerj@...> wrote:

Hi Winona,

FWIW, in answer to the question "is this supported", your syntax does follow the pattern described in appendix B.4:
http://www.w3.org/TR/xforms11/#data-mutation-patterns-set-attribute

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

From: Aaron Reed <aaronr@...>
To: www-forms@...
Date: 10/23/2009 11:43 AM
Subject: Re: Inserting attributes from one instance to another

It seems like a bug in our code. At least I could recreate your issue with a testcase that I think is valid (fails in our code, works in Orbeon). I opened a bug on it ->https://bugzilla.mozilla.org/show_bug.cgi?id=524164--Aaron Winona Salesky wrote: > Sorry, that is just a cut and past issue. This code works in Orbeon, and > I believe it used to work with the firefox extension, but I'm not sure > when it stopped working. > -Winon > > On Fri, Oct 23, 2009 at 8:55 AM, Charles F Wiecha <wiecha@... > <wiecha@...>> wrote: > > Do you have an extra blank in your context xpath or is that just a > cut&paste issue? Charlie Wiecha > > > Inactive hide details for Winona Salesky ---10/23/2009 08:11:13 > AM---I've been using the firefox extntion for a while and you Winona > Salesky ---10/23/2009 08:11:13 AM---I've been using the firefox > extntion for a while and you used to be able to insert attributes from > > > From: > Winona Salesky <wsalesky@... <wsalesky@...>> > > To: > www-forms@... <www-forms@...> > > Date: > 10/23/2009 08:11 AM > > Subject: > Inserting attributes from one instance to another > > Sent by: > www-forms-request@... <www-forms-request@...> > > ------------------------------------------------------------------------ > > > > I've been using the firefox extntion for a while and you used to be > able to insert attributes from one instance to another using the > following syntax: > <xforms:trigger appearance="minimal" ref="self::node()[not(@type)]"> > <xforms:label>Add type</xforms:label> > <xforms:insert ev:event="DOMActivate" > context="instance('metadata')//mods:mods/ > mods:titleInfo[index('titleInfo')]" > origin="instance('template')/mods:titleInfo/@type"/> > </xforms:trigger> > > > This does not appear to work anymore, is my syntax wrong, or is this > no longer supported? > > Thanks. > > -Winona > >

Re: Inserting attributes from one instance to another

2009-10-23T11:49:20Z

Hi Winona,

FWIW, in answer to the question "is this supported", your syntax does follow the pattern described in appendix B.4:
http://www.w3.org/TR/xforms11/#data-mutation-patterns-set-attribute

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

From:	Aaron Reed <aaronr@...>
To:	www-forms@...
Date:	10/23/2009 11:43 AM
Subject:	Re: Inserting attributes from one instance to another

It seems like a bug in our code. At least I could recreate your issue with a testcase that I think is valid (fails in our code, works in Orbeon). I opened a bug on it ->https://bugzilla.mozilla.org/show_bug.cgi?id=524164--Aaron Winona Salesky wrote: > Sorry, that is just a cut and past issue. This code works in Orbeon, and > I believe it used to work with the firefox extension, but I'm not sure > when it stopped working. > -Winon > > On Fri, Oct 23, 2009 at 8:55 AM, Charles F Wiecha <wiecha@... > <mailto:wiecha@...>> wrote: > > Do you have an extra blank in your context xpath or is that just a > cut&paste issue? Charlie Wiecha > > > Inactive hide details for Winona Salesky ---10/23/2009 08:11:13 > AM---I've been using the firefox extntion for a while and you Winona > Salesky ---10/23/2009 08:11:13 AM---I've been using the firefox > extntion for a while and you used to be able to insert attributes from > > > From: > Winona Salesky <wsalesky@... <mailto:wsalesky@...>> > > To: > www-forms@... <www-forms@...> > > Date: > 10/23/2009 08:11 AM > > Subject: > Inserting attributes from one instance to another > > Sent by: > www-forms-request@... <www-forms-request@...> > > ------------------------------------------------------------------------ > > > > I've been using the firefox extntion for a while and you used to be > able to insert attributes from one instance to another using the > following syntax: > <xforms:trigger appearance="minimal" ref="self::node()[not(@type)]"> > <xforms:label>Add type</xforms:label> > <xforms:insert ev:event="DOMActivate" > context="instance('metadata')//mods:mods/ > mods:titleInfo[index('titleInfo')]" > origin="instance('template')/mods:titleInfo/@type"/> > </xforms:trigger> > > > This does not appear to work anymore, is my syntax wrong, or is this > no longer supported? > > Thanks. > > -Winona > >

Re: Inserting attributes from one instance to another

2009-10-23T11:16:02Z

It seems like a bug in our code. At least I could recreate your issue
with a testcase that I think is valid (fails in our code, works in
Orbeon). I opened a bug on it ->
https://bugzilla.mozilla.org/show_bug.cgi?id=524164

--Aaron

Winona Salesky wrote:

> Sorry, that is just a cut and past issue. This code works in Orbeon, and
> I believe it used to work with the firefox extension, but I'm not sure
> when it stopped working.
> -Winon
>
> On Fri, Oct 23, 2009 at 8:55 AM, Charles F Wiecha <wiecha@...
> <mailto:wiecha@...>> wrote:
>
> Do you have an extra blank in your context xpath or is that just a
> cut&paste issue? Charlie Wiecha
>
>
> Inactive hide details for Winona Salesky ---10/23/2009 08:11:13
> AM---I've been using the firefox extntion for a while and you Winona
> Salesky ---10/23/2009 08:11:13 AM---I've been using the firefox
> extntion for a while and you used to be able to insert attributes from
>
>
> From:
> Winona Salesky <wsalesky@... <mailto:wsalesky@...>>
>
> To:
> www-forms@... <mailto:www-forms@...>
>
> Date:
> 10/23/2009 08:11 AM
>
> Subject:
> Inserting attributes from one instance to another
>
> Sent by:
> www-forms-request@... <mailto:www-forms-request@...>
>
> ------------------------------------------------------------------------
>
>
>
> I've been using the firefox extntion for a while and you used to be
> able to insert attributes from one instance to another using the
> following syntax:
> <xforms:trigger appearance="minimal" ref="self::node()[not(@type)]">
> <xforms:label>Add type</xforms:label>
> <xforms:insert ev:event="DOMActivate"
> context="instance('metadata')//mods:mods/
> mods:titleInfo[index('titleInfo')]"
> origin="instance('template')/mods:titleInfo/@type"/>
> </xforms:trigger>
>
>
> This does not appear to work anymore, is my syntax wrong, or is this
> no longer supported?
>
> Thanks.
>
> -Winona
>
>

Re: Inserting attributes from one instance to another

2009-10-23T06:45:17Z

Sorry, that is just a cut and past issue. This code works in Orbeon, and I believe it used to work with the firefox extension, but I'm not sure when it stopped working.
-Winon

On Fri, Oct 23, 2009 at 8:55 AM, Charles F Wiecha <wiecha@...> wrote:

Do you have an extra blank in your context xpath or is that just a cut&paste issue? Charlie Wiecha

Winona Salesky ---10/23/2009 08:11:13 AM---I've been using the firefox extntion for a while and you used to be able to insert attributes from

From:
Winona Salesky <wsalesky@...>

To:
www-forms@...

Date:
10/23/2009 08:11 AM

Subject:
Inserting attributes from one instance to another

Sent by:
www-forms-request@...

I've been using the firefox extntion for a while and you used to be able to insert attributes from one instance to another using the following syntax:
<xforms:trigger appearance="minimal" ref="self::node()[not(@type)]">
    <xforms:label>Add type</xforms:label>
     <xforms:insert ev:event="DOMActivate" context="instance('metadata')//mods:mods/ mods:titleInfo[index('titleInfo')]"
           origin="instance('template')/mods:titleInfo/@type"/>
</xforms:trigger>

This does not appear to work anymore, is my syntax wrong, or is this no longer supported?

Thanks.

-Winona

Re: Inserting attributes from one instance to another

2009-10-23T05:55:28Z

Do you have an extra blank in your context xpath or is that just a cut&paste issue? Charlie Wiecha

Winona Salesky ---10/23/2009 08:11:13 AM---I've been using the firefox extntion for a while and you used to be able to insert attributes from

From:	Winona Salesky <wsalesky@...>
To:	www-forms@...
Date:	10/23/2009 08:11 AM
Subject:	Inserting attributes from one instance to another
Sent by:	www-forms-request@...

I've been using the firefox extntion for a while and you used to be able to insert attributes from one instance to another using the following syntax:
<xforms:trigger appearance="minimal" ref="self::node()[not(@type)]">
    <xforms:label>Add type</xforms:label>
     <xforms:insert ev:event="DOMActivate" context="instance('metadata')//mods:mods/ mods:titleInfo[index('titleInfo')]"
           origin="instance('template')/mods:titleInfo/@type"/>
</xforms:trigger>

This does not appear to work anymore, is my syntax wrong, or is this no longer supported?

Thanks.

-Winona

Fw: Digital signature problem

2009-10-23T00:22:22Z

Sir,

I Deepak Tewani is a new member of W3C. I request you to please try to take your time out in reading this mail and removing my issues in xforms.

I am trying to apply digital signature on the xml file generated through xforms document.

I want to develop the code that will develop a button on xforms document and after clicking on the button it will digitally sign the xml file generated throug xforms.

The code that i have written is as follows , kindly reply if there is any need for modification of the code,

The code is..

<html 
 xmlns="http://www.w3.org/1999/xhtml" 
 xmlns:xforms="http://www.w3.org/2002/xforms" 
 xmlns:ev="http://www.w3.org/2001/xml-events"
 xmlns:xs="http://www.w3.org/2001/XMLSchema"

 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#"
 xmlns:custom="http://www.ibm.com/xmlns/prod/XFDL/Custom" 
 xmlns:designer="http://www.ibm.com/xmlns/prod/workplace/forms/designer/2.6" 
 xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
 xmlns:dsxp="http://www.w3.org/2002/06/xmldsig-filter2" 
 xmlns:sigmeta="http://www.ibm.com/xmlns/prod/forms/signature/metadata/1.0"
 
 xmlns:xfdl="http://www.ibm.com/xmlns/prod/XFDL/7.6">

<head>

<xforms:model>

<xforms:instance id="GeneratedInstance" xmlns="">
   <generated>
                 
      <test/>
      <PAGE1>
         <BUTTON1>
             <ds:Signature>

             
   <ds:SignedInfo>
                   <ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:CanonicalizationMethod>
                   <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1">
                   </ds:SignatureMethod>
                   <ds:Reference>
                      <ds:Transforms>
                         <ds:Transform Algorithm="http://www.w3.org/2002/06/xmldsig-filter2">
                            <dsxp:XPath Filter="subtract">/xfdl:XFDL/xfdl:globalpage/xfdl:global/xfdl:xformsmodels/xforms:model/xforms:instance[@id="GeneratedInstance"]/generated/PAGE1/BUTTON1/ds:Signature</dsxp:XPath>

                         </ds:Transform>
     
                 </ds:Transforms>
                      <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">
 
                     </ds:DigestMethod>
                      <ds:DigestValue></ds:DigestValue>
                   </ds:Reference>
                   <ds:Reference URI="">
                      <ds:Transforms>
                         <ds:Transform Algorithm="http://www.w3.org/2002/06/xmldsig-filter2">

                         <dsxp:XPath Filter="intersect">here()/ancestor::ds:Signature[1]/ds:Object[sigmeta:metadata]</dsxp:XPath>
        
 
                </ds:Transform>
                       </ds:Transforms>
                       <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                      
 <ds:DigestValue></ds:DigestValue>
                   </ds:Reference>
                 </ds:SignedInfo>
              <ds:SignatureValue></ds:SignatureValue>

              <ds:Object>
                 <sigmeta:metadata>
                    <sigmeta:timestamp>
                       <sigmeta:signtime></sigmeta:signtime>
                      
 <sigmeta:dst></sigmeta:dst>
               
        <sigmeta:date></sigmeta:date>
                    </sigmeta:timestamp>
                    <sigmeta:signformat>
                    application/signature+xml;
             
          engine="GenericRSA"
                    </sigmeta:signformat>

       
 
         </sigmeta:metadata>
              </ds:Object>
           </ds:Signature>
         </BUTTON1>
      </PAGE1>
   </generated>
</xforms:instance>

 <xforms:submission id="saveDoc" action="data.xml" replace="none" method="put"
 />
		<xforms:submission
 id="loadDoc" action="data.xml" replace="instance" method="get"/>

<xforms:signature
 ref="ds:Signature" id="X">
<xforms:action ev:event="signature-create">
Actions to prepare dsig:Signature
</xforms:action>
<xforms:action ev:event="signature-create-done">
Actions to post-process success
</xforms:action>
<xforms:action ev:event="signature-create-error">
Actions that respond to failure
</xforms:action>

</xforms:signature>


</xforms:model>

<!-- <script language="javascript" type="text/javascript">

			function setCertStr(cert) {
				document.getElementById('cert_data').value = '';
				document.getElementById('cert_data').value = cert;
			}
			
	
	</script> -->

</head>
<body>
<p>name</p>
<xforms:input ref="test"/>

<xforms:button sid="BUTTON1">
         <xforms:trigger
 ref="instance('GeneratedInstance')/PAGE1/
               BUTTON1/ds:Signature/ds:SignatureValue">
            <xforms:label>Click to Sign</xforms:label>
         </xforms:trigger>
         <xforms:itemlocation>

            <below>FIELD3</below>
            <width>246</width>
         </xforms:itemlocation>
         <xforms:value compute="signer == 'INVALID' ? invalid() : signer">
         </xforms:value>
         <xforms:type>signature</xforms:type>
         <xforms:signer></xforms:signer>

         <signformat>application/signature+xml;engine="GenericRSA"</signformat>


      </xforms:button>
<!-- <textarea rows="6" cols="50" id="cert_data"></textarea>
    
       <applet code="gov.nic.keyupload.gui.KeyRegister.class"
        		archive="sign.jar,plugin.jar" 
        		width="500" height="150" name="CertRead" id="CertRead">
        	<param name="appType" value="read" />
        </applet> -->
         
    <xforms:submit submission="saveDoc">
			<xforms:label>Save Doc</xforms:label>
		</xforms:submit>

		<xforms:submit submission="loadDoc">

			<xforms:label>Load Doc</xforms:label>
		</xforms:submit>

</body>
</html>

Please reply me ..

Thanks and Regads,
Deepak Tewani
Programmer
NIC

Digital signature problem

2009-10-22T23:34:59Z

Sir,

I am trying to apply digital signature on the xml file generated through xforms document.

I want to develop the code that will develop a button on xforms document and after clicking on the button it will digitally sign the xml file generated throug xforms.

The code that i have written is as follows , kindly reply if there is any need for modification of the code,

The code is..

<html 
 xmlns="http://www.w3.org/1999/xhtml" 
 xmlns:xforms="http://www.w3.org/2002/xforms" 
 xmlns:ev="http://www.w3.org/2001/xml-events"
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#"
 xmlns:custom="http://www.ibm.com/xmlns/prod/XFDL/Custom" 
 xmlns:designer="http://www.ibm.com/xmlns/prod/workplace/forms/designer/2.6" 
 xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
 xmlns:dsxp="http://www.w3.org/2002/06/xmldsig-filter2" 
 xmlns:sigmeta="http://www.ibm.com/xmlns/prod/forms/signature/metadata/1.0" 
 xmlns:xfdl="http://www.ibm.com/xmlns/prod/XFDL/7.6">

<head>

<xforms:model>

<xforms:instance id="GeneratedInstance" xmlns="">
   <generated>
                 
      <test/>
      <PAGE1>
         <BUTTON1>
             <ds:Signature>

                <ds:SignedInfo>
                   <ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:CanonicalizationMethod>
                   <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1">
                   </ds:SignatureMethod>
                   <ds:Reference>
                      <ds:Transforms>
                         <ds:Transform Algorithm="http://www.w3.org/2002/06/xmldsig-filter2">
                            <dsxp:XPath Filter="subtract">/xfdl:XFDL/xfdl:globalpage/xfdl:global/xfdl:xformsmodels/xforms:model/xforms:instance[@id="GeneratedInstance"]/generated/PAGE1/BUTTON1/ds:Signature</dsxp:XPath>

                         </ds:Transform>
     
                 </ds:Transforms>
                      <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">
                      </ds:DigestMethod>
                      <ds:DigestValue></ds:DigestValue>
                   </ds:Reference>
                   <ds:Reference URI="">
                      <ds:Transforms>
                         <ds:Transform Algorithm="http://www.w3.org/2002/06/xmldsig-filter2">

                         <dsxp:XPath Filter="intersect">here()/ancestor::ds:Signature[1]/ds:Object[sigmeta:metadata]</dsxp:XPath>
                         </ds:Transform>
                       </ds:Transforms>
                       <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                       <ds:DigestValue></ds:DigestValue>
                   </ds:Reference>
                 </ds:SignedInfo>
              <ds:SignatureValue></ds:SignatureValue>

              <ds:Object>
                 <sigmeta:metadata>
                    <sigmeta:timestamp>
                       <sigmeta:signtime></sigmeta:signtime>
                       <sigmeta:dst></sigmeta:dst>
               
        <sigmeta:date></sigmeta:date>
                    </sigmeta:timestamp>
                    <sigmeta:signformat>
                    application/signature+xml;
                       engine="GenericRSA"
                    </sigmeta:signformat>

                 </sigmeta:metadata>
              </ds:Object>
           </ds:Signature>
         </BUTTON1>
      </PAGE1>
   </generated>
</xforms:instance>

 <xforms:submission id="saveDoc" action="data.xml" replace="none" method="put" />
		<xforms:submission id="loadDoc" action="data.xml" replace="instance" method="get"/>

<xforms:signature ref="ds:Signature" id="X">
<xforms:action ev:event="signature-create">
Actions to prepare dsig:Signature
</xforms:action>
<xforms:action ev:event="signature-create-done">
Actions to post-process success
</xforms:action>
<xforms:action ev:event="signature-create-error">
Actions that respond to failure
</xforms:action>

</xforms:signature>


</xforms:model>

<!-- <script language="javascript" type="text/javascript">

			function setCertStr(cert) {
				document.getElementById('cert_data').value = '';
				document.getElementById('cert_data').value = cert;
			}
			
		</script> -->

</head>
<body>
<p>name</p>
<xforms:input ref="test"/>

<xforms:button sid="BUTTON1">
         <xforms:trigger
 ref="instance('GeneratedInstance')/PAGE1/
               BUTTON1/ds:Signature/ds:SignatureValue">
            <xforms:label>Click to Sign</xforms:label>
         </xforms:trigger>
         <xforms:itemlocation>

            <below>FIELD3</below>
            <width>246</width>
         </xforms:itemlocation>
         <xforms:value compute="signer == 'INVALID' ? invalid() : signer">
         </xforms:value>
         <xforms:type>signature</xforms:type>
         <xforms:signer></xforms:signer>

         <signformat>application/signature+xml;engine="GenericRSA"</signformat>


      </xforms:button>
<!-- <textarea rows="6" cols="50" id="cert_data"></textarea>
    
       <applet code="gov.nic.keyupload.gui.KeyRegister.class"
        		archive="sign.jar,plugin.jar" 
        		width="500" height="150" name="CertRead" id="CertRead">
        	<param name="appType" value="read" />
        </applet> -->
         
    <xforms:submit submission="saveDoc">
			<xforms:label>Save Doc</xforms:label>
		</xforms:submit>

		<xforms:submit submission="loadDoc">

			<xforms:label>Load Doc</xforms:label>
		</xforms:submit>

</body>
</html>

Please reply me ..

Thanks and Regads,
Deepak Tewani
Programmer
NIC

Digital signature problem

2009-10-22T23:34:42Z

<html 
 xmlns="http://www.w3.org/1999/xhtml" 
 xmlns:xforms="http://www.w3.org/2002/xforms" 
 xmlns:ev="http://www.w3.org/2001/xml-events"
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#"
 xmlns:custom="http://www.ibm.com/xmlns/prod/XFDL/Custom" 
 xmlns:designer="http://www.ibm.com/xmlns/prod/workplace/forms/designer/2.6" 
 xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
 xmlns:dsxp="http://www.w3.org/2002/06/xmldsig-filter2" 
 xmlns:sigmeta="http://www.ibm.com/xmlns/prod/forms/signature/metadata/1.0" 
 xmlns:xfdl="http://www.ibm.com/xmlns/prod/XFDL/7.6">

<head>

<xforms:model>

<xforms:instance id="GeneratedInstance" xmlns="">
   <generated>
                 
      <test/>
      <PAGE1>
         <BUTTON1>
             <ds:Signature>

                <ds:SignedInfo>
                   <ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:CanonicalizationMethod>
                   <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1">
                   </ds:SignatureMethod>
                   <ds:Reference>
                      <ds:Transforms>
                         <ds:Transform Algorithm="http://www.w3.org/2002/06/xmldsig-filter2">
                            <dsxp:XPath Filter="subtract">/xfdl:XFDL/xfdl:globalpage/xfdl:global/xfdl:xformsmodels/xforms:model/xforms:instance[@id="GeneratedInstance"]/generated/PAGE1/BUTTON1/ds:Signature</dsxp:XPath>

                         </ds:Transform>
     
                 </ds:Transforms>
                      <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1">
                      </ds:DigestMethod>
                      <ds:DigestValue></ds:DigestValue>
                   </ds:Reference>
                   <ds:Reference URI="">
                      <ds:Transforms>
                         <ds:Transform Algorithm="http://www.w3.org/2002/06/xmldsig-filter2">

                         <dsxp:XPath Filter="intersect">here()/ancestor::ds:Signature[1]/ds:Object[sigmeta:metadata]</dsxp:XPath>
                         </ds:Transform>
                       </ds:Transforms>
                       <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                       <ds:DigestValue></ds:DigestValue>
                   </ds:Reference>
                 </ds:SignedInfo>
              <ds:SignatureValue></ds:SignatureValue>

              <ds:Object>
                 <sigmeta:metadata>
                    <sigmeta:timestamp>
                       <sigmeta:signtime></sigmeta:signtime>
                       <sigmeta:dst></sigmeta:dst>
               
        <sigmeta:date></sigmeta:date>
                    </sigmeta:timestamp>
                    <sigmeta:signformat>
                    application/signature+xml;
                       engine="GenericRSA"
                    </sigmeta:signformat>

                 </sigmeta:metadata>
              </ds:Object>
           </ds:Signature>
         </BUTTON1>
      </PAGE1>
   </generated>
</xforms:instance>

 <xforms:submission id="saveDoc" action="data.xml" replace="none" method="put" />
		<xforms:submission id="loadDoc" action="data.xml" replace="instance" method="get"/>

<xforms:signature ref="ds:Signature" id="X">
<xforms:action ev:event="signature-create">
Actions to prepare dsig:Signature
</xforms:action>
<xforms:action ev:event="signature-create-done">
Actions to post-process success
</xforms:action>
<xforms:action ev:event="signature-create-error">
Actions that respond to failure
</xforms:action>

</xforms:signature>


</xforms:model>

<!-- <script language="javascript" type="text/javascript">

			function setCertStr(cert) {
				document.getElementById('cert_data').value = '';
				document.getElementById('cert_data').value = cert;
			}
			
		</script> -->

</head>
<body>
<p>name</p>
<xforms:input ref="test"/>

<xforms:button sid="BUTTON1">
         <xforms:trigger
 ref="instance('GeneratedInstance')/PAGE1/
               BUTTON1/ds:Signature/ds:SignatureValue">
            <xforms:label>Click to Sign</xforms:label>
         </xforms:trigger>
         <xforms:itemlocation>

            <below>FIELD3</below>
            <width>246</width>
         </xforms:itemlocation>
         <xforms:value compute="signer == 'INVALID' ? invalid() : signer">
         </xforms:value>
         <xforms:type>signature</xforms:type>
         <xforms:signer></xforms:signer>

         <signformat>application/signature+xml;engine="GenericRSA"</signformat>


      </xforms:button>
<!-- <textarea rows="6" cols="50" id="cert_data"></textarea>
    
       <applet code="gov.nic.keyupload.gui.KeyRegister.class"
        		archive="sign.jar,plugin.jar" 
        		width="500" height="150" name="CertRead" id="CertRead">
        	<param name="appType" value="read" />
        </applet> -->
         
    <xforms:submit submission="saveDoc">
			<xforms:label>Save Doc</xforms:label>
		</xforms:submit>

		<xforms:submit submission="loadDoc">

			<xforms:label>Load Doc</xforms:label>
		</xforms:submit>

</body>
</html>

Please reply me ..

Thanks and Regads,
Deepak Tewani
Programmer
NIC

Inserting attributes from one instance to another

2009-10-22T19:03:49Z

Re: XForms 1.1 is a W3C Recommendation

2009-10-21T16:06:52Z

Excellent! Thanks to everyone in the WG for all of your long hard work.

--Aaron

John Boyer wrote:

>
> It's official, XForms 1.1 is a W3C Recommendation.
> See the www.w3.org main page now.
>
> Also, for W3C members, please see the announcement to the AC:
> http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html
>
> Congratulations to the Forms WG and the Forms community.
>
> Best regards,
> John M. Boyer, Ph.D.
> STSM, Interactive Documents and Web 2.0 Applications
> Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@...
>
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
> Blog RSS feed:
> http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
>

Re: XForms 1.1 is a W3C Recommendation

2009-10-21T15:54:28Z

Scott,

yes AFAIK you are right. But this does not mean that there are no
mature and powerful implementations out there that have been proven in
a lot of real-life projects. I agree that from an interoperability
point of view we still have to do some work. On the other hand XForms
1.1 is such a big improvement over 1.0 that it's probably not
astonishing that the implementers haven't addressed all new
functionality yet. But be sure that we're working on it. For my part i
can say that we're beyond 95% now and have automated the testsuite for
regression testing. Stay tuned and i'm sure you'll see conformant
processors in the public space within a few weeks or months from now.

Probably it would be worth for the WG to think about doing less in one
step. This would certainly make the implemeners life easier and
probably lead to fully conformant processors in shorter time. But
there was hardly a chance to do so for 1.1 as so many lessons-learned
had to be addressed. Hope there will be a chance for 1.2 but in a
world that ask for features features features ...

Anyway i think the WG did fantastic work and XForms will have a bright
future within the xml technology toolset AND it's definitely a
technology you can use right now.

Joern
On Wednesday, October 21, 2009, Scott Shattuck <idearat@...> wrote:

> While I applaud the work of the XForms group I have to note that none of the implementation reports appear to be without failures, some in areas I'd consider significant such as event dispatch and submission processing. So in fact, there do not appear to be any fully-compliant implementations of the 1.1 specification at this time. Is that correct?
>
> ss
>
> On Oct 21, 2009, at 1:59 PM, John Boyer wrote:
>
>
> Advancement to W3C Proposed Recommendation(PR),
> which is the step before the one announced here that occurred in August,
> is supported by an implementation report containing results from numerous
> implementations. The implementation report link appears in the PR
> status section. A number of these implementations are open source
> projects.
>
>
> Cheers,
>
> John M. Boyer, Ph.D.
> STSM, Interactive Documents and Web 2.0 Applications
> Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@... <javascript:_e({}, 'cvml', 'boyerj@...');>
>
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
> Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
>
>
>
>
>
>
>
> From:
> Kai-Uwe Behrmann <ku.b@... <javascript:_e({}, 'cvml', 'ku.b@...');>>
>
> To:
> John Boyer/CanWest/IBM@IBMCA
>
> Cc:
> public-forms@... <javascript:_e({}, 'cvml', 'public-forms@...');>, www-forms@... <javascript:_e({}, 'cvml', 'www-forms@...');>
>
> Date:
> 10/21/2009 12:31 PM
>
> Subject:
> Re: XForms 1.1 is a W3C Recommendation
>
>
>
>
>
> May I ask,
> where is the reference implementation to XFORMS 1.1?
>
>
> kind regards
> Kai-Uwe Behrmann
> --
> developing for colour management
> www.behrmann.name
> + www.oyranos.org
>
>
> Am 20.10.09, 14:41 -0700 schrieb John Boyer:
>> It's official, XForms 1.1 is a W3C Recommendation.
>> See the www.w3.org
> main page now.
>>
>> Also, for W3C members, please see the announcement to the AC:
>> http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html
>>
>> Congratulations to the Forms WG and the Forms community.
>>
>> Best regards,
>> John M. Boyer, Ph.D.
>> STSM, Interactive Documents and Web 2.0 Applications
>> Chair, W3C Forms Working Group
>> Workplace, Portal and Collaboration Software
>> IBM Victoria Software Lab
>> E-Mail: boyerj@... <javascript:_e({}, 'cvml', 'boyerj@...');>
>>
>> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
>> Blog RSS feed:
>> http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
>>
>>
>
>
>
>
>
>

New how-to about repeat and insert

2009-10-21T15:05:38Z

All,

Here is a new how-to about inserting a new item into a repeat:

http://wiki.orbeon.com/forms/how-to/repeat-insert-position

This is a slightly tricky topic, which we thought was worth documenting.

Feedback is welcome!

Enjoy,

-Erik

Re: XForms 1.1 is a W3C Recommendation

2009-10-21T14:35:01Z

While I applaud the work of the XForms group I have to note that none of the implementation reports appear to be without failures, some in areas I'd consider significant such as event dispatch and submission processing. So in fact, there do not appear to be any fully-compliant implementations of the 1.1 specification at this time. Is that correct?

On Oct 21, 2009, at 1:59 PM, John Boyer wrote:

Advancement to W3C Proposed Recommendation(PR), which is the step before the one announced here that occurred in August, is supported by an implementation report containing results from numerous implementations. The implementation report link appears in the PR status section. A number of these implementations are open source projects.

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

From: Kai-Uwe Behrmann <ku.b@...>
To: John Boyer/CanWest/IBM@IBMCA
Cc: public-forms@..., www-forms@...
Date: 10/21/2009 12:31 PM
Subject: Re: XForms 1.1 is a W3C Recommendation

May I ask, where is the reference implementation to XFORMS 1.1? kind regards Kai-Uwe Behrmann -- developing for colour managementwww.behrmann.name+www.oyranos.orgAm 20.10.09, 14:41 -0700 schrieb John Boyer: > It's official, XForms 1.1 is a W3C Recommendation. > See thewww.w3.orgmain page now. > > Also, for W3C members, please see the announcement to the AC: >http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html> > Congratulations to the Forms WG and the Forms community. > > Best regards, > John M. Boyer, Ph.D. > STSM, Interactive Documents and Web 2.0 Applications > Chair, W3C Forms Working Group > Workplace, Portal and Collaboration Software > IBM Victoria Software Lab > E-Mail: boyerj@... > > Blog:http://www.ibm.com/developerworks/blogs/page/JohnBoyer> Blog RSS feed: >http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw> >

Re: XForms 1.1 is a W3C Recommendation

2009-10-21T12:59:06Z

Advancement to W3C Proposed Recommendation(PR), which is the step before the one announced here that occurred in August, is supported by an implementation report containing results from numerous implementations. The implementation report link appears in the PR status section. A number of these implementations are open source projects.

Cheers,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

From:	Kai-Uwe Behrmann <ku.b@...>
To:	John Boyer/CanWest/IBM@IBMCA
Cc:	public-forms@..., www-forms@...
Date:	10/21/2009 12:31 PM
Subject:	Re: XForms 1.1 is a W3C Recommendation

May I ask, where is the reference implementation to XFORMS 1.1? kind regards Kai-Uwe Behrmann -- developing for colour managementwww.behrmann.name+www.oyranos.orgAm 20.10.09, 14:41 -0700 schrieb John Boyer: > It's official, XForms 1.1 is a W3C Recommendation. > See thewww.w3.orgmain page now. > > Also, for W3C members, please see the announcement to the AC: >http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html> > Congratulations to the Forms WG and the Forms community. > > Best regards, > John M. Boyer, Ph.D. > STSM, Interactive Documents and Web 2.0 Applications > Chair, W3C Forms Working Group > Workplace, Portal and Collaboration Software > IBM Victoria Software Lab > E-Mail: boyerj@... > > Blog:http://www.ibm.com/developerworks/blogs/page/JohnBoyer> Blog RSS feed: >http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw> >

Re: XForms 1.1 is a W3C Recommendation

2009-10-21T12:30:44Z

May I ask,
where is the reference implementation to XFORMS 1.1?

kind regards
Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org

Am 20.10.09, 14:41 -0700 schrieb John Boyer:

> It's official, XForms 1.1 is a W3C Recommendation.
> See the www.w3.org main page now.
>
> Also, for W3C members, please see the announcement to the AC:
> http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html
>
> Congratulations to the Forms WG and the Forms community.
>
> Best regards,
> John M. Boyer, Ph.D.
> STSM, Interactive Documents and Web 2.0 Applications
> Chair, W3C Forms Working Group
> Workplace, Portal and Collaboration Software
> IBM Victoria Software Lab
> E-Mail: boyerj@...
>
> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
> Blog RSS feed:
> http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
>
>

RE: XForms 1.1 is a W3C Recommendation

2009-10-21T01:04:46Z

> It's official, XForms 1.1 is a W3C Recommendation.

Excellent news!

Best regards and well done to everyone involved

Philip Fennell
Consultant

Mark Logic
www.marklogic.com

E-mail: philip.fennell@...
Mobile: +44 (0)7824 830 866

From: www-forms-request@... [mailto:www-forms-request@...] On Behalf Of John Boyer
Sent: 20 October 2009 22:41
To: public-forms@...; www-forms@...
Subject: XForms 1.1 is a W3C Recommendation
Importance: High

It's official, XForms 1.1 is a W3C Recommendation.
See the www.w3.org main page now.

Also, for W3C members, please see the announcement to the AC:
http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html

Congratulations to the Forms WG and the Forms community.

Best regards,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

Re: XForms 1.1 is a W3C Recommendation

2009-10-20T17:18:02Z

T.V Raman schrieb:
> Congratulations Gang!

Yep! Thanks for doing a great job.

All the best,

- Sebastian

XForms 1.1 is a W3C Recommendation

2009-10-20T15:54:24Z

Congratulations Gang!

John Boyer writes:

XForms 1.1 is a W3C Recommendation

2009-10-20T14:41:09Z

It's official, XForms 1.1 is a W3C Recommendation.
See the www.w3.org main page now.

Also, for W3C members, please see the announcement to the AC:
http://lists.w3.org/Archives/Member/w3c-ac-members/2009OctDec/0025.html

Congratulations to the Forms WG and the Forms community.

Best regards,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

Re: Semicolon better than ampersand as the default separator

2009-10-20T10:59:47Z

Mark, John, WG,

My concern was also that having & as the default encourages people to have lots of URIs containing & and they can also type those URIs somewhere in markup in addition to having them constructed at submission. But this default enabling authors to have no & at all in the document coupled with & support on the server indeed may be a better remedy. Thanks for your explanation, I find it more compelling than that provided in the PR.

Best regards,

Krzysztof Maczyński
Invited Expert, HTML WG

Re: Semicolon better than ampersand as the default separator

2009-10-20T09:47:59Z

I agree with Mark, but he was quicker on the draw :-)

During the implementation phase, it was discovered that implementers by-and-large went with the current web default of ampersand when *constructing* URI parameters from instance data. We had to be responsive to that reality in order to exit CR.

However, to Mark's point, because the change concerns what separator is used to *construct* the URI parametners, the only occurrence of the separator character is in the separator attribute. So, changing the default to ampersand means you don't have to write an escaped ampersand into the XML markup of the submission in order to get ampersand separators. You can express it if you want, but you used to be forced to write an escaped ampersand separator on pretty much every submission, which is why the implementation community generally did not go this way.

John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@...

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

From:	Mark Birbeck <mark.birbeck@...>
To:	Krzysztof Maczyński <1981km@...>
Cc:	www-forms@..., www-forms-editor@...
Date:	10/20/2009 07:21 AM
Subject:	Re: Semicolon better than ampersand as the default separator

Hi Krzysztof, You are right that the ampersand needs escaping, but that is exactly why it's a better choice as the default. With the change to XForms 1.1, authors only need to provide a value for @separator if the server they are addressing uses semi-colons. Regards, Mark -- Mark Birbeck, webBackplane mark.birbeck@...http://webBackplane.com/mark-birbeckwebBackplane is a trading name of Backplane Ltd. (company number 05972288, registered office: 2nd Floor, 69/85 Tabernacle Street, London, EC2A 4RR) 2009/10/19 Krzysztof Maczyński <1981km@...>: > Dear WG, > > Pardon the cross-posting, but I'm not sure to which list this should go. > > In XForms 1.1 PR the default of the separator attribute was changed to ampersand. Semicolon is a viable and fairly common alternative whose main advantage over ampersand is that it doesn't need escaping in XML and SGML. See also [1] and [2]. Worse even, authors often fail to escape it, which results in errors. I'd like to ask you to reconsider this change and I'd rather see it reverted. > > Best regards, > > Krzysztof Maczyński > Invited Expert, HTML WG > > [1]http://www.w3.org/DesignIssues/MatrixURIs> [2]http://xmltoday.org/content/dancing-naked-streets-madman-takes-html-5#comment-2240> (Not what you might expect having read that URI.) > >

Request for being added to the XForms Implementations List

2009-10-20T07:15:59Z

Dear working group,

Our research group at the Karlsruhe Institute of Technology (KIT) in Germany has developed a visual Web-based XForms editor which is available for free at:

http://research.tm.uka.de/DialogDSLDemosite

We are kindly requesting to be added to the W3C XForms Group Wiki’s Implementations Page (http://www.w3.org/MarkUp/Forms/wiki/XForms_Implementations).

The editor promotes a two-layered modeling approach which strongly focuses on dynamic behavior and usability aspects of advanced Web-based dialogs:

1.) On the first layer, a dialog’s data model can be visually grouped into semantically cohesive groups and dynamic transitions between these groups can be defined (“Previous / Next” or selection-dependent transitions).

2.) On the second layer, each partition’s appearance can be designed in detail, thereby particularly emphasizing usability-enhancing attributes like help, hint, validations etc.

All modeling can be done visually in the browser. The implementation is AJAX-based which fosters an efficient and satisfying modeling experience. Besides that, also direct manipulations on the XForms markup code can be performed.

The editor is part of our “Dialog DSL” research which was presented at the WWW2008 and the ICWE2008:

http://www2008.org/papers/pdf/p1069-freudensteinA.pdf

http://icwe2008.webengineering.org/Program/Proceedings/ISBN978-0-7695-3261-5/3261a038.pdf

We have also begun to conduct empirical evaluations of the editor’s adequacy for stakeholders with a non-IT-related background. The current results indicate significant efficiency gains as well as a good effectiveness / usability, also for non-programmers. More information about the evaluation can be found in my PhD thesis “Web Engineering for Workflow-based Applications: Models, Systems and Methodologies” which is available at:

http://digbib.ubka.uni-karlsruhe.de/volltexte/1000012659

We would greatly appreciate being listed on the “XForms Implementations” page mentioned above. If you should have questions or feedback, please do not hesitate to contact me.

Thank you very much for your attention!

Best regards,

Patrick Freudenstein

Karlsruhe Institute of Technology (KIT)

Steinbuch Centre for Computing (SCC)

Dr.-Ing. Patrick Freudenstein

Integration and Virtualization

Engesserstr. 4 / Building 20.51

D-76128 Karlsruhe
Germany
Find me!


Phone:	+49 (0)721/608 8072
Email:	patrick.freudenstein@...
Web:	http://mwrg.tm.uni-karlsruhe.de

KIT - University of the federal state of Baden-Wuerttemberg and national large-scale research center of the Helmholtz Association

smime.p7s (7K) Download Attachment

Re: Semicolon better than ampersand as the default separator

2009-10-20T07:10:14Z

Hi Krzysztof,

You are right that the ampersand needs escaping, but that is exactly
why it's a better choice as the default. With the change to XForms
1.1, authors only need to provide a value for @separator if the server
they are addressing uses semi-colons.

Regards,

Mark

--
Mark Birbeck, webBackplane

mark.birbeck@...

http://webBackplane.com/mark-birbeck

webBackplane is a trading name of Backplane Ltd. (company number
05972288, registered office: 2nd Floor, 69/85 Tabernacle Street,
London, EC2A 4RR)

2009/10/19 Krzysztof Maczyński <1981km@...>:

> Dear WG,
>
> Pardon the cross-posting, but I'm not sure to which list this should go.
>
> In XForms 1.1 PR the default of the separator attribute was changed to ampersand. Semicolon is a viable and fairly common alternative whose main advantage over ampersand is that it doesn't need escaping in XML and SGML. See also [1] and [2]. Worse even, authors often fail to escape it, which results in errors. I'd like to ask you to reconsider this change and I'd rather see it reverted.
>
> Best regards,
>
> Krzysztof Maczyński
> Invited Expert, HTML WG
>
> [1] http://www.w3.org/DesignIssues/MatrixURIs
> [2] http://xmltoday.org/content/dancing-naked-streets-madman-takes-html-5#comment-2240
> (Not what you might expect having read that URI.)
>
>

Semicolon better than ampersand as the default separator

2009-10-19T14:05:30Z

Dear WG,

Pardon the cross-posting, but I'm not sure to which list this should go.

In XForms 1.1 PR the default of the separator attribute was changed to ampersand. Semicolon is a viable and fairly common alternative whose main advantage over ampersand is that it doesn't need escaping in XML and SGML. See also [1] and [2]. Worse even, authors often fail to escape it, which results in errors. I'd like to ask you to reconsider this change and I'd rather see it reverted.

Best regards,

Krzysztof Maczyński
Invited Expert, HTML WG

[1] http://www.w3.org/DesignIssues/MatrixURIs
[2] http://xmltoday.org/content/dancing-naked-streets-madman-takes-html-5#comment-2240
(Not what you might expect having read that URI.)