[xml2rfc] feature request for tagging publication related information

[[e-mail] (Julian Reschke)]

Marshall Rose wrote:

>>Re: issue tracking. I think this is useful as well, and my rfc2629.xslt 
>>already supports some kind of "poor man's change and issue" tracking. 
>>Those who haven't seen that yet may want to check out the XML and HTML 
>>examples on <http://greenbytes.de/tech/webdav/>.
> 
> 
> can you point to one representative file?

Sure:

<http://greenbytes.de/tech/webdav/draft-ietf-webdav-acl-latest.xml>
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-acl-latest.html>
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-acl-latest.txt>

Basically I have

1) issue tracking: ed:issue (with entry and resolution sub-elemenents) and
2) change tracking: ed:ins/ed:del (with an ed:replace container)

Issues have hrefs (for instance, mailing list entry), identifiers, 
dates...; changes keep track of when, why (link to issue), who entered it...

The format works for me but probably is hard to handle for those who 
don't spend as much time with XML as I do. It's greatest benefits are:

- issues and change tracking embedded
- when releasing a new I-D, I can automatically remove all ed:del 
artifacts and all closed issues
- I can generate an appendix summarizing open and closed issues for this 
draft
- automatical generation of stand-alone issues document, such as 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-acl-issues.html>


I am mentioning this to illustrate that it may make sense to implement 
this kind of stuff outside of xml2rfc (with a conversion option to 
"plain" xml2rfc format). This allows playing around with the format 
without having to worry too much about backwards compatibility...

Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:[phone]