[rfc-i] [EXTERNAL]Re: [Bimi] SVG P/S Feedback
Kirk.Hall at entrustdatacard.com
Tue Sep 1 16:14:27 PDT 2020
Here is input from Serge Mister of Entrust Datacard.
The mention of fonts as a risk is interesting (I'd flagged missing-glyph as a risk for similar reasons; but it sounds like some renderers ignore the glyphs even if they are present?). Personally I've had trouble generating SVGs (for work illustrations) that use fonts because the same fonts aren't available on the different platforms (e.g. Linux and Windows), so I agree that in practice logo designers would want to convert their text to curves (both to avoid rendering issues and to save space).
The SVG native effort does sound like it has similar goals. Just based on reading the introduction it does sound like it would be nice to combine the efforts. I wonder if there would be any funding (I'm thinking from BIMI) for adding support for the output format to InkScape. That would go a ways to helping with adoption. I don't know what it would cost.
From: bimi <bimi-bounces at ietf.org> On Behalf Of Brian E Carpenter
Sent: Friday, August 28, 2020 3:26 PM
To: Brotman, Alex <Alex_Brotman at comcast.com>; rfc-interest at rfc-editor.org
Cc: BIMI (IETF) (bimi at ietf.org) <bimi at ietf.org>
Subject: [EXTERNAL]Re: [Bimi] [rfc-i] SVG P/S Feedback
I have to say that the RFC7996 profile of SVG Tiny is, in my experience, a problem rather than a solution. It was designed with the best possible intentions and some of the rules (like no colour, no greyscale, and no external references) are appropriate for the RFC context, but trying to generate conformant SVG with popular and widespread drawing tools is almost impossible**.
** Even with dia, which is a pretty minimal tool, some post-processing of the SVG may be needed. Producing my own recent effort (https://www.ietf.org/id/draft-carpenter-eligibility-expand-04.html#section-appendix.a) was quite a saga.
On 29-Aug-20 00:57, Brotman, Alex wrote:
> [Apologies for the cross-posting]
> As part of a separate project, we wanted to create a smaller SVG profile. It is based on SVG Tiny 1.2, with several components removed. The goal is to try to keep the document self-contained, remove animations, and generally more portable and secure (hence P/S). Personally, I've been curious if we should be trying to create a new baseProfile as we've specified, given that it may behoove a developer to only target this subset of Tiny features, reducing footprint and attack surface. We also welcome feedback about the text and font elements that we've permitted in the draft, and their security implications.
> We thank you for any advice or feedback you can provide.
>  https://datatracker.ietf.org/doc/draft-svg-tiny-ps-abrotman/
> Alex Brotman
> Sr. Engineer, Anti-Abuse & Messaging Policy Comcast
> rfc-interest mailing list
> rfc-interest at rfc-editor.org<mailto:rfc-interest at rfc-editor.org>
bimi mailing list
bimi at ietf.org<mailto:bimi at ietf.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rfc-interest