Adding Semantics to RosettaNet Specifications

1
Adding Semantics to RosettaNet Specifications
Paavo Kotinurmi and Tomas Vitvar
Extract of RosettaNet in WSML ... concept
productIdentification nonFunctionalProperties
dcdescription hasValue Collection of
business properties describing identifiers.
endNonFunctionalProperties
productIdentifier ofType (1 1) string
qualificationAgency ofType (1 1) string
revision ofType (0 1) string axiom
qualificationAgencyConstraint
nonFunctionalProperties dcdescription
hasValue The valid list of agencies who
define product identifiers.
endNonFunctionalProperties definedBy !-
?xqualificationAgency hasValue ?type and
(?type GTIN or ?type Manufacturer
or ?type Buyer or ?type Seller
or ?type EN or ?type BP). ...
Extract of RosettaNet PIP in XML
Schema ... ltxselement nameProductIdentification
typeProductIdentificationType
/gt ltxscomplexType nameProductIdentificationType
gt ltxscomplexContentgtltxssequencegt
ltxselement nameProductName typexsstring
minOccurs0 /gt ltxselement
nameRevision typexsstring
minOccurs0 /gt ltxschoicegt
ltxselement refAlternativeIdentifier
maxOccursunbounded /gt ltxselement
refGTIN /gt lt/xschoicegt
lt/xssequencegtlt/xscomplexContentgt lt/xscomplexTyp
egt ...
Extract of RosettaNet PIP in DTD ... lt!ELEMENT
ProductIdentification (GlobalProductIdentifier
?, PartnerProductIdentification)gt lt!ELEMENT
GlobalProductIdentifier (PCDATA)gt lt!ELEMENT
PartnerProductIdentification
(GlobalPartnerClassificationCode,
ProprietaryProductIdentifier,
revisionIdentifier?)gt lt!ELEMENT
ProprietaryProductIdentifier
(PCDATA)gt ... Message Guidelines add natural
language contraint Constraint One instance of
either "GlobalProductIdentifier" or
"PartnerProductIdentification" is mandatory.
Benefits of Adding Semantics to RosettaNet
RosettaNet and Semantic Web Services

• Benefits
• Ontologies enable semi-automated semantic
  discovery and composition of services.
• The ontology language WSML can represent
  constraints not possible with DTD or XML Schema
  used in PIPs.
• Interoperability can be better supported by
  enabling flexibility between accepted
  definitions. Working with different standards,
  such as EDI, can be supported easier.
• The use of formal ontologies enables using common
  conversion functions to mediate some differences
  with logical dependencies e.g. RosettaNet
  Global Product Unit Of Measure Codes Gram and
  Ounce have a logical relation but this is not
  specified in RosettaNet specifications.
• (Semi) automated mediation of message differences
  can help to make the process of integrating
  partners quicker.

• RosettaNet
• RosettaNet is a widely used XML-based standard
  for B2B integration. Partner Interface Processes
  (PIP) specifications define message semantics and
  sequence.
• Considerable effort is required when implementing
  B2B integration based on RosettaNet PIPs.
• Semantic Web Services
• Semantic Web Services are emerging technologies
  to facilitate (semi) automated discovery,
  selection, composition, mediation and invocation
  of services.
• Semantic Web Services in combination with
  RosettaNet can introduce more dynamics to the B2B
  integration process.
• Semantics can be added to RosettaNet
  specification by lifting RosettaNet PIPs to a
  formal ontology language (e.g. WSML).

Tomas Vitvar tomas.vitvar_at_deri.org
Paavo Kotinurmi Paavo.Kotinurmi_at_tkk.fi,deri.org