OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

rights-specification message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [rights-specification] 2002-09-04 Notes


Title: 2002-09-04 Notes

Notes attached.

Our next meeting is the F2F on Wednesday, 2002-09-11, 9:00 AM PDT.

Thanks,
Thomas.
<<20020904 spec sc concall.txt>>

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

Attendees (Y/N):

[Y] Carlisle Adams
[Y] Bob Atkinson
[Y] Thomas DeMartini
[N] Bob DuCharme
[N] John Erickson
[Y] Thomas Hardjono
[N] Hal Lockhart
[N] Kawamori Masahito
[Y] M. Paramasivam
[N] Krishna Sankar
[N] Peter Schirling
[Y] Others: Eve Maler, Martha Nalebuff, Brad Gandee, Benny Higdon,
            Xin Wang, Harry Piccariello

Schedule:

2002-06-12 Change Management Process Working Draft -- Done.
2002-06-12 Change Request Template Working Draft -- Done.
2002-06-19 Approved Change Management Process SC Draft -- Done.
2002-06-19 Approved Change Request Template SC Draft -- Done.
2002-06-26 RLTC-Approved Change Management Process -- Done.
2002-06-26 RLTC-Approved Change Request Template -- Done.
2002-06-26 Begin accepting Change Requests -- Done.
2002-09-04 -- We Are Here.
2002-09-10 Stop accepting Change Requests.
2002-09-11 Spec SC F2F @ Cisco, San Jose
2002-09-12 RLTC F2F @ Cisco, San Jose
2002-09-13 Spec SC F2F @ Cisco, San Jose
2002-10-07 Spec SC F2F @ Cisco, San Jose
2002-10-08 Spec SC F2F @ Cisco, San Jose
2002-10-09 Spec SC F2F @ Cisco, San Jose
2002-10-15 Finish writing and editing specification.
2002-12-01 Package to OASIS administration for processing.
2003-01-01 Package to OASIS members for review.
2003-04-01 Package to OASIS members for voting.
2003-05-01 OASIS spec.

Discussion:

* CR00002
  * Eve
    * Schema design rules for XML: how to encode code lists in UBL.
    * Can be used for non-UBL things.
    * Typically, schemas should be developed by code list owners.
    * Example code list is 3166 country codes.
    * Suggested to include version and agency, but can add other
      info such as date if it is required.
  * BobA
    * What if other agencies don't move?
  * Eve
    * UBL has created some orphan code lists for their use while
      they try to convince code list owners to create official
      schemas.
    * UNECE owns ISO 3166.  They are experimenting w/ schemas.
      However, their schema is mostly a schema for code *lists*,
      rather than a schema for codes.
    * There is an ISO meeting next week or in the near future.  One
      reason for getting the list out there is to show evidence for
      its need.
  * BobA
    * UDDI heavily involved in code lists as well.
  * ThomasD
    * Is there any indication when UNECE will have a schema?
  * Eve
    * Doesn't know, but hopes sooner than later.
    * Encourages us to let them know our needs such as clarity of
      version fields (for instance, semantics of "0.2"?).
    * unece.org/etrades/unedocs/repository/codelist.htm
      * Doesn't match UBL document exactly, but is very close.
    * Marcus Pickardt is a good contact.
* Anyone thinking of submitting CRs?  This time can be used to
  bounce ideas off each other.
  * ThomasD
    * Submitting a couple things for R24, such as about ForAll.
    * Submitting a couple things about a transfer requirement that
      was discussed at the requirements call this morning.
    * Submitting a couple things about R15 based on recent
      developments in the area.
    * Submitting a couple things based on implementation experience.

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC