Re: [Rswg] Making progress on evolving the XML format

[Joel Halpern <[e-mail]>]

Rereading this email several times, I think I am missing some minor aspects.

I think the idea is that the RFC in its main body would contain:

1) description from 7990 that continues to apply

2) descriptions from draft-irse-xml2rfcv3-implemented that are agreed to 
apply going forward

3) descriptions of changes to the format that the rswg (and then the 
community) have adopted in addition to the above two.

I can not find where item 3 is described in the text you sent. Probalby 
my mis-reading.

And then, in the appendix, there would be a record of

1) Any things from 7990 that were removed / obsoleted / significantly 
modified in the process

2) any items from -implemented that were rejected by the process

So that the appendix would allow one to construct the description of 
what is "currently" implemented.

Have I understood that properly?  Is there any way to do that such taht 
it would be easier for a reader to reconstruct the interim state if / 
when they need to figure it out?

I don't know what this says about the referenced emergency changes, and 
how those would be described.

Thanks,

Joel

On 2/13/2023 3:27 PM, Eric Rescorla wrote:
> Hi RSWG members,
>
> Pete and I have been chatting about the best way forward for evolving
> the XMLv3 grammar. We think that there's broad agreement that:
>
> 1. We need some document that describes the "as-is" xmlv3 format.
>    - That document should be published in some form that implies
>      it doesn't have consensus.
>    - The WG should do the work of making sure that happens
> 2. We need to work on a new format (v3.1?) that will have consensus.
>
> I think people are assuming that the new format will need an RFC but
> there is not agreement on whether the "as-is" should be.
>
>
> Pete and I would like to propose the following way forward, based
> on a suggestion from Martin Thomson in January.
>
> - Adopt draft-irse-draft-irse-xml2rfcv3-implemented as a WG document
>   to use as the basis for v3.1.
>
> - Everything that doesn't match RFC 7990 will be marked as
>   "provisional". We go through all of these and either adopt them as
>   having consensus or decline to make the change, in which case we
>   move them to an Appendix.
>
> - If necessary, we can also update the I-D to make consensus changes
>   to the as-is version on an "emergency" basis, though hopefully
>   this will not be needed often.
>
> At the end of this process, we will have a document which describes
> the consensus format and also an appendix which describes how "as
> implemented" differs from the consensus format. These can be published
> together as an RFC, which will provide archival forms of both but
> without requiring that we publish an RFC of the current document while
> the consensus version is still in flux. In the meantime, the ID
> can serve as the definition of the current format.
>
> What do people think of this proposal?
> -Ekr
>