UBL Library Content Semantics Ontology –Background presentation at lunchtime –Subteam to develop position paper UDEF –MHP project example Controlled vocabulary

UBL Library Content

Semantics• Ontology

– Background presentation at lunchtime– Subteam to develop position paper

• UDEF– MHP project example

• Controlled vocabulary– CEFACT?

• Contexts– How do we name contexts?

UBL Library Content

Methodology

• Artifact driven

• Document and data-centric views– Documents are assemblies of re-usable data

components (structure and content)

• Design of logical model

• Common core for re-use

• Tools for managing models

UBL Library ContentConceptual view (BOV)

Technology

view (FSV)

The Real World

Ana

lysi

s

Implem

entation

Design

Required or ‘solution’ situationExisting or ‘problem’ situation

The Big Picture

11. Modeling E-business Documents and Processes

Copyright © 2002 Robert J. Glushko

SIMS 290-4, 26 February 2002

1. Plan for Today's Class•What is a 'model'?•What is a 'metamodel'?•Why do modeling?•Disciplines for modeling•Just enough UML•XML as a modeling notation









<BuyerParty>

<Party>

<NameAddress>

<Name1>ABC Enterprises</Name1>

<Name2>Global Services</Name2>

<POBox POBoxPostalCode="249"/>

<PostalCode>20012</PostalCode>

<City>Alpine</City>

<Region><RegionCoded>USNY</RegionCoded> </Region>

</NameAddress>

</Party>

</BuyerParty>

Messages/Documents

Physical Models

Logical Models













<BuyerParty>

<Party>

<NameAddress>

<Name1>ABC Enterprises</Name1>

<Name2>Global Services</Name2>

<POBox POBoxPostalCode="249"/>

<PostalCode>20012</PostalCode>

<City>Alpine</City>

<Region><RegionCoded>USNY</RegionCoded> </Region>

</NameAddress>

</Party>

</BuyerParty>

Form

at

BIEsContexts

BIEsBIEsContextsContextsContexts

UBLLibrary

UBLNDR

UNSMDirectories

schemas

Core ComponentsCore ComponentsComponentsComponents E

ncode

schemasschemasschemas

UBL Library Content

Extending the model

• Separating logical and physical model attributes.– One model, two views– Physical (XML) extends logical

• Business rules– Dependencies, constraints, contingencies– Mike’s position paper

• Physical attributes for XML syntax– Facets, types, etc..– NDR position papers (code sets)

UBL Library Content

Document Schedule• Business context determines document requirements

• Supply Chain Documents:•Order

•Order Response

•Order Change

•Advance Ship Notice

•Invoice

•Proof of delivery/receipt

•Time series

•Inventory Report

UBL Library Content

Procurement Activity

UBL Library ContentProcurement Documents

First Draft

Build model

UBL Library Content

Library Review

• Closed 13th May

• 68 Items– Approach, BIE, Model, Context and CC related– ARTS, NDR, SAP, SGML + 3 individuals

• Clarified and categorized by editing team

• Disposition this week

• Revised schema by end of June.

UBL Library Content

ScheduleMon Tues Weds Thu Fri

AM Semantics

Disposition of Comments


Finish Disposition of Comments, Methodology, Business rules

Future workplan

Lunch Ontology Ontology

PM

Housekeeping

Syntax dependent features

Joint NDR session


Order Response model

4 – 5 Wine and Cheese

Regency

Regency

Regency

Regency

Lake Superior B

Lake Superior B

Lake Superior A

UBL Library Content