Response Criteria

ResponseCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned.

ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD’s noun exemplar.

ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns.

That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated.

The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies.

Child Components

Response Expression 0..1
Change Status 0..1

UML Class Model

The following link opens the SVG image in a separate browser tab.
You can save the file locally and use it, for example, in PowerPoint.
SVG File
@startuml

class ResponseCriteria {
    String ResponseExpression
}

class "ChangeStatus"{}

ResponseCriteria o-d- "0...1" "ChangeStatus"

hide circle
@enduml

Where Used

Following is a list of components that have Response Criteria as a child component.

Feedback

OAGi and its members welcome your feedback.

UUID: 0c7f17ab099d4cffa0819ceec2b421b7

connectSpec (OAGIS) Version 10.12