Oversight on my part.

I have not included the address endpoint

Proof is in tasting pudding they say or maybe in our case it will be dog food.

I need to run this through a code generator to see what monster I have created.
Hopefully it is pretty and pretty easy to use but it could also transform into a it's alive situation.

Really need more examples in the code.

I lef the JSON schema's for RAML 0.8 includes in the file. No side effects but need to remove them as we are now moving to RAML 1.0

This might be needed in future.

We need to create an endpoint:

/address
/address/{addressid}

Currently the paging trait does not include the following items:

1. first
2. last
3. next
4. previous

The vent operations will be used primarily by clients that synchronise data from the API to their local persistent storage.

The operations can be draining on the system thus it is proposed to use HTTP 429 Too Many Request as a potential cure for clients being a bit optimistic over a slow connection for example.

:)

The system needs to be able to filter on lists. This is currently not implemented.

Since we are dealing with two objects here is it worth implementing them in traits?

We could create the following traits:

1. Customer Filter Traits
2. Address Filter Traits.

Review wiki and add more details and remove unneeded details from draft.