[rfc-i] draft-hoffman-rfcformat-canon-others-03.txt

Tim Bray tbray at textuality.com
Fri Jul 13 09:57:19 PDT 2012


What Joe said.  This image management stuff should be part of the
publisher's job, not the author's.  As long as the author puts graphics
where the RFC editor can find them, good enough.
On Jul 13, 2012 9:41 AM, "Joe Hildebrand (jhildebr)" <jhildebr at cisco.com>
wrote:

>
> On 7/13/12 9:37 AM, "Iljitsch van Beijnum" <iljitsch at muada.com> wrote:
>
> >On 13 Jul 2012, at 17:00 , Paul Hoffman wrote:
> >
> >>> I don't like the idea of including base64 binary information in the
> >>>HTML.
> >
> >> Then don't do it. The only time you need to actually include it is when
> >>you submit the draft for publication.
> >
> >Then all the authors still need to be able to create this format, which
> >is just another hoop to jump through. If we don't need this later than we
> >don't need it at submission time.
>
> The RFC Editor could choose to accept submissions that did not have the
> images inlined yet, and could perform the insertions for you.  That way,
> the URLs would only need to be stable for a MUCH shorter period.
>
> --
> Joe Hildebrand
>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20120713/8b431985/attachment.htm>


More information about the rfc-interest mailing list