<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hello SSE Working Group,
<div class=""><br class="">
</div>
<div class="">Now that the CAEP-related work in starting to solidify, I think it appropriate to merge changes into the existing RISC Profile document, in order to establish continuity between the current Implementer's Draft and what will hopefully soon be the
new Implementer's Draft.</div>
<div class=""><br class="">
</div>
<div class="">I have scanned through the diff between the two documents, and while there are a number of changes, I think they can be merged in pretty cleanly. Most of the changes are additive, and there is little to no drastic rewriting or reordering of sections,
or other mutations that would make for a messy merge process. However, I recommend we break the changes down into several pull requests, along these lines:</div>
<div class=""><br class="">
</div>
<div class="">
<ol class="MailOutline">
<li class="">Replace core Subject Identifier Type definition with reference to draft</li><li class="">Minor editorial corrections</li><li class="">Renaming (e.g., "RISC" to "SSE", or something else?)</li><li class="">New Subject Identifier Types</li><li class="">Stream Updated event</li><li class="">Small-scope normative changes, taken individually, e.g.,:
<ol class="">
<li class="">Stream Updated event</li><li class="">Change to meaning of missing "verified" property in an Add Subject request</li><li class="">202 responses</li></ol>
</li><li class="">Everything related to SPAGs</li></ol>
<div class=""><br class="">
</div>
</div>
<div class="">This will let us clear through the simple changes quickly, and make it easier to understand the more complicated ones. This will also give us an opportunity to surface the more significant changes to the list. I think a lot of discussion as happened
on calls and face-to-faces (back when we could have those) that hasn't made it to the list, which means it isn't well documented and we haven't really established working group consensus.</div>
<div class=""><br class="">
</div>
<div class="">I think most of these will be non-controversial, but there are a few items that we may want to poke at. (e.g., is SSE the right name for this?)</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div>—</div>
<div>Annabelle Backman</div>
<div><a href="mailto:richanna@amazon.com" class="">richanna@amazon.com</a></div>
<div class=""><br class="">
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
</div>
</body>
</html>