Re: Correction: Request for Proposal: RFC Format CSS Design

Joe Hildebrand <hildjj@cursive.net> Fri, 22 July 2016 19:34 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Correction: Request for Proposal: RFC Format CSS Design
From: Joe Hildebrand <hildjj@cursive.net>
In-Reply-To: <CAPt1N1nwkGyx2z_e9hnarpHjrsMYBYwv00pJYsVFMtJDfAPF8A@mail.gmail.com>
Date: Fri, 22 Jul 2016 21:33:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F15019E-9E41-4807-BD63-AF7B807F0E2C@cursive.net>
References: <20160722100616.12323.78312.idtracker@ietfa.amsl.com> <CAPt1N1nwkGyx2z_e9hnarpHjrsMYBYwv00pJYsVFMtJDfAPF8A@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BgZ8uNZb2J8H4P__MzldAHICCO4>
Cc: ietf <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Precedence: list

The intent is that the HTML will be responsive. The PDF will look like the HTML, responsive to an A4 page size with margins set such that it will print adequately on US Letter page size as well.

If you want to read on your phone, and don't have some sort of fancy PDF reader there, use the HTML.


> On Jul 22, 2016, at 1:01 PM, Ted Lemon <mellon@fugue.com> wrote:
> 
> How can it be responsive if the PDF and HTML are to look the same?  On a phone screen that would be to small to read!
> 
> 
> On Jul 22, 2016 12:06, "IETF Administrative Director" <iad@ietf.org> wrote:
> Correction
> The previous announcement contained an error in the list of
> Deliverables.  Below is the corrected list.
> 
> +++++++++++++++++++++++++++++++++++++++++++++
> The IETF Administrative Oversight Committee (IAOC), on behalf of the
> IETF, announces this Request for Proposals for the development of a
> RFC Format CSS Design.  The successful bidder will enter into a
> contract with the Internet Society.
> 
> The RFC Editor plans to produce a canonical RFC document in XML
> using the xml2rfc v3 grammar, and to publish the RFC in several
> Publication Formats as defined in RFC6949.  In particular, there
> will be an HTML and PDF output that will support many new features
> within the documents, including SVG line art.  This project will
> result in a CSS file that will reflect visually pleasing,
> accessible, and responsive design.
> 
> Deliverables
> 
> •       Provide a responsive design CSS for future RFCs following the
> guidance in draft-iab-rfc-css
> 
> •       The PDF and HTML output must look as similar as possible
> 
> •       All of the HTML features  that have been called out in
> draft-iab-html-rfc need to be in place in the CSS
> 
> The RFP can be found at: <https://iaoc.ietf.org/rfps.html>.
> 
> Proposals must be received via email at tmc@ietf-bids.org no later
> than September 9, 2016.  All questions, inquiries must be submitted
> by August 8, 2016.  Responses to questions and inquiries shall be
> posted online at:  <https://iaoc.ietf.org/rfps.html> by August 15,
> 2016.
> 
> The point of contact regarding this RFP is the IETF Administrative
> Director, Ray Pelletier, iad@ietf.org.
> 
> Ray Pelletier
> IAD
> 

-- 
Joe Hildebrand

Re: Correction: Request for Proposal: RFC Format … Joe Hildebrand
Correction: Request for Proposal: RFC Format CSS … IETF Administrative Director
Re: Correction: Request for Proposal: RFC Format … Yoav Nir
Re: Correction: Request for Proposal: RFC Format … John Levine
Re: Correction: Request for Proposal: RFC Format … Ted Lemon