A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2016; you can also visit the original URL.
The file type is application/pdf
.
A framework for obligation fulfillment in REST services
2011
Proceedings of the Second International Workshop on RESTful Design - WS-REST '11
An Obligation is an expression of non-functional or cross-cutting requirements, the scope of which transcends any specific service, but for which the service bears an enforcement responsibility. Example use cases include regulations imposed on handling of Electronic Health Records. We describe the concept of an Obligation, provide example use cases, and then define a general design pattern for when a REST developer should consider their use. We then describe a proof-of-concept implementation
doi:10.1145/1967428.1967443
dblp:conf/rest/FieldGM11
fatcat:k6jnzjoujrgsbjpbixzsfaamfi