ontolog-forum
[Top] [All Lists]

Re: [ontolog] Providing Review to the UBL Jan-2003 Release

To: <ontolog@xxxxxxxxxxxxxxx>
From: "Peter P. Yim" <yimpp@xxxxxxxxxxx>
Date: Mon, 27 Jan 2003 12:24:21 -0800
Message-id: <034a01c2c642$1364ceb0$2e0c5c42@helios>
It's officially out now!    (01)

Here's the announcement made about it this morning:    (02)

//    (03)

----- Original Message -----
From: "Jon Bosak" <Jon.Bosak@xxxxxxx>
To: <ubl@xxxxxxxxxxxxxxxxxxxx>; <ubl-comment@xxxxxxxxxxxxxxxxxxxx>
Sent: Monday, January 27, 2003 11:29 AM
Subject: [ubl] UBL Schemas released for public review    (04)

UBL SCHEMAS RELEASED FOR PUBLIC REVIEW    (05)

The first draft of a royalty-free data representation standard for
electronic commerce has been released by the OASIS Universal
Business Language (UBL) Technical Committee.    (06)

The UBL Library Content 0p70 Public Review release can be found at    (07)

   http://oasis-open.org/committees/ubl/lcsc/0p70/    (08)

A zip file containing the entire review set packaged for local
installation can be downloaded from    (09)

   http://oasis-open.org/committees/ubl/lcsc/0p70/UBL0p70.zip    (010)

Intended to become international standards for electronic trade,
the UBL schemas contained in the review package specify
machine-readable XML representations of familiar business
documents.  The seven basic documents covered in this release
include Order, Order Response, Simple Order Response, Order
Cancellation, Despatch Advice, Receipt Advice, and Invoice.
Together, they can be used to implement a generic buy/sell
relationship or supply chain whose components fit existing trade
agreements and are immediately understandable by workers in
business, supply-chain management (SCM), Electronic Data
Interchange (EDI), accounting, customs, taxation, and shipping.    (011)

These generic schemas are intended to work in a wide variety of
business contexts through custom extensions.  Automated context
configuration will be addressed in a later phase of the effort.
The schemas are also designed be used in their generic form in
many ordinary business contexts without further modification.    (012)

The business context in which the generic document types are
designed to function is detailed in the materials accompanying the
release.  Other documentation includes the entire semantic model
on which the schemas are based, a description of the methodology
by which the schemas were created, and UML diagrams to aid in
software design.  The package also contains alternative ASN.1
specifications for the UBL schemas that allow ASN.1 tools to be
used for UBL document transfers.  Additional supplementary
materials will be made available in a following package update to
be announced separately.    (013)

