Examples: Resource RDF/XML payloads

Example: Event
Example: Event creation
This example creates an event and sets various properties.
Example: Event PATCH
This example updates the creator, lastOccurence, acknowledged, ownerGID and location properties.
Example: Event query result
The result message from the query capability is nonstandard but optimized to prevent unnecessary repetitive fetches of individual events. When a query is resolved, the OSLC interface has all of the events already. Consequently, in addition to generating a ResponseInfo section detailing the members of the result, the message also provides all of the requested properties of the events in the response too.
Example: Journal
Example: Journal PATCH
This example updates the journal text.
Example: Journal creation
Example: Journal query result
The result message from the query capability is nonstandard but optimized to prevent unnecessary repetitive fetches of individual journals. When a query is resolved, the OSLC interface has all of the journals already. Consequently, in addition to generating a ResponseInfo section detailing the members of the result, the message provides all the requested properties of the journals in the response.
Example: Detail
Example: Detail PATCH
This example updates the detail property of the resource.
Example: Detail creation
Example: Detail query result
The result message from the query capability is nonstandard but optimized to prevent unnecessary repetitive fetches of individual details. When a query is resolved the OSLC interface has all of the details already. Consequently, in addition to generating a ResponseInfo section that details the members of the result, the message provides all the requested properties of the details in the response.
Example: Event Collection Identifier Pattern
Example: Event Collection Identifier Pattern response
The result message from the query capability is nonstandard but optimized to prevent unnecessary repetitive fetches of individual event collection identifier patterns. When a query is resolved, the OSLC interface has all the event collection identifier patterns already. Consequently, in addition to generating a collection block detailing the members of the result, the message provides all the requested properties of the events in the response.
Example: Group
Example: User
Example: RDF/XML success message
Example: RDF/XML error message

Parent topic: Tivoli Netcool/OMNIbus ObjectServer OSLC interface