SRDC Ltd.

1

Problem Solutions

Various standardization efforts◦ Document models

addressing a broad range of requirements vs Industry Specific Document Models

◦ No conceptual semantic model

◦ Not re-usable for different collaborations

UN/CEFACT CCTS◦ flexible and adaptable

business document schemas

◦ Context-free and syntax independent building blocks

◦ Conceptual Model UBL

◦ UN/CEFACT CCTS implementation in XML

◦ Customization Guidelines

2

Integrates modeling approach of UN/CEFACT CCTS and UBL ◦ Modeling: UN/CEFACT CCTS◦ Customization: UBL

Maximize re-use of business information, minimize duplicative effort◦ Allow discovery of document building blocks◦ Presents document artifacts created or customized by users as well

as UBL 2.0 Common Library Artifacts

Online and 7/24 accessible

Common, standard based, and evolving repository architecture

Graphical Modeling combined with information on conceptual model

Documentation of e-business document model

3

4

Examination of document artifact structure and information content in a single complete view◦ Navigation over document structure from message assembly to data

type along with their properties

Discovery of components

Accessibility and sharing of components via the repository

Modeling of standard-based document artifacts which are at the same time tailored to specific requirements◦ Modification of components

Compatible Customization Conformant Customization

◦ Creation of components from scratch

Generation of UBL Document schema accompanied with some informative supporting materials

5

Conventional Model Document Designer

6

Document Model file

UBL Common Library file

Qualified Data Type file

Unqualified Data Type

•Presents document artifacts in a single Russian Doll modelas the tree expands

With the properties of selected component such as definition, cardinality etc.

7

Aggregate Business Information View

Basic Business Information View

Data Type View

Visualization of Document ArtifactsVisualization of Document Artifacts

Text based search Query format adaptable to conceptual model of different

document artifacts Allow specification of keywords on

Context values Definition Qualifiers Dictionary entry names Business Terms etc. based on document artifact type

Logical connectors in query : “OR” vs “AND” Search result includes both standard document artifacts

provided by UBL and standard-based document artifacts created by users

8

Changes “status” when user commits the component to the repository

Assembling available document building blocks to a new document artifact in graphical model: (1) Drag

(2)Set properties of conceptual model

(3) Drop

9

New QDTs can be created by ◦ Qualification of UDTs◦ Further qualification of QDTs (1)Restricting content component : Add or Delete restrictions

Restriction types varies according to Type of Content Component

10

(2) Subsetting supplementary components

•No new UDTs, it inherits UBL 2.0 UDTs

“A UBL conformant instance is an instance validating against customized document constraints while simultaneously validating against a UBL standard schema.”

UBL Customization Guidelines v1.0

11

Subsetting original document artifacts◦ Removing optional building blocks

(1) Through selecting “Delete” on right click

(2) Through check tree feature Automatic removal of inner document artifacts from document schema

12

optional

Subsetting through cardinality restriction◦ Changing cardinality

Minimums can be increased to their maximum Maximums can be decreased to their minimum

Constraining Context of Business Information Entities◦ Add◦ Delete

13

Extending document schema module by◦ Adding new components—other than using extension

element

◦ Discarding mandotary components minimum cardinality >=1, Mandatory element is in RED

◦ Changing cardinality values to a range which violates conformance design rules Decreasing minimum cardinality Increasing maximum cardinality

Changing property term qualifiers

Building a component from scratch

When an action results in UBL compliant document by violating conformance document design rules, the tool warns the user that the design will be conformant if the action is realized.

14

Export UBL Document schema accompanied with some informative supporting materials in UBL directory format

◦ XML Schema of Document Assembly with automatic translation from graphical model by UBL Naming and Design Rules

◦ Spreadsheet models defining the document assembly

◦ Genericode files for defining code lists (aka. enumerations or controlled vocabularies)

15

16

Based on a spreadsheet template, new code values can be assigned to data types.

17

Filled template is submitted from Data Type Properties -> Genericode view.

18

Predefined cardinality rules◦ Right click on any element on the document

content hierarchy

19

Any rules using XPATH language can be added for document elements

20

Rule Context: Shows the context attribute based on the ‘assigned node’ of the rule that will be created in the schematron file

21

Assigned node: Shows the XPATH of the document element to which the custom rule is assigned.

22

Rule Test: Assertion for the rule

23

Text to Display: The text in case the assertion of the rule fails

24

Thank you for your attention Demo Links: Overview of the tool :

http://144.122.230.53:8080/DocumentDesignerToolViewlets/main.htm Creating a new document artifact:

http://144.122.230.53:8080/DocumentDesignerToolViewlets/createMessage.htm Qualifying a data type

http://144.122.230.53:8080/DocumentDesignerToolViewlets/datatype.htm Conformant Customization:

http://144.122.230.53:8080/DocumentDesignerToolViewlets/conformantCustomization.htm Compatible Customization:

http://144.122.230.53:8080/DocumentDesignerToolViewlets/compatibleCustomization.htm Documentation of Document Model:

http://144.122.230.53:8080/DocumentDesignerToolViewlets/exportXSD.htm

25