EBAS Opening Meeting

Attendees:

• Michael Rowell, Oracle, Chief Architect OAG.
• Tobias Vogel, SAP Research, Switzerland.
• Rainer Schuster, ARC Austria.
• Philipp Liegl, ARC Austria.
• Birgit Hofreiter, University of Vienna.
• Kenji Itoh, Japan, JASTPRO (Trade Facilitation Orgn) (former UN-EDIFACT Rapporteur Asia), UEB Glossary Editor. Would like to see updated ebTA
• Steve Capell, Red Wahoo, Australia.
• Marco Zapletal, Vienna University of Technology
• Mark Palmer, NIST, Vice Chair CEFACT (Bureau) - Worked on e-Business Standards convergence forum and would like to contribute
  .

Reviewed EBAS Project proposal. Invited Comments.

• Consensus from group that EBAS proposal was acceptable.
• Worked on e-Business Standards convergence forum presentation from Mark. See attachment.
  See also http://www.nssn.org CEFACT, ANSI, ISO, ITU will participate in a global e-business standards architecture.

Customers for EBAS:

• External users who need to make sense of CEFACT standards.
• CEFACT Management & Working groups.
• Business Standards Consortia / organisations (eg CIDX, GS1, etc).
• Software vendors who may be implementers.

Requirements:

• identify / create a reference model for CEFACT standards. 1999 ebTA is the initial contributions. Review for currency - does it need update?
• Identify all CEFACT standards (technical and business) - including versions and dependencies.
• Vocabularies / classifications for CEFACT and dependent standards (Take contribution from M.Palmer NIST work?).
• Identify CEFACT procedural changes needed to maintain accuracy and currency of the standards list.
• EBAS will include a methodology as well as reference model. ie the "How" as well as the "What"? The methodology will aim to assist users to navigate and use all CEFACT product.

Deliverables:

External Facing

• Architecture Specification (ie conceptual framework / reference model). Normative / ODP.
• Methodology / user guide. Non-normative.
• Repository of current standards - including dependencies & packaging. Non-normative.

  Internal Facing

• Templates / Naming conventions / URI .. etc for CEFACT technical Specifications.
• Architecture compliance criteria - how does a project specification be "compliant" with CEFACT architecture?

Issues:

• How to maintain currency of "repository" data?
  • Each WG chair to update spreadsheet each Quarter?
  • Add our meta-data to some existing FMG spreadsheet?

Resourcing:

• EBAS (reference model / conceptual framework) Editor: Nada
• Methodology / User Guide: Steve
• Repository (spreadsheet): Steve
• Templates / conventions for developing tech specs: COD project??

MetaData For each standard.

Taxonomies for classification

To be developed.