Figure 10 — “initialize” operation UML static model Table 25 — UML role name in “initialize” operation request
Name Definition
Data type Optionality and use
sessionInfo The core set of parameters required in each
message exchanged between a client and server operating in a session context, where
these parameters support message routing and session management
SessionInfo, See Table 12
Zero or one Conditional Include when sessions are
supportedrequired by protocol binding andor
result sets are persistent
Table 26 — UML role name in “initiaize” operation normal response
Name Definition
Data type Optionality and use
sessionInfo The core set of parameters required in each
message exchanged between a client and server operating in a session context, where
these parameters support message routing and session management
SessionInfo, See Table 12
Zero or one Conditional Include when sessions are
supportedrequired by protocol binding andor
result sets are persistent
NOTE This general model assumes that operation failure will be signalled to the client in a manner specified by
each protocol binding.
7.2.5.3 “close” operation
The “close” operation is more completely specified in Table 27. provides a UML model of the “close” operation that shows the complete Session class with the CloseRequest and
CloseResponse classes and the class they use. The operation request includes the
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
45
association role name listed and defined in Table 28. The normal operation response includes the association role name listed and defined in Table 29.
Table 27 — Definition of “close” operation
Definition
Allows clients to terminate an interactive session with a server
Receives Identifiers of session and of operation request
Returns Optional identities of session or request in acknowledgement.
Exceptions
Missing Parameter Value, Invalid Parameter Value
Pre-conditions Client has previously initiated identified session
Post-conditions
Optional result document returned to requesting client , and results sets created during the session are deleted and other resources are released.
Figure 11 — “close” operation UML static model Table 28 — UML role name in “close” operation request
Name Definition
Data type Optionality and use
sessionInfo The core set of parameters required in each
message exchanged between a client and server operating in a session context,
where these parameters support message routing and session management
SessionInfo, See Table 12
Zero or one Conditional Include when sessions are
supportedrequired by protocol binding andor
result sets are persistent
46
Copyright © 2007 Open Geospatial Consortium, Inc. All Rights Reserved.
Table 29 — UML role name in “close” operation normal response
Name Definition
Data type Optionality and use
sessionInfo The core set of parameters required in each
message exchanged between a client and server operating in a session context,
where these parameters support message routing and session management
SessionInfo, See Table 12
Zero or one Conditional Include when sessions are
supportedrequired by protocol binding andor
result sets are persistent
NOTE This general model assumes that operation failure will be signalled to the client in a manner specified by
each protocol binding.
7.2.5.4 “status” operation
