Upload
miguel-reeves
View
218
Download
1
Tags:
Embed Size (px)
Citation preview
Modular Trade Item OverviewName of Session: eCom
Time of Session:
Speaker: Eric Kauz
Moving forward together, to better serve your business ©2009 GS12
Moving forward together, to better serve your business ©2009 GS12
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).
Moving forward together, to better serve your business ©2009 GS13
Moving forward together, to better serve your business ©2009 GS13
What is Modular Item?
Small Core
ItemContextualized
Attributes
Flexible
Extension to
Send Context
Specific DataIncreased
use of validation
rules to replace
schema validation
Validations
Applied
According to
Context
Changes to Messages
Moving forward together, to better serve your business ©2009 GS15
Moving forward together, to better serve your business ©2009 GS15
New Trade Item
TradeItemIdentificationTradeItemClassification(from Trade Item Classi fication)
TargetMarketInformation
PartyIdentificationTradeItem
lastChangeDateTime : DateTime
1111
0..*0..*
1
+informationProviderIdentification
1
BusinessContextIdentificationTradeItemInformation
contextIteration : NonNegativeIntegerextension : ExtensionType
1..*1..*11
Document(from Document)
<<abstract>>
EntityIdentification(from Enti ty Identi fication)
CatalogueItemState
state : CatalogueItemStateListcancelDate [0..1] : DateTimediscontinueDate [0..1] : DateTime
CatalogueItemNotification
isReload : Boolean
<<root>>
1
+catalogueItemNotificationIdentification
1
TradeItem(from Trade Item)
CatalogueItem
dataRecipient[0..1] : GLNsourceDataPool[0..1] : GLN
11
11
11CatalogueItemChildItemLink
quantity : Integer
0..*0..*
11
Moving forward together, to better serve your business ©2009 GS16
Moving forward together, to better serve your business ©2009 GS16
Context ExtensionTradeItemInformation
PropertyValue
propertyValueIteration : Integer<<choice>> amountValue : Amount<<choice>> codeValue : String {1..70}<<choice>> dateTimeValue : DateTime<<choice>> descriptionValue : Description5000<<choice>> floatValue : Float<<choice>> integerValue : Integer<<choice>> measurementValue : MeasurementValue<<choice>> stringValue : String
PropertyInformation
propertyIdentification : String {1..70}propertyName : String{1..70}
1..*1..*
ClassInformation
classIdentification : String{1..35}classIteration : IntegerclassName[0..1] : String{1..70}classQualifier[0..1] : String{1..70}relatedClassIdentification[0..1] : String{1..35}relatedClassIteration[0..1} : Integer
1..*1..*
ContextualInformationExtension
DictionaryInformation
dictionaryDefinedByPartyIndentifier[0..1] : String{1..35}dictionaryIdentification[0..1] : String{1..35}dictionaryVersion[0..1] : Version
1..*1..*
1..*1..*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”.
Moving forward together, to better serve your business ©2009 GS17
Moving forward together, to better serve your business ©2009 GS17
Example
Contexts
Moving forward together, to better serve your business ©2009 GS19
Moving forward together, to better serve your business ©2009 GS19
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.
Moving forward together, to better serve your business ©2009 GS110
Moving forward together, to better serve your business ©2009 GS110
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.
Moving forward together, to better serve your business ©2009 GS111
Moving forward together, to better serve your business ©2009 GS111
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.
Moving forward together, to better serve your business ©2009 GS112
Moving forward together, to better serve your business ©2009 GS112
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.
Contact Details
Name: Eric Kauz
Title: Methodology Manager
GS1 Global Office
W www.gs1.orgE [email protected]