Javascript Object Signing and Encryption
charter-ietf-jose-04

This was formerly a BLOCK, moved to a COMMENT:

> The WG will develop a generic syntax that can be used by
> applications to secure JSON-data, but it will be up to the
> application to fully specify the use of the WG's documents
> much the same way S/MIME is the application of CMS to
> MIME-based media types.

When I've asked App folks who are working on new JSON-based protocols and formats about JOSE, the feedback I've gotten is that they don't see the applicability of JOSE to their work.  It's possible that this is simply short-sightedness, but it disturbs me.  I'd like to have some assurance that there is some real communication between JOSE development and the target uses -- the JSON-based applications -- and that the needs of those targets are being fed into JOSE now, during the development cycle.

Part of this probably involves pushing items 7 and 8 up to the top, working on them actively -- with direct input from the target users -- before nailing down the details.

--- UPDATE for -01-02 ---
The following text was added in -01-02:
The WG will strive to gather use cases to ensure the broadest possible applicability of the mechanism.

That, in addition to discussion with the chairs, makes me happy that we will collectively connect with potential users and collect use cases, dispel myths, figure out who can and should make use of this, and sing "Kumbayah".

I always prefer to see the milestones, to understand how long the charter completion could take, and to see the logical order of the document delivery. 
However, I know that some people don't consider the milestones part of the charter. Let's not redo the discussion here, but can you please order the milestones in a logical order. 
For example, I guess that the following entry should be number 1.
   (7) An Informational document detailing Use Cases and Requirements
   for JSON Object Signing and Encryption (JOSE).

I await with interest the outcome of Barry's first blocking point.