OASIS Reference Model & Use Cases
From AMWA-EBU
This page is an introduction to the OASIS Service Definition Reference Model - section 4.3.
The purpose is to use this model to identify key features needed to comprehensively define 'services' in a file-based SOA production environment. These requirements would be used for editing the FIMS first request for technology on a 'common service definition framework'.
As noted in the Reference Model, the service interface is the means for interacting with a service. The service interface will support an exchange of messages, where the message conforms to a referenceable message exchange pattern (MEP):
- the message payload conforms to the structure and semantics of the indicated information model,
- the messages are used to denote events or actions against the service, where the actions are specified in the action model and any required sequencing of actions is specified in the process model.
The following file is a first attempt to apply the OASIS service definition model to FIMS' use case. This first example is based on the 'capture' use case.
File:OASIS Service Interface Reference model final capture.pdf
