[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML for forms

• From: "Barclay Blair" <barclay@u...>
• To: "Michael Rossi" <mrossi@c...>, <xml-dev@i...>
• Date: Wed, 14 Jul 1999 11:02:42 -0700

Thanks for pointing out this concern, and I sincerely apologize to the group
for the inappropriate postings. I will keep further postings within the
boundaries of tone and content that are more suitable.

Mike, as to your question, I believe the answer is yes for both XFA and
XFDL.

Any parser that uses SAX/DOM can read, change, and write XFDL forms, but the
?additional? features that XFDL offers, such as digital signatures,
formatting, computations, etc, will not be active using those standard
parsers.

Barclay

 ============================================
    Barclay Blair -- Industry Relations
    UWI.Com -- The InternetForms Company
  v: 250-479-8334 x161   fx: 250-479-3772
 barclay@u...	       www.uwi.com
============================================

-----Original Message-----
From: owner-xml-dev@i... [mailto:owner-xml-dev@i...]On Behalf Of
Michael Rossi
Sent: Wednesday, July 14, 1999 10:18 AM
To: xml-dev@i...
Subject: RE: XML for forms


Barclay Blair wrote:
>
> Rob and Gavin,
>
> Thanks for the responses -- very interesting! I always enjoy exchanging
> ideas  (or barbs, as the case may be, Gavin :)).  I have some concerns
that
> we're in danger of boring the rest of the group with the semantics of form
> presentation etc., so I'd be happy to continue the discussion individually
> with each of you, instead of on the list. That is, unless the group or
> yourselves feel strongly about continuing the dialogue on the list.

   This discussion, while quite interesting, is clearly inappropriate for
this list - as Tim noted. But I do have a (hopefully) more relevant
question. As someone who has only begun to look into both
technologies/products, I have yet to determine whether each
technology/product will allow me to interact with their forms using standard
DOM/SAX methods.

   From what I've seen so far I'm concerned that this need to capture
presentation aspects of a form might be leading to proprietary development
within the underlying specs. I'm envisioning working with XML-based forms in
the context of a larger XML-enabled process and I'd hate to get tied into a
single product to support that requirement.

   Again, I haven't had a chance to go far enough yet. But feel free to
enlighten me please. Thanks.

Mike

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN
981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following
message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • RE: XML for forms
    • From: Michael Rossi <mrossi@c...>

• Prev by Date: RE: XML for forms
• Next by Date: general external entity reference from a DTD to another one?
• Previous by thread: RE: XML for forms
• Next by thread: RE: XML for forms
• Index(es):
  • Date
  • Thread