RE: [regrep] [Fwd: [xml-dev] Extract A Subset of a W3C XML Schema?]

["Peter Kacandes" <pkacande@adobe.com>]

For a whole variety of reasons, XForms is pretty much wholly inadequate,
which is pretty much why none of the significant eForms vendors are
supporting it.

However, there will be data interoperability for the form data schemas.

cheers

pk

-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Wednesday, August 06, 2003 10:09 AM
To: Peter Kacandes
Cc: regrep@lists.oasis-open.org
Subject: Re: [regrep] [Fwd: [xml-dev] Extract A Subset of a W3C XML
Schema?]


<Quote1>
For a designer looking to automate a form they are confronted with the
need to find appropriate XML to which to bind the form fields.
</Quote1>

XForms 1.0 - when it becomes a W3C Recommendation - will be ideal for
this.

<Quote2>
For a large organization with many forms it is likely that there will be
many elements that are common to some forms.
</Quote2>

Yes - and when we've completed our Technical Note on the registration of
elements/attributes/datatypes/namespace identifiers, it will be a
wonderful step toward this goal.

Joe

Peter Kacandes wrote:
>
> An XML fragment could be anything from a single element name up to a
> complete schema for a particular form.
>
> For a designer looking to automate a form they are confronted with the
need
> to find appropriate XML to which to bind the form fields.
>
> For a large organization with many forms it is likely that there will be
> many elements that are common to some forms.
>
> If the form designer could use existing fragments for the common elements
of
> a particular form they are working on, then they would only have to
develop
> new fragments for the pieces of their form that are unique.
>
> hth
>
> cheers
>
> pk
>
> -----Original Message-----
> From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> Sent: Thursday, July 31, 2003 1:08 PM
> To: Peter Kacandes
> Cc: regrep@lists.oasis-open.org
> Subject: Re: [regrep] [Fwd: [xml-dev] Extract A Subset of a W3C XML
> Schema?]
>
> <Quote>
> When designing a PDF/XML form, the designer would search the registry
> for various fragments
> </Quote>
>
> Please define a "fragment" in terms of both XML and an electronic form.
>
> Joe
>
> Peter Kacandes wrote:
> >
> > This type of thing was a core aspect of the demo that we did for the
gov't
> > folks.
> >
> > When designing a PDF/XML form, the designer would search the registry
for
> > various fragments that might be applicable to the particular form they
are
> > designing.
> >
> > These fragments would then be downloaded to the local machine where the
> > designer would import them into the tool where they would then be bound
to
> > particular form fields.
> >
> > Of course, it would be way cooler if the registry could be searched
> directly
> > from the tool, but I'm working on that.
> >
> > For a concrete example, let's say the gov't designed a fragments for and
> > organization name and DUNS numbers with an associated web service that
> would
> > go out and get the DUNS number for a name when it was typed into the
name
> > field.
> >
> > There are many gov't forms across different agencies that might use the
> DUNS
> > fragment and web service. A designer who has been tasked with automating
a
> > particular form could go through and search the registry for any
fragments
> > that match fields on the particular form they are automating.
> >
> > hth
> >
> > cheers
> >
> > pk
> >
> > -----Original Message-----
> > From: Duane Nickull [mailto:duane@yellowdragonsoft.com]
> > Sent: Thursday, July 31, 2003 10:17 AM
> > To: Matthew MacKenzie
> > Cc: Farrukh Najmi; Chiusano Joseph; regrep@lists.oasis-open.org
> > Subject: Re: [regrep] [Fwd: [xml-dev] Extract A Subset of a W3C XML
> > Schema?]
> >
> > Matthew MacKenzie wrote:
> >
> > > I think registry already has the capability to do this sort of thing.
> > > Must we place every use case in the specification?  Maybe a best
> > > practice doc is needed.
> >
> > This use case has been noted in the eGovernments TC's Government
> > Registry Requirements document, although it has not been sussed out in
> > great detail.  I can send copies of it (early draft) to anyone who
wants.
> >
> > Duane
> >
> > --
> > ***************************************************
> > Yellow Dragon Software - http://www.yellowdragonsoft.com
> > Web Services & ebXML Messaging / Registry Downloads
> > Project Team Lead - UN/CEFACT eBusiness Architecture
> > Phone:   +1 (604) 738-1051 - Canada: Pacific Standard Time
> > Direct:  +1 (604) 726-3329
> >
> > You may leave a Technical Committee at any time by visiting
> >
>
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> > php
> >
> > You may leave a Technical Committee at any time by visiting
>
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
> php
>
> You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
php