SV: [ubl-psc] Adding new document types in UBL 2.1

["Peter L. Borresen" <plb@ebconnect.dk>]

Hi Jon and Fulya

I think we need a meeting to discuss this. I would like to know the
difference between purchase conditions and contract. I also have knowledge
of at least one more document: CatalogueTemplate. Requirements are to be
provided by PEPPOL.

/Peter



-----Oprindelig meddelelse-----
Fra: Jon Bosak [mailto:bosak@pinax.com] 
Sendt: 16. februar 2010 18:11
Til: UBL PSC
Cc: fulya@srdc.metu.edu.tr
Emne: [ubl-psc] Adding new document types in UBL 2.1

Hello PSC,

Regarding the proposed new document type "Purchase Conditions,"
please note the procedure below from today's TC call minutes.

Jon

==================================================================

ADDING NEW DOCUMENT TYPES

    We have a request to add one new CPFR document type, Purchase
    Conditions (not two as recorded in the minutes of the Pacific
    TC call).

    JB: Let's review the way we approve new UBL content.  The
     method we've used since before UBL 0.7 is as follows:

     - Content is developed by business experts in a relevant UBL
       content subcommittee.  In UBL 0.7 and 1.0, this was a single
       subcommittee called "the Content Subcommittee."  Since then,
       this work has taken place in two subcommittees, the UBL
       Procurement Subcommittee (PSC) and the UBL Transportation
       Subcommittee (TSC).  These subcommittees are trusted to make
       virtually all decisions about the UBL data models.

     - The rules for creating an XML syntax binding for the data
       models are created by a separate team.  In UBL 0.7 and 1.0,
       this was a subcommittee called the NDR Subcommittee; in UBL
       2.0 and later, this work has been entrusted to the two NDR
       editors, who work closely with the TC and (in 2.1) the
       Schema Generation Subcommittee.

     - The UBL TC itself is formally responsible for everything
       that goes into each UBL release.  In practice, this
       authority is generally exercised by approving or
       disapproving the entire release when it comes time to
       approve a draft.  In every release so far, there have been
       actual issues to resolve at the TC level, but for practical
       reasons we try whenever possible to resolve these in the
       subcommittees and only look at issues for which resolution
       at the subcommittee level has proven impossible.

     - For UBL 2.1, we've put two other groups into the process.
       One of these groups is a Modeling Integration Team that was
       created on 27 October 2009 and consists of TM, AS, and PB:

       http://lists.oasis-open.org/archives/ubl/200910/msg00029.html

       The other group is the Schema Generation Task Group, which
       was created a year ago (2009.02.23-03.02) and consists of
       GKH, Oriol, and TonyC:

       http://lists.oasis-open.org/archives/ubl/200902/msg00019.html

    The way content gets into the release now is as follows:

       1. The PSC or TSC approves content

       2. The Modeling Integration Team verifies that the content
          is properly integrated into the data models

       3. The data models go to the SGTG

       4. The SGTG generates the schemas using the schema
          generation tool (which happens this time around to be
          eDoCreator).

    (Cf. http://lists.oasis-open.org/archives/ubl/201001/msg00003.html)

    So the way that this additional document type is going to get
    added to the set is as follows:

       1. The PSC approves the new Purchase Conditions document
          type (or not)

       2. The MIT verifies that Purchase Conditions is properly
          integrated into the data models

       3. The revised data models go to the SGTG

       4. The SGTG generates the revised schema set.

    The next step, therefore, is for Fulya to send a message to the
    PSC mail list asking for the addition of Purchase Conditions to
    UBL 2.1.  Then the PSC considers this (in person or by email),
    and so on.

    ACTION: JB to call these minutes to the attention of the PSC.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php