ID: 7
Title
- Extend information model with user-defined classes
Description
Currently ebXML Registry allow clients to extend Registry Information Model (RIM) only via attribute extension using Slots on existing RIM classes.New RIM classes cannot be defined.
This use case envisions allowing clients to extend Registry Information Model (RIM) classes be defining new classes that may be sub-classes of existing RIM classes .
The result is that verticals and enterprises may specialize ebXML RIM to meet their domain specific needs.
Use Case Diagram: Extend information model with user-defined classes
Actors
- Domain Expert
- Content Publisher
- Registry
Priority (Low, Medium, High)
- Medium
Pre-conditions
- None
Post-conditions
- None
Basic Flow
- Domain expert defines extension to RIM by submitting new RIM
classes to the Registry
- Content publisher may now submit instances of new RIM classes to the Registry
Alternative flows…
- None
Exceptions
- None
Includes Use Cases
- None
Special Requirements
- None
Assumptions
- It is envisioned that in order to support this use case the RIM would have to be expressed in an ontology syntax chosen byu the registry
- It is likely that the Ontology syntax chosen by the registry will be OWL.
Use Case Relationships
- None
Issues
- None
-- Regards, Farrukh