
Readme File (Last modified) Date: 29 June 2004

====================================================================================

What is in this Readme File:
1. Overview
2. Getting Started
3. New Components in the RosettaNet PIP(TM) Specification package
4. Related Documents
5. Copyright and Legal Disclaimer
6. Support

====================================================================================

1. Overview

This document provides information that should be reviewed prior to using the PIP 
Specification package.  PIP specification packages labeled with version 11.00.00 
represent the new XML Schema Format (Modular) for RosettaNet PIP Specifications.  
The PIP Specification package contains different components as compared to its 
predecessor, DTD based PIPs (Monolithic). 

====================================================================================

2. Getting Started

To effectively view the contents of the specification package, it is recommended 
that all files be extracted onto your desktop.  This will display the folders for 
easy viewing and navigation.

====================================================================================

3. New Components in the RosettaNet Specification package

After extracting specification package onto your desktop, the initial view is 
comprised of a:   
a.  RosettaNet ReadMe file - Provides basic support information for the 
    specification package.

b.  XML folder - Contains the normative, machine-readable RosettaNet standard.  
    This folder is comprised of the following items:
      ·	  Domain Folder - The domain model folder contains at least one 
          domain (i.e. Collaborative Forecasting) and may contain multiple domains 
          (i.e. Collaborative Forecasting, Logistics, Finance, etc.) that a specific 
          PIP contains.  Each domain folder contains data structures that are 
          specific to an area of knowledge (i.e. Logistics).  
      ·	  Interchange Folder - This contains one or more XML Schema file with the 
          file name format of 'Name of Message'.xsd. These XSD files are the XML 
          Interchange (the PIP/business document).  This file provides the structure 
          of the document, but does not contain all information necessary.  The 
          information not contained within this XSD file is imported from the multiple 
          xsd files contained within the domain, system and universal folders.
      ·	  System - System structures are the components of the Standard 
          Document Header as adopted from the UN/CEFACT.  This folder contains the 
          XSD files of those objects. 
      ·	  Universal - A Universal structure is an object that may be used 
          across multiple PIPs and is not specific to a particular domain.  This folder 
          contains the XSD files (by category) of the objects contained within the 
          specific PIP. 
      ·	  'Name of PIP' BPSS - This XML instance provides the message control 
          parameters for the given PIP.  The BPSS file is based upon the ebXML BPSS 
          version 1.01 with modifications.

Note: The Domain Model and Universal folders are comprised of 
      Data Structure and Codelist XSD files.

c.	Descriptive Folder - Contains the non-normative, human-readable form of the 
        RosettaNet standard.  This folder is comprised of the following documents:
     ·	Description of the Partner Interface Process - Provides message control 
        parameters in textual form (similar to the PIP Specification in DTD based 
        PIPs). These parameters are the same as what is used in the BPSS file.
     ·	Description of PIP Messages - Provides the dictionary component similar to the XSD 
        files (like the bottom portion of the Message Guidelines in DTD based PIPs).
     ·	'Name of Message' Folder for each Message in the PIP- This subfolder contains 
        the Message Structure and XML instance files:
         · Message Structure - Provides the business document's hierarchical structure 
	   similar to the XSD files in a spreadsheet (similar to the Message Guidelines 
	   in DTD based PIPs).
	 · XML instance - Provides a sample message.

Note:  Should a discrepancy arise between a descriptive document and an XSD file, 
the XSD file should be adhered to.  

====================================================================================

4.  Related Documents

·  RosettaNet ebXML BPSS Guidelines
·  RosettaNet Namespace Specification
·  RosettaNet XML Design Guidelines 

To locate the documents noted above, visit http://www.rosettanet.org/architecture 

====================================================================================

5.  Copyright and Legal Disclaimer

Copyright: © 2004 RosettaNet. All rights reserved. No part of this publication may 
be reproduced, stored in a retrieval system, or transmitted, in any form or by any 
means, electronic, mechanical, photocopying, recording, or otherwise, without the 
inclusion of this copyright notice. Any derivative works must cite the copyright 
notice. Any public redistribution or sale of this publication or derivative works 
requires prior written permission of the publisher.

Trademarks: RosettaNet, Partner Interface Process, PIP and the RosettaNet logo are 
trademarks or registered trademarks of "RosettaNet", a non-profit organization.  
All other product names and company logos mentioned herein are the trademarks of 
their respective owners.  In the best effort, all terms mentioned in this document 
that are known to be trademarks or registered trademarks have been appropriately 
recognized in the first occurrence of the term.

====================================================================================

6. Contact: RosettaNet 

For information regarding how to read the New PIP Specification format, please refer 
to the New PIP Specification Package Training module located on the RosettaNet Web 
site at http://www.rosettanet.org/newpipspecformat 

For additional support for RosettaNet Partners, please contact: 
http://www.rosettanet.org/support
support@rosettanet.org

====================================================================================

-- END OF FILE --

