XML for forms

[Trevor Croll]

Thanks Gavin - I agree KISS keep it short and simple is the way to go:

For a forms input and printing function I looked at the possibilities of:

Data:                                    XML format for data specified by a
DTD:
Screen:                                XSL format for screen
Adding data to a Screen:        Xlink
Taking data from the screen    XPointer
(Some Xpointer or Xlink specification for identifying the data on a form and
putting data into a screen)

Would this then be using the existing basic XML specs rather than building
new ones

Perhaps your XFA is really just another way of including all the XSL,
Xpointer. Xlink, XML etc and packaging it into a specification that is a
selected set of the these?

I really must study your XFA in much more detail but it does seem to have
the functionality I am looking for.
I could possibly use your Jetform forms designer as part of my overall
package approach. My market target was going to be the smaller business and
the big business to small customer, Plumbing supplier to client plumber as
an example.

I was going to try to produce a package that allowed business to communicate
with each other through emailed encripted forms. - not really an accounting
package more a filing system.

regards Trevor Croll



Your views would be most welcome


----- Original Message -----
From: Gavin McKenzie <gmckenzi at JetForm.com>
To: 'Trevor Croll' <litebook at powerup.com.au>
Cc: <xml-dev at ic.ac.uk>
Sent: Monday, July 05, 1999 11:32 PM
Subject: RE: XML for forms


>
> Trevor,
>
> [And I extend this invitation to the general public]
>
> As the editor of the XFA specifications I would be happy to try and
address
> some of your more detailed questions.  My ability to keep up on XML-Dev is
> very inconsistent (as is clear from the fact that it has taken me this
long
> to pick up on this thread).  Direct email is always easier for me.
>
> We (JetForm) wish to not require form data to be anything more than well
> formed XML.  There is a whole range of initiatives springing up around
> schemas and data definition -- not something I want to get in the way of.
I
> expect that this bubble of extreme growth will pop in the not too distant
> future and collapse into a few de facto technologies and techniques.  IMHO
> the Keep It Simple approach to data (i.e. well formed XML) is the safest
> 'today' approach.
>
> Gavin.
>
> ========================================================
> Gavin F. McKenzie          mailto:gmckenzi at jetform.com
> Systems Architect          Vox:+1(613)230-3676
> JetForm Corporation         or:+1(613)751-4800 ext 5277
> http://www.jetform.com     Fax:+1(613)751-4864
> ========================================================
>
>
>
> xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
> 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 at ic.ac.uk the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:majordomo at ic.ac.uk the following
message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
>
>


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
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 at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)