Optional binding
Minimal HTTP reference
ABCS business semantics are transport-neutral. ABR demonstrates one optional HTTP binding so adopters can experiment with a familiar interface without making HTTP normative.
Discover
GET https://abr.sirvisetti.com/capabilities
Describe
GET https://abr.sirvisetti.com/capabilities/procurement.purchase-order.submit
Invoke
POST https://abr.sirvisetti.com/capabilities
Content-Type: application/json
{
"abcs": "0.2",
"capability": "procurement.purchase-order.submit",
"requestId": "demo-001",
"payload": { ...canonical Purchase Order... }
}Reference behavior
The three demonstrations include business-oriented checks: purchase-order submission requires a draft/not-submitted order with lines; journal posting requires a draft balanced entry; leave submission requires a draft/not-submitted request with a valid date range.
Non-normative: these checks make the reference useful to explore. They do not add requirements to ABCS beyond the normative capability definitions and schemas.
OpenAPI
The OpenAPI document describes only this ABR HTTP binding. It does not replace ABCS and is not normative.
