David Brossard

> The workaround is to specify directories at `volumes:` , not files. > > [Here ](https://github.com/nkiyo/json-server-with-docker-compose)is the code that worked. > > ``` > services: > json-server: > image: clue/json-server...

As stated by @baboulebou and @aaguiarz, these are implementation-specific requirements that are important but belong in profiles rather than the core spec. Once we have ratified the core spec, we...

We could create a profile for context that maps to specific elements. For instance, we could have an `Obligation` profile that defines a `context` object that contains an `Obligation` array....

- HTTP 401 should be a MUST - the `WWW-Authenticate` should be a SHOULD

@identitymonk we need clarification: do you intend to make authentication mandatory or do you mean to clarify the error code in case of failed authentication? Thanks

Thanks @identitymonk

After chatting with @baboulebou and @identitymonk we agreed that when using a boxcarred request with an evaluation semantic should always lead to a single decision. - permit_on_first_permit should always lead...

On the 6/20 call @ggebel @identitymonk and @davidjbrossard agreed that: 1. We need a top-level decision: why would the PEP have to parse N elements of an array only to...

On the 8/21 call, we agreed participants should add their feedback here to decide on the way forward. Some points that were brought up were: 1. the spec as it...

On the 6/20 ad-hoc meeting, @ggebel @identitymonk and @davidjbrossard agreed that 1. to keep the specs as parallel as possible (between subject, resource, and action search) 2. to plan for...