Re: [ubl-dev] trying to resend PDF attachment, RE: [ubl-dev] feedback request on UBL with Adobe PDF example form

["David Webber \(XML\)" <david@drrw.info>]

Brad,

That is exactly what the current OASIS registry work on SCM has
already defined.

The XSD for that is here:
http://www.oasis-open.org/committees/download.php/9714/nounmetadata.xsd

and an example of USGov data dictionary items for eCGAP system
is here:
http://drrw.net/backup/NIH/nounexample-eCGAP.xml

Notice you can capture the BIE information, a form label, and then
localized description information - along with data content
semantics in a variety of syntax - such as XPath, xslt, CAM, etc.

Using the bulk loader package facilities in Registry it would be
feasible to export the XML out from the UBL spreadsheet and
then load that data dictionary in.

Enjoy, DW

----- Original Message ----- 
From: "Brad Sturtevant" <sturdyworks@yahoo.com>
To: <ubl-dev@lists.oasis-open.org>
Sent: Saturday, August 20, 2005 12:59 PM
Subject: Re: [ubl-dev] trying to resend PDF attachment, RE: [ubl-dev]
feedback request on UBL with Adobe PDF example form


> I am probably missing something obvious, but I did
> want to mention that there is a UBL Data Dictionary
> published April, 2005--I have attached this Excel
> spreadsheet as renamed zip file cd-UBL-1.0.zpi.
>
> It seems to have all of the standardized field names
> for all entity records such as Invoices/Line Items,
> etc. and a description in English, Spanish, Japanese,
> Chinese.
>
> In general, it would seem that the forms should be
> using these Data Dictionary field names, and a
> flexible design might allow official UBL data
> dictionary names to be mapped to the divergent field
> names on forms. The descriptions in UBL data
> dictionary are great for clearly identifying what a
> field name actually represents.
>
> Brad Sturtevant
> Principle Technologist
> Sturdyworks
>
>
> --- jon.bosak@sun.com wrote:
>
> > [pkacande@adobe.com:]
> >
> > | It seems like it might be very difficult to
> > generate one or just a
> > | few general purpose forms. For example, if the you
> > look at the
> > | sample in the UBL download for Joinery dispatch,
> > it has completely
> > | different headers and line item details. If there
> > are very many of
> > | these industry specific formats, then it might not
> > make sense to
> > | try and develop forms for each one.
> >
> > That's not a separate form, it's just another
> > example instance of
> > the same form (Despatch Advice).
> >
> > The question of how you map the many potential
> > elements in a UBL
> > schema to the much more limited number of cells in a
> > printed or
> > displayed form has received a great deal of
> > attention in UBL.  The
> > UBL 1.0 Standard contains a whole section describing
> > the mapping
> > of the relevant UBL data to the corresponding cells
> > of an
> > internationally standardized paper form, the UN
> > Layout Key.  In
> > UBL 2.0, as Micah Dubinko has pointed out, we're
> > attempting to do
> > the same thing for input forms.
> >
> > Jon
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > ubl-dev-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail:
> > ubl-dev-help@lists.oasis-open.org
> >
> >
>


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


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org