grouping common profile documents

[Tim Hudson <tjh@cryptsoft.com>]

Working through the list of profile documents (now that the base one is out for review and the first of the new style on the OASIS 1.2 template) I think it would make sense to batch the HTTPS, JSON and XML profiles into one document - "KMIP Message Encodings" with three sections within the document reflecting the content of the committee drafts.

If there are no objections to combining these documents then I'll proceed on that basis - as it seems that those three documents do indeed belong together (unlike most of the other profile documents).

Bob/Subhash - can you add this to the agenda for this weeks call - just a quick check to see if there are objections before asking for an OASIS template starter document for the combined document.

Thanks,
Tim.