This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
design:start [2013/10/15 14:47] rsewikiadmin |
design:start [2015/10/13 08:36] rsewikiadmin added reading list; removed discussion topics |
||
---|---|---|---|
Line 11: | Line 11: | ||
* is based on a solid mark-up language that is expected to exist for the foreseeable future. | * is based on a solid mark-up language that is expected to exist for the foreseeable future. | ||
- | Over the past few months, the [[design: | + | Authors may continue to submit XML or text files when their I-Ds are approved |
- | ==== Requirements ==== | + | By allowing for multiple Publication formats, readers can choose a format that works best for their circumstances. |
- | * [[design: | + | |
- | * [[design: | + | |
- | * [[design: | + | |
- | * [[design: | + | |
- | * [[design: | + | |
- | ==== Recommendations and discussions | + | Over the past two years, the [[design: |
- | * [[design:formats|Thoughts on Non-Canonical Formats]] | + | |
- | * [[design:tool|Ideas for the RFC tool]] | + | ==== Reading list ==== |
- | * [[design:svg|Thoughts on SVG]] | + | The RFC Format is a large project that has required several documents to capture the requirements found in each aspect of the work. The documents depend on each other, and are moving through the community review and publication process as a set to help keep those relationships intact. Several documents require understanding a separate document for full comprehension of the material. |
- | * [[design:utf-8|Thoughts on UTF-8]] | + | |
+ | Below is the suggested reading order for the drafts that describe the new RFC format requirements. The design team has done a great job in pulling all fo this together, and many members of the community have reviewed these in parts and offered targeted feedback. Please take this time to review the drafts as a compendium, and then review the Statements of Work that describe the programming effort that will depend on these drafts as their requirements. | ||
+ | |||
+ | 1. The big picture | ||
+ | * Flanagan, H., "RFC Format Framework", | ||
+ | |||
+ | 2. The underlying vocabulary | ||
+ | * Hoffman, P., "The ' | ||
+ | |||
+ | 3. The outputs | ||
+ | * Hildebrand, J. and P. Hoffman, " | ||
+ | * Flanagan, H., " | ||
+ | * Hansen, T., Masinter, L., and M. Hardy, "PDF for an RFC Series Output Document Format", | ||
+ | * Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", Work in Progress, | ||
+ | |||
+ | 4. Generalized requirements | ||
+ | * Flanagan, H., "The Use of Non-ASCII Characters in RFCs", Work in Progress, | ||
+ | |||
+ | 5. Workflow and tools (note that the examples draft will not become an RFC, but is necessary for the project) | ||
+ | * Hildebrand, J. and P. Hoffman, "RFC v3 Prep Tool Description", | ||
+ | * Hoffman, P. and T. Hansen, " | ||
+ | |||
+ | 6. The Statements of Work | ||
+ | * http:// | ||
- | ==== Other information ==== | ||
- | * [[design: | ||
- | * [[design: | ||
- | * [[design: | ||
- | * [[design: | ||
- | * [[design: | ||
- | * [[design: | ||
==== Format Requirements pulled from RFC 6949 ==== | ==== Format Requirements pulled from RFC 6949 ==== |