[rfc-i] v3imp #5 Tag figs with filenames, Internet message data

Julian Reschke julian.reschke at gmx.de
Fri Jan 23 03:14:35 PST 2015

On 2015-01-23 10:05, Sean Leonard wrote:
> Improvement Need
> #5 Tag figs with filenames, Internet message data
> This improvement calls for tagging figs with filenames and Internet
> message data. The term "figs" is meant to include <figure> as well as
> other non-spec-text data, including what is currently encompassed by
> <sourcecode>.
> I note that <sourcecode> is a stab in the right direction.
> Many standards include figures that are better operated upon as files,
> such as ASN.1 modules or Python source code. A big problem historically
> has been that these data have been split apart by pagination and spacing
> artifacts. When stitching them back together, transformation
> (copy-and-paste type) errors have occurred with bad results.
> It makes sense to tag this data with filenames, so that users of the
> standard can extract the file information as-is and operate upon it.
> For that matter, I also want to be able to tag a figure or blob of code
> with a media type (*and* parameters--yes, we need parameters). Calling
> something "foo.js" is one thing; labeling it as "application/javascript"
> or "application/json" is more well-defined.
> ...

I note that we've had artwork/@name and artwork/@type for ages; what's 

Best regards, Julian

More information about the rfc-interest mailing list