1. Modular Trade Item Overview Name of Session: eCom Time of Session: Speaker: Eric Kauz

2. Moving forward together, to better serve your business ©2009 GS1 2 Moving forward together, to better serve your business ©2009 GS1 2 Why Monolithic, one size fits all Rigid class characteristics Rigid attribute usage Reduced flexibility for managing different business scenarios (products, geopolitical, regulatory). Not scalable Scalability is increasingly important as more demands are placed on the standard (e.g. MR4 has over 300 new requirements).

3. Moving forward together, to better serve your business ©2009 GS1 3 Moving forward together, to better serve your business ©2009 GS1 3 What is Modular Item? Small Core Item Contextualized Attributes Flexible Extension to Send Context Specific Data Increased use of validation rules to replace schema validation Validations Applied According to Context

4. Changes to Messages

5. Moving forward together, to better serve your business ©2009 GS1 5 Moving forward together, to better serve your business ©2009 GS1 5 New Trade Item

6. Moving forward together, to better serve your business ©2009 GS1 6 Moving forward together, to better serve your business ©2009 GS1 6 Context Extension Identifies a class such as Marketing Information Identifies an attribute such as Campaign Name Identifies a value for the attribute such as Back To School.

7. Moving forward together, to better serve your business ©2009 GS1 7 Moving forward together, to better serve your business ©2009 GS1 7 Example

8. Contexts

9. Moving forward together, to better serve your business ©2009 GS1 9 Moving forward together, to better serve your business ©2009 GS1 9 Goals in Creating Contexts Make contexts specific enough to limit the attributes and rules to those required for a certain scenario. To limit the number of contexts that the network needs to maintain and that Data Recipients need to register. What does this mean?: a slimmer set of attributes that trading partners have to understand. context sets that are able to handle specific needs of different products/industries/regulations etc.

10. Moving forward together, to better serve your business ©2009 GS1 10 Moving forward together, to better serve your business ©2009 GS1 10 Management of Contexts The creation of contexts will be managed through the GSMP. They will be managed like other message standards through versioning and release schedules. Contexts will be stored in the GDD for retrieval along with associated data and rules. Only contexts created through GSMP will be used within the GDSN.

11. Moving forward together, to better serve your business ©2009 GS1 11 Moving forward together, to better serve your business ©2009 GS1 11 Context and Attributes Definitions, Data Types, Facets do not change per context. Context will drive presence of attributes and cardinality/Optionality. Context could also drive appropriate code list values.

12. Moving forward together, to better serve your business ©2009 GS1 12 Moving forward together, to better serve your business ©2009 GS1 12 Effect on PRICAT Mapping There will still be a single pool of GS1 Trade Item attributes to pull from even if they are subdivided within GDSN by context. The challenge in mapping will be in differences in mapping optionality and cardinality.

13. Contact Details Name: Eric Kauz Title: Methodology Manager GS1 Global Office W www.gs1.org E Eric.Kauz@gs1.org