Conventions for referencing ebXML documents.

[Tim McGrath <tmcgrath@tedis.com.au>]

In an attempt to assist cross-referencing of ebXML specifications, the
QR team wish to propose a convention for Editors to use when referencing
ebXML documents.

We would like all Team Editors to adopt these conventions (rather than
create new ones) in the next round of chnages to their specifications
and related documents.

The following is our first attempt at this.

Technical Specifications
---------------------------------

[ebREQ]  ebXML Requirements Specification
[ebTA]  ebXML Technical Architecture Specification
[ebGLOSS] ebXML Glossary
[ebBPSS]  ebXML Business Process Specification Schema
[ebCCD&A] ebXML Methodology: Core Components Discovery and Analysis
[ebCCDOC]  ebXML Specification – Document Assembly & Context Rules
[ebCCNAM] ebXML Convention – Naming Convention for Core Components
[ebCNTXT] ebXML Concept – Context and Re-Usability of Core Components
[ebCPP] ebXML Collaboration-Protocol Profile and Agreement Specification

[ebRS]  ebXML Registry Services Specification
[ebRIM] ebXML Registry Information Model
[ebMS] ebXML Message Service Specification

Discussion/White Paper/Background Material
--------------------------------------------------------------
[bpOVER] Business Process and Business Information Analysis Overview
[bpPATT] E-Commerce and Simple Negotiation Patterns
[bpWS]  Business Process Analysis Worksheet and Guidelines
[bpPROC] ebXML Catalog of Common Business Processes
[ccOVER] Core Component and Business Process Document Overview
[ccCTLG] The Initial Core Components Catalogue
[ccDRIV] Initial Catalogue of Context Drivers
[secRISK] ebXML Technical Architecture Risk Assessment
[qrROAD] ebXML “Read me” Roadmap


Can you please circulate these to your relevant editors and also
feedback any modifications, additions or deletions you wish to be made.

--
regards
tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142