[rfc-i] New Version Notification for draft-hoffman-xml2rfc-18.txt

Heather Flanagan (RFC Series Editor) rse at rfc-editor.org
Wed Jun 3 14:08:34 PDT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

At this point, I am seeing compelling reasoning from both sides of the
discussion. What I'd like to see, and we have discussed doing this in
the design team but could use further input, is a proposal that actually
lays out in table form what <xref> would need to look like with all the
expected attributes, and indicate which attributes should and should not
be seen together.  Someone would need to be able to code against that
description.

I think expanding <xref> will work, as will the proposal to tighten up
the definition of <xref> and create <relref>. Since both will work and
we need this to be resolved in order to unblock several documents and
create the final RFPs, I'm setting a time boundary on this particular
debate. I'm looking for proposals and discussion by Tuesday, 9 June. If
no one has cycles to create the full <xref> description, then we'll go
with the creation of the new element; as I've said, it sounds like both
will work.

Thank you in advance for your input!

- - -Heather
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCAAGBQJVb2zSAAoJEER/xjINbZoGic4H/i7klCzEuzrqQQWItMx50MqB
Rmzih00X3lDKZ2ECWMa8zvYbSWSSblULMSKVVTZHPKb51D/DAaw4Ci+J5SBz/mvp
CEP76RA+8bphbZfGbbvBUccC0alVf0o8Ow7+p3+JjN23G0tTBKNmZEeJ1OS3i/Tt
osCYfrkU9ck/AD4BQz2/8VQVdqQajC1O1OJGkejjVrANavUlE4x7px9e1974KcxE
fTCUdXYmSafiFJqMseAbSJ5KaEPtY622X+D9tx9jksaZvMnmCOhEcg8eK2m7xtbX
tJN7pGMQpygK9wvfJkm1gZfJ4j8WnAzqFXsD2zVPG0PU9Mt2dqZSci/k142sScg=
=H/aA
-----END PGP SIGNATURE-----


More information about the rfc-interest mailing list