The UBL schemas reflect a number of inputs, the most important of
which are the commercial xCBL schemas from Commerce One and SAP;
the ebXML Core Components Specification; early XSL stylesheet
implementations; and early feedback from the UBL Liaisons
(http://oasis-open.org/committees/ubl/lsc/).  UBL schema design
follows the UBL Naming and Design Rules developed by the UBL NDR
Subcommittee (http://oasis-open.org/committees/ubl/ndrsc/).  The
definition of UBL semantic content, based on existing practice in
EDI and electronic marketplaces, has taken place in close
alignment with ebXML Core Components methodology to ensure optimal
integration into the ebXML semantic registry.    (014)

As works in progress, the materials in the Library Content 0p70
Public Review package do not yet have the status of an OASIS
Standard or an OASIS Committee Specification.  The construction of
experimental prototypes based on these materials is encouraged for
the purpose of generating input back to the committee process, but
implementers are strongly advised against basing commercial or
mission-critical applications on the draft specifications.    (015)

The OASIS UBL Library Content Subcommittee invites interested
parties to comment on this release directly to the Library Content
Subcommittee Editor, Bill Meadows (bill.meadows@xxxxxxx), using the
recommended feedback form at    (016)

   http://www.oasis-open.org/committees/ubl/lcsc/0p70/UBL_Comment-0p1.rtf    (017)

This release comment period applies from Monday, January 27th until
Monday, April 14th 2003. We welcome all comments and will ensure to
advise of our dispositions to any suggestions.    (018)

The work of the OASIS UBL Technical Committee is open to public
view through the mail archives linked from the UBL home page:    (019)

   http://oasis-open.org/committees/ubl/    (020)

Formal input to UBL from industry data exchange organizations is
provided through the UBL Liaison Subcommittee:    (021)

   http://oasis-open.org/committees/ubl/lsc/    (022)

Input from the general public is accepted through the ubl-comment
mail list:    (023)

   http://lists.oasis-open.org/archives/ubl-comment/    (024)

Interested parties are invited to comment on the work of the UBL
TC by subscribing to the ubl-comment list using the OASIS list
manager:    (025)

   http://lists.oasis-open.org/ob/adm.pl    (026)

//    (027)

original posting on the ubl mailing list archives can be found at:
  http://lists.oasis-open.org/archives/ubl/200301/msg00004.html    (028)

Please help review the UBL released material. [attn: ALL]    (029)

Let's talk about them, along the line proposed in the last message, if
anyone has other ideas and suggestions, please bring them up too.    (030)

Thanks & regards,
PPY
--    (031)

----- Original Message -----
From: "Peter P. Yim" <yimpp@xxxxxxxxxxx>
To: <ontolog@xxxxxxxxxxxxxxx>
Sent: Wednesday, January 15, 2003 3:46 PM
Subject: [ontolog] Providing Review to the UBL Jan-2003 Release    (032)


> Happy New Year!
>
> 1. I would like to let everyone know that the UBL - Universal Business
> Language - Technical Committee is imminently making the next release
> of their interim work product for review by the industry.
>
> 2. One of the charters of this forum is to "identify ontological
> engineering approaches that might be applied to the UBL effort."
> (see http://ontolog.cim3.org/forums/ontolog/0209/msg00000.html#nid03)
>
> 3. We intend to collectively contribute to that review effort, and the
> purpose of this message is draw everyone's attention to this upcoming
> activity.
>
> 4. What we can possibly do, after we are provided access to the UBL
> work products, would be:
>
>    (a) to review the work and provide general (on non-ontological
> issues) feedback, individually, to UBL directly;
>
>    (b) to bring up ontology or ontological engineering issues for
> discussion within this forum, and then provide a compilation of our
> findings and recommendations (possibly in the form of a position
> paper) to UBL collectively;
>
>    (c) Consider making an attempt to "ontologize" the UBL work product
>   -- but, obviously, we need to discuss the what? and how? of this
> effort in more depth.
>
>    (d) plus, anything else members of this community would propose and
> agree to take on.
>
> 5. For those members who are not very familiar with the OASIS-UBL TC
> and their work, please take a moment to browse their website at:
>
>    http://oasis-open.org/committees/ubl/
>
> In particular, the two recent presentations made by UBL TC members (at
> the XML Conference in Baltimore, MD, USA in Dec. 2002), as highlighted
> at the UBL site, would provide a succinct picture of what UBL is all
> about. See:
>
> //
> UBL TC Vice Chair Mark Crawford gave the UBL keynote:
> http://oasis-open.org/committees/ubl/200212/0212ubl.ppt
>
> Schema designers will find Eve Maler's talk on Schema Rules for UBL of
> particular interest:
> http://oasis-open.org/committees/ubl/info/ubl2002e.pdf
> //
>
> 6. I'll get back to you all, shortly, once I have specific information
> to the new UBL release.
>
> Regards,
> PPY
>
>
> --
> To post messages mailto:ontolog@xxxxxxxxxxxxxxx
> An archive of the [ontolog] forum can be found
> at http://ontolog.cim3.org/forums/ontolog
>    (033)

--
To post messages mailto:ontolog@xxxxxxxxxxxxxxx
An archive of the [ontolog] forum can be found
at http://ontolog.cim3.org/forums/ontolog    (034)
<Prev in Thread] Current Thread [Next in Thread>