ebXMLRegistry Semantic Content Management SC Use Case |
|||
UC ID: | 1 | Priority (L/M/H) : | High |
Use Case : | 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 | ||
Pre-Conditions: | none | Post-Conditions: | none |
Basic Flow : |
|
||
Alternate Flow : |
|
||
Exceptions : | none | ||
Includes Use Cases: | None | Special Requirements: | None |
Assumptions: |
|
||
Use Case Relationships: | None | Issues : | none |
Examples: | |||
proposer david@drrw.info |