The core of the WS-Agreement specification describes a number of things, (omitting examples, use cases, and WSDL)

S3. Architecture
S4. Agreement Structure
S5. Agreement Template
S6. Definition of Template compliance
S7. Runtime States of guarantee terms and services
S8. PortTypes

15 of the 27 pages spent on the above are contained within Section 4.  It strikes me that the agreement document 
structure is valuable on its own.   I propose that the WS-Agreement specification be split into two parts: a document 
format document, and a WS-Agreement protocol document, describing how WS-Agreement uses the document format to 
facilitate agreements.

This would be a good, clean and easy decoupling to make.  The document format document would also be more resiliant 
against changes in underlying specifications such as WS-Addressing and WSRF-ResourceProperties - all of these 
dependences would be located within the protocol document.

(Anecdotally, some people I spoke to believed that was the split which took place when WS-Agreement split into WS-
Agreement and WS-AgreementNegotiation.  They thought it was a good move...)