Background

W3C XML Schema expression patterns

There are four well-known W3C XML Schema expression patterns. They are:

• Russian Doll

• Garden of Eden

• Salami Slice

• Venetian Blind

The names of these patterns are used in this document. Useful resources for understanding the patterns include:

• https://www.balisage.net/Proceedings/vol25/print/Bruggemann-Klein01/BalisageVol25-Bruggemann-Klein01.html

• Introducing Design Patterns in XML Schemas (oracle.com)

• XML Schema Design Patterns · Saumil Patel

OAGIS maintenance approach and release packages

OAGIS 10.6

OAGi manually maintained OAGIS versions through version 10.6. Version 10.6 was a result of Mike Rowell, OAGi’s former Chief Architect, manually updating XSD files on his file system, running scripts locally, zipping content, etc.

OAGIS 10.6 was/is offered in four release packages (“editions”):

• Enterprise (included all below)

• Platform (included all below)

• Standalone Global

• Standalone Local

• Standalone Local Groups

OAGIS 10.7 and later

OAGi began maintaining OAGIS with Score for version 10.7. OAGi ceased to advertise availability of any XML Schema expressions of OAGIS while quietly making the platform model (Garden of Eden) and Standalone (pattern ) editions available to members on request.

Miscellaneous

JSON schema patterns

What XML Schema design patterns are possible with JSON schema?

“Canonical” meaning

OAGi has historically referred to OAGIS as an “enterprise canonical”. Canonical in this context refers to a format that an enterprise uses to map other formats to/from.

Use cases

Score support for CC expression

Available in Score 3.0 (and some earlier versions)

Module-based expression in W3C XML Schema according to the Venetian Blind pattern.

Available in Score 3.0+ test instance

Choose component or components (e.g., based on noun tag) and express each selected component as W3C XML Schema according to the Venetian Blind pattern. In the case of multiple components, the XSD files will be zipped.

API design

API parameters

1. Model subset: What part of the model needs to be expressed?

   1. All

   2. All except… (e.g., all except supplementary components)

   3. A root component (e.g., BOM)

   4. A set of root components (e.g., BOM, ProcessPurchaseOrder, NotifyShipment)

   5. All components with a specified tag (e.g., noun)

2. Expression type: What is the expression type? (Is there a better name for this other than “expression type”?)

   1. W3C XML Schema

   2. JSON Schema

   3. XMI

   4. Documentation

   5. OAS? (Jim doesn’t think this makes sense)

   6. OWL?

   7. RDF Schema?

3. Pattern: For some expression types, what is the expression pattern?

4. File system structure: For some expression types, what is the file/folder naming conventions and structure?

5. Internal file organization: For some expression types, how content is organized within files? (E.g., within W3C XML Schemas list element declarations first in alphabetical order followed by type definitions in alphabetical order.)