- From: Tyler St. John <trs17@pitt.edu>
- Date: Wed, 30 May 2007 23:01:28 -0400
- To: "Dustin Whitney" <dustin.whitney@gmail.com>
- Cc: "Nikunj Mehta" <nikunj.mehta@oracle.com>, www-forms@w3.org, "Elliotte Harold" <elharo@metalab.unc.edu>
- Message-ID: <3e20ab510705302001l597e251ay8bb2feea936a4c5d@mail.gmail.com>
What kind of applications is everyone developing with APP?? I'm just working on a really simple reader/editor. However, I've ran into several problems. I've basically reached a wall in my application because of the poor ability to handle xhtml content. This poor ability may be due to my lack of experience in XForms and APP. I can only read in escaped xhtml and not any xhtml wrapped in CDATA. Any ideas on what I can do? On 5/30/07, Dustin Whitney <dustin.whitney@gmail.com> wrote: > > I've experience similar problems, not in implementing APP, but in wishing > that xs:complexContent were supported. > > -Dustin > > On 5/30/07, Nikunj Mehta <nikunj.mehta@oracle.com> wrote: > > > > > > Elliotte Harold wrote: > > > > > > Has anyone yet written or started work on an XForms client for APP? I > > > googled but didn't find anything. If the space is open I may take a > > > crack at it myself. > > > > > > I think XForms 1.1 would be required since XForms 1.0 does not support > > > PUT and DELETE. > > > > > Apart from the challenges introduced by the event + form model (which by > > the way simplify many things in the end), a limitation I find with > > XForms in its proposed incarnation (1.1) is that the XForms model is > > quite closed ended when it comes to content. It chooses xs:simpleContent > > as the basis for producing and displaying form instances. > > > > A major consequence is that rendering atom:link as xhtml:link is not > > going to be supported in the proposed revision. Another consequence is > > that the various content models in atom such as atom:title, > > atom:summary, atom:content, etc. cannot be rendered meaningfully if > > their contents are anything other than text. > > > > I was very hopeful today when I started investigating creating a simple > > browser + XForms based APP client, but quickly realized that without > > support for xs:complexContent, I would end up working around the > > standard that I might as well wait for the issues to be resolved in the > > Forms WG. > > > > Anyone have more positive experience with XForms for APP? I'd surely > > love to know. > > > > ....Nikunj > > > > > > > -- Tyler St. John
Received on Thursday, 31 May 2007 23:41:46 UTC