[use-case] #1 - eBusiness Industry Dictionary: nouns

["David RR Webber" <david@drrw.info>]

Re-post as HTML

Title: untitled

ID:  1

Title

• eBusiness Industry Dictionary: nouns

Description

Organizations such as OAGi, RosettaNet, STEP along with eGov initiatives such as MOD, DOJ, IJI and EPR require interoperable semantics of noun definitions for their industry domains. OASIS TCs such as CIQ need means to document their noun semantics in Registry.

To date the Registry provides Classifications, Taxonomies, the RIM and logical models (CCTS) but no means to capture consistent semantics around the physical noun details. W3C XSD schema provides some small limited subset of this - datatype, use, annotation, tokenized values, but much more is required, and especially the ability to support context driven semantics, language localization and consistent versioning.

Coupled to this is the ability to support assembly of ebusiness transaction documents from the noun dictionary both as models (CCTS) and physical transactions (CAM). The ability to link in OWL and topic maps to further add semantics to the nouns should be part of the design considerations, with the aim to enhance the
physical noun collections for discovery and re-use.

Initial deliverable is an XML instance for storing physical noun semantics in registry that is optimized to take best advantage of existing registry features and enable ebusiness transaction assembly from the noun definitions. Multi-lingual locale support is also required along with context driven content semantics.

The XML instance will allow implementors to have a consistent information set of nouns across industry domains and provide the building block for adopters to rapidly implement ebXML Registry based dictionaries from their existing manually managed dictionary content.

Actors

• business information analyst

Priority (Low, Medium, High)

• High

Pre-conditions

• None

Post-conditions

• None

Basic Flow

1. analyst #1 publishes a semantic noun as XML to registry
2. analyst #1 assigns classification and taxonomy to noun entry
3. analyst #2 queries and retrieves noun based on industry search criteria
4. analyst #2 uses browse and drill down to locate specific noun meeting industry criteria

Alternative flows

1. machine process retrieves semantic noun details as XML
2. referencing is done via direct external key value look up and using REST interface
3. machine process scans registry for matching industry nouns and produces catalogue of same as human readable report

Exceptions

• None

Includes Use Cases

• None

Special Requirements

• None

Assumptions

• Industry analyst creates dictionary content using domain expertise.
• Noun details may be spread across multiple registries that may or may not be federated

Use Case Relationships

• None

Issues

• None