ubl-ndrsc — archive

[ubl-ndrsc] Minutes for 17 July 2002 UBL NDR SC meeting

From: Eve Maler
To: [email protected]
Date: Wed, 17 Jul 2002 12:58:00 -0000

MHonArc v2.5.2 -->

ubl-ndrsc message

Subject: [ubl-ndrsc] Minutes for 17 July 2002 UBL NDR SC meeting

From: "Eve L. Maler" <[email protected]>
To: ubl-ndrsc <[email protected]>
Date: Wed, 17 Jul 2002 12:58:27 -0400

Minutes for 17 July 2002 UBL NDR SC meeting

NDR SC agenda:
1. Roll call (quorum is 8)
     * Bill Burcham       YES
     * Mavis Cournane     YES
     * Mark Crawford      YES (joined y:02)
     * Fabrice Desr�      awol
     * Matt Gertner       regrets
     * Arofan Gregory     YES
     * Jessica Glace      regrets
     * Michael Grimley    regrets
     * Eduardo Gutentag   regrets
     * Eve Maler          YES
     * Sue Probert        YES (joined y:02)
     * Lisa Seaburg       YES
     * Gunther Stuhec     YES
     * Paul Thorpe        awol

    Quorum not achieved by x:34; we proceeded informally.  We reached
    quorum by y:02.

2. Acceptance of minutes of previous meetings

    26 June 2002
    http://lists.oasis-open.org/archives/ubl-ndrsc/200206/msg00029.html

    3 July 2002
    http://lists.oasis-open.org/archives/ubl-ndrsc/200207/msg00004.html

    Accepted.

3. Adoption of agenda/schedule planning

    Agenda adopted with deletion of the embedded documentation item.

    July 17:
    - Planned topics: Embedded Documentation, Nested
      Supplementary Components, Dates/Times
    July 24:
    - Mark, Jessica, Michael send regrets
    - Topics: ?
    July 31:
     - Mark sends regrets
    - Topics: Review NDR document, ?
    ...
    September 18:
    - Topics: Approve documents for review distribution #3
    September 25:
    - No meeting; work on other UBL tasks instead
    October 1-4:
    - F2F #5 in Burlington, MA, USA

       A NDR document improvements (review every two weeks)
       A+ Embedded documentation DONE EXCEPT FOR DOCUMENTING IT
       A Code lists IN PROGRESS
       A Dates and times IN PROGRESS
       A Nested supplementary components
       A Identifier references and whether to pass content by reference
       A- Local vs. global elements
       B+ Containership
       B Updating guiding principles
       B Modnamver URN/schema location
       B Referencing of content, e.g. for attachments
       C Facets
       C Wildcards/open content
       C Nillability
       C Aggregation of similar information for XPath V1.0 addressing

4. Action item review

    Mavis:
    - Review Gunther's script for new issues. IN PROGRESS
    - With Gunther, add *Type/*ContentType info to the NDR document.
      IN PROGRESS
    - Update the issues spreadsheet with Eve's comments.

    Eve:
    - Finish draft of code list document. IN PROGRESS
    - Approach Tim and Jon on SWAT team idea. DONE

    Gunther:
    - Write content referencing paper. IN PROGRESS
    - Review the date/time comments and recommend dispositions.

    Bill:
    - Update modnamver; discuss with Eve and Lisa. IN PROGRESS
    - Revise role model paper. CANCELED

    Arofan:
    - Get NDR document section written on embedded documentation.
      IN PROGRESS
    - Create a worked example of how to define nested supplementary
      components.

5. Brief reports from elsewhere

    LC (Lisa): A class diagram of Order will be sent out for review.
    A 0pt65 version of the spreadsheet is being sent around the group
    for internal review; it has Order Response in it.  They are planning
    a distribution in mid- to late August.  It's been reported that the
    CCSD work is progressing pretty quickly, but we don't have good
    access to those documents.  Sally and Gunther are well aware of
    those activities.

    ebXML Joint Coordination Committee (Bill): It meets by phone every
    two weeks.  Bill will report more as it goes.

    CM (Eve): Matt Gertner intends to get things going again in a few
    weeks.

    CD (Arofan): He and Sue are in the process of setting up this SC.

    X12C (Eve):  In discussions, Eve and Lisa Shreve agreed that each
    group needs to learn more about the work of the other.

    CC (Arofan): The meeting is going on right now.  There is a
    flattening of "nested" supplementary components going on that will
    ease our naming and CCT design concerns.  The code/identifier issue
    is, so far, being addressed with (a) a recommendation that the two be
    used in a mutually exclusive fashion and (b) some guidelines about
    how to pick one or the other.  A new notion of "squirts" (essentially
    syntax-neutral datatypes) has been added.

6. Embedded documentation
    Review position paper/chapter writeup if there is one ready

    Deferred.

7. Nested supplementary components

    - We agreed not to go back and reasess our element vs. attribute
      decision; that is, we're not currently interested in disallowing
      attributes entirely.

    - Thus, we will definitely have attributes that apply to other
      attributes.  The worst case is codes (other than Language.Code,
      since the code list for that will be fixed) that are
      supplementary to real BIEs.

    - We believe that the names for these second-order attributes can
      be constructed automatically by applying a qualifier consisting
      of the name of the first-order attribute to which they apply.

    - However, we think the definition of the relevant XSD types could
      be tricky, because those additional attributes need to be specific
      to particular attributes defined on particular complex types.

    - We need to work a full example with syntax and everything.

8. Date/Time
    We have decided on all the recommendations except for periodicity/
    recurrent.  We agreed to accept Gunther's Option 3; Gunther will
    send further examples of this going forward.

    When Gunther has had a chance to review Alan Stitzer's and Bob
    Miller's comments, we will dispose of those (possibly next week).

    We have a new topic to discuss: when to use groups.  Gunther sees
    some places where model groups would be useful in managing the
    Date/Time types, and there are other cases too.  In the case of
    the handcrafted CommonLeafTypes module, there seems no problem
    in choosing to use this technique as we see fit.  Right now we
    don't have any recommendations on when they should be applied
    deterministically to other modules.  Attribute groups might end
    up being handy too.

    We don't have any problem with the naming used in the sub-elements
    of the RecurrenceDetails element; the people involved in the CC work
    will propose the additional representation terms necessary.

9. Adjourn
    Adjourned at y:55.  Mavis will send out the agenda and help out with
    chairing and note-taking next week, as Eve will need to miss the
    first bit of the meeting.  Mark can't attend next week.

-- 
Eve Maler                                        +1 781 442 3190
Sun Microsystems                            cell +1 781 883 5917
XML Web Services / Industry Initiatives      eve.maler @ sun.com