Attendees:
Garret Minakawa
Fred van Blommestein
Alan Stitzer
Sylvia Webb

Administrative:
  - Conducted roll call of attendees
  - Verified permission was granted to record the call

Review Agenda:
  - Define project plan for the next 6-8 weeks
  - Review ATG2 NDR Gaps and Comments

Define Project Plan:
  - Review list of tasks from August F2F meeting
    * Review TBG17 components and submit feedback
       - Confirmed with Alan that initial 19 components were finalized and approved by TBG17
       - Any feedback re:19 approved components must be done via Change Request Form
       - TBG17 should be publishing 19 approved and next set of components within the next week
       - WG should be focusing on the next set of TBG17 components prior to end of comment period
       - TBG17 comment period will end 4 weeks before next F2F (December 6, 2004)
       - WG still needs to re-evaluate 19 approved components and determine if Change Requests
              are necessary
       - Alan reported on UBL/TBG17 conference call.  Tim McGrath to review 19 approved components
               and compare to UBL.  Marion Royal to report on UBL comments not accepted by TBG17
       - Announced requirement to re-submit original contribution with full definitions
    * Order of priority will be:
       1. Review next set of TBG17 components before end of comment period
       2. Identify gaps between OAGIS and 19 approved components
       3. Complete re-submission of OAGi Core Components
    * Review ATG2 NDR Document
       - Initial set of comments were submitted to ATG2 on 10-Sep-2004
       - Most of the OAGi comments were addressed at the UN/CEFACT Forum meeting
       - WG needs to review recent ATG2 decisions, identify gaps, and determine how to deal with gaps
       - ATG2 NDR applies to both Core Components WG and Architecture WG
       - Still need to wait for ATG2 to address remaining OAGi comments
    * Review ISO TC154 7372MA
       - Identify areas where 7372MA intersects with existing OAGIS library and evaluate whether
                   OAGIS should adopt 7372MA

Review ATG2 NDR Comments and Gaps:
  - Discussed OAGIS-ATG2-Diffs.xls from WG web site
    * Raised issue about how external organizations should apply ATG2 NDRs in order to be compliant
       - Using prologue as an example, should external organizations use the same prologue as
                   ATG2 in order to be compliant?
       - This would not make sense for external organizations
    * Annotations
       - Fred pointed out that annotations could be important for harmonization if the harmonization
                    is based on UniqueId or DictionaryEntryName.
       - Some discussion about whether ATG2 annotations should be appinfo or documentation
       - Recommendation to Architecture WG will be to adopt the ATG2 annotation scheme
    * ID vs. Id
       - Group agreed that abbreviations should have upper case first character followed by all
                    lower case
    * Code List and Identifier Lists
       - Big architecture issue about whether OAGi will adopt ATG2 Code List implementation
       - Most other standards organizations are undecided about their Code List implementation
       - EAN/UCC has tentatively committed to implementing the ATG2 Code List scheme
       - Question raised about whether code list extensibility conflicts with CCTS
       - Explained ATG2's rationale for excluding several supplemental components
       - Question raised about whether supplemental components such as AgencyId and
                    AgencyName are useful in an XML instance document
       - URIs can be processed and would be more useful in an instance document
       - Acknowledged that people need to better understand how data will be used for design
                    time (XML Schema) vs. run time (XML instance)
       - Need OAGi Architect to resolve this issue
    * mimeCode required for BinaryObject
       - No consensus about whether mimeCode should be required
    * LanguageId
       - ATG2 decided to use xsd:language at the UN/CEFACT Forum meeting

SUMMARY:
  - Priority of Tasks are:
    * Review next set of TBG17 components
    * Review and gap analysis of 19 approved components
    * Resubmit OAGi Core Components to TBG17
  - Other Tasks:
    * Review ISO TC154 7372MA and identify areas of possible adoption within OAGIS
    * Address open issues with ATG2 NDR
  - OAGi Architect required to resolve many of the NDR open issues
  - ATG2 NDRs need clarification about how external organizations should implement
  - Recommendation to Architecture WG that ATG2 annotation scheme be adopted by OAGi

Next call scheduled for Tuesday, October 5 at 8:00 PDT.