[rfc-i] artwork, bitmap, SVG...

[julian.reschke at gmx.de (Julian Reschke)]

On 2014-11-10 19:42, Heather Flanagan (RFC Series Editor) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/8/14 5:06 PM, Paul Hoffman wrote:
>>> The text appears to imply that bitmaps are reasonable artwork.
>>> I thought that it was going to be restricted to ascii art and svg
>>> at this time.  (Yes I realize that one can put a bitmap into an
>>> svg object.)  it might be better to remove some of the "such as
>>> a bitmap" type text.
>> Nothing yet has prohibited bitmap graphics on their own. If you
>> want to do so, please start a thread about saying this in
>> draft-flanagan-rfc-framework. If the RSE agrees, I'll fix this
>> document.
>>
>
> The intent is that in the new format world, artwork may be ASCII or
> SVG.  Support for other formats (e.g., jpg, png) are not on the
> roadmap for the project at this point.
>
> - -Heather

V2 supports bitmap graphics; support for it has been implemented in at 
least two formatter (dunno about the Python one), and it has been used 
for an RFC at least once. So this is a V2 feature; we can deprecate it 
in V3, but let's not pretend it's not there.

For *RFCs*, we can of course state what kinds of media types that are 
accepted, but IMHO that's not a vocabulary question. After all, the V3 
spec also doesn't say that the prose needs to be in English.

Best regards, Julian