1. Gunther Stuhec SAP AG Container Ship

2.  SAP AG 2003, Title of Presentation, Speaker Name / 2 What kind of containers exists in Modeling? 1/3 1. Generic objects with subtypes 2. Aggregations, Composites of Objects (Grouped Element Containers) ~ Buyer ~ Vendor ~...... Party Wheel CARMotor Door Suggestion: Generalizing and aggregation/ composition should be admit as containers in interfaces. Subclass ( Spezializing ) Abstract Class (Generalizing) 4711 0815 0816 10 20 4711 Composition

3.  SAP AG 2003, Title of Presentation, Speaker Name / 3 What kind of containers exists in Modeling? 2/3 3a. Semantic brackets in general 3b. Semantic brackets: List Containers It could be possible on every position, where a element can be appears Suggestion: We must be care about it. It‘s sometimes useful, if the number of occurences is infinte (like LineItem). Therefore it should be allowed only in the first one or two levels. A 1:cn F D B C G E Graphical grouping Suggestion: Admit in interfaces. It should be used or structuring the general document only (first two levels). LineItem ListOf LineItem OrderLineItemOrder =

4.  SAP AG 2003, Title of Presentation, Speaker Name / 4 What kind of containers exists in Modeling? 3/3 4. Presentational Containers (e.g.: Header, Summary) Header Order Summary OrderNumber... Party LineItem TotalAmount... Arbitrary semantic separation of information into „Header“ and „Summary“. (Represents a „Presentation- Layer“ of a process (serial processing), but is not a grouping of semantic information.). Suggestion: Should be not used in interfaces. Redundant data or can be represented in the header information.

5.  SAP AG 2003, Title of Presentation, Speaker Name / 5 Semantic Brackets Semantic brackets are placeholders (baskets) in a message, to put the objects into the right place. It helps to structuring the messages always in the same and right way. It should be represented as placeholders in the XML-Schema, too. But it should not be occur in XML- Instances.  it is recommended using suffix „Container“ and „xsd:group“ Exp: xsd:group name=„PartyContainer“ MESSAGE Line Item List Identification References Parties Instructions Conditions Item Item Identification Requirements Information Totals

6.  SAP AG 2003, Title of Presentation, Speaker Name / 6 Lists of Occurences List of occurences is an assembly of all occurences into one container. It might be helpful for selection information in a XML-Instance (XPath). Therefore, it should be represented with a specific name in the instance, too.  it is recommended using the name „List“ as suffix Exp: xsd:element name=„ LineItemList“ MESSAGE Line Item List Identification References Parties Instructions Conditions Item Item Identification Requirements Information Totals

7.  SAP AG 2003, Title of Presentation, Speaker Name / 7 Container and list Advantages of container: Allways sematically group in the same way It gives all business documents the same structure Helpful for the definition of documents Advantages of xsd:group: The container itself occurs not in the XML-instance No additional unnecessary redundant information  Because semantic containers are only necessary in the design-time XPath-expressions corresponds to the dictionary entry names Advantages of list-container: Easier selection by XPath-expression Better separation of many occurences

8.  SAP AG 2003, Title of Presentation, Speaker Name / 8 Example of an XML-Instance <Order xmlns="urn:oasis:names:tc:ubl:Order:1.0:0.70" xmlns:cat="urn:oasis:names:tc:ubl:CommonAggregateTypes:1.0:0.70" xmlns:cct="urn:oasis:names:tc:ubl:CoreComponentTypes:1.0:0.70" xmlns:ccts="urn:oasis:names:tc:ubl:CoreComponentParameters:1.0:0.70" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:ubl:Order:1.0:0.70 C:\scripts\xsd\UBL_Library_0p70_Order.xsd"> token 1967-08-13 …...... token......... … … 3.14 … 3.14... E1001... E1002... E1003...

9.  SAP AG 2003, Title of Presentation, Speaker Name / 9 No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies. Copyright 2003 SAP AG. All Rights Reserved