W3C home > Mailing lists > Public > spec-prod@w3.org > April to June 2007

Tools to revive an old-ish TR and convert it to an RFC?

From: Thomas Roessler <tlr@w3.org>
Date: Mon, 9 Apr 2007 12:27:49 +0200
To: spec-prod@w3.org
Message-ID: <20070409102749.GG8674@raktajino.does-not-exist.org>

The XML Security Specifications Maintenance WG [1] will soon be in
the business of editing xmldsig-core (this round of edits will be
relatively limited, but more work might be ahead in the future); the
group is chartered to submit a version of its edits to the IETF for
publication as an RFC.

That brings up at least two important editing toolchain issues:

- What's the general wisdom in terms of converting an existing TR
  from HTML to xmlspec -- to what extent is that even deemed
  feasible with tools (i.e., how much information loss is there in
  the conversion from xmlspec to html), are there tools that go part
  of the way, or would some poor editor be in for a rather
  terrifying manual conversion job?

  (The obvious alternative would be to edit the HTML directly.)

- Assuming we'd go for xmlspec, is there any existing tooling that
  would lend itself to easily producing an RFC out of this, e.g. by
  transforming xmlspec into the format defined in the latest
  draft-mrose-writing-rfcs [2], and then using the tools that are
  common in the IETF?

1. http://www.w3.org/2007/xmlsec/
2. http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html

-- 
Thomas Roessler, W3C  <tlr@w3.org>
Received on Monday, 9 April 2007 10:27:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:14 GMT