Re: [Bimi] [rfc-i] SVG P/S Feedback

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 30 August 2020 21:09 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: bimi@ietfa.amsl.com
Delivered-To: bimi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB0AA3A08A6 for <bimi@ietfa.amsl.com>; Sun, 30 Aug 2020 14:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.046
X-Spam-Level:
X-Spam-Status: No, score=-3.046 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.948, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97MFglLsAyTP for <bimi@ietfa.amsl.com>; Sun, 30 Aug 2020 14:09:25 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38C8B3A0895 for <bimi@ietf.org>; Sun, 30 Aug 2020 14:09:25 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id g29so3195488pgl.2 for <bimi@ietf.org>; Sun, 30 Aug 2020 14:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=q6H2jVcqwjmTrgmfDDFBQtT5gyXmFtT9fj/at9G5Dno=; b=SOFQ9JKelQg3tTbyvArc3y7hpT9YQJ/8cX9/0BlS6i5BxAv18xNTw7/MxW3UQYcwz0 UB4hHTKrFaSR75csE2XWyHzvVja1GE62x41yA/S7q/JdXkhAIpTLAAvwkOWAHToddfFY 8WDChHCeDFaOsTSlklX5vFbwD7A4WqOLX8mLv93UBcIrVju8Hh1LOHmru7AzZxeQDTeJ +PAOKWUZzrv2NtO5/qrKGqW7euwu6EfFWdB5Z4lyjldrAGvV3MtUQT0cd36Ujb2dccjX Frq3g66zCIML5p9FTxRYKKp/RzTlewALkc1OMSTmUWfD02lXwwmD9Vp1qladJFYExttJ atiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=q6H2jVcqwjmTrgmfDDFBQtT5gyXmFtT9fj/at9G5Dno=; b=cl7n9KxalQp4sCb77GLIA8pAJ9Li69uWfd5kqnVh86B8pzcjJiU59hfMHbL6Cowrzf ZcZaSrCNktjFj5ZlLQT9XQjHg7qiQQ0hna3FTo9PcOOdX/57G0P8mXKmpTuUS6mDxHO6 /xZl+mz76TUTEpv0wMiapz87SEWgrBe83h/E4gH57u+oApXnJTDxCJWVN8a/l5wdSaWx pdSZf+nXYqwkR+Yl5IL+R7U7XcL77UAvjxkdBN/3C1RvY9yDAuHNuc9XbOA2X1p5r1px aKpjxDn+/Icy9RSdVRqAla9/nm54T89wvj6GJjW7qeKgnMLl28PXtVBZkgI6QWa0EyBL wIPA==
X-Gm-Message-State: AOAM5327SouKmpZ9rTEl47I/ud8xkY3qdbVE/cKqUjR2J9IIDHA+p6dT Y/jWoJvFxH56VfWW3aL3PWTDmGqaIAHmgg==
X-Google-Smtp-Source: ABdhPJx86isGEFPXMZja13V3IWsNcaE1AvWGBGjBat9SyC7j071oclbZtwZ6L+Jx7hwbqfgC2n6S/w==
X-Received: by 2002:a63:2f02:: with SMTP id v2mr1533004pgv.369.1598821764272; Sun, 30 Aug 2020 14:09:24 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id x22sm5637396pfn.41.2020.08.30.14.09.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Aug 2020 14:09:23 -0700 (PDT)
To: Leonard Rosenthol <lrosenth@adobe.com>, Larry Masinter <LMM@acm.org>, "'Brotman, Alex'" <Alex_Brotman@comcast.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Cc: "'BIMI (IETF)'" <bimi@ietf.org>
References: <MN2PR11MB4351CC443B406196C3953D1BF7520@MN2PR11MB4351.namprd11.prod.outlook.com> <70eadfe5-16f6-47d9-4cb8-f4f9bffdd355@gmail.com> <013c01d67d8e$5b952f60$12bf8e20$@acm.org> <f2df89d0-73c5-49b5-c18c-ec0ac16dfa1c@gmail.com> <290BCC09-02FB-4289-9D1A-2FD00B476E78@adobe.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <53a7ca18-792f-ef67-24f9-e84e5e154989@gmail.com>
Date: Mon, 31 Aug 2020 09:09:18 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <290BCC09-02FB-4289-9D1A-2FD00B476E78@adobe.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/xbJWC5Lhx1m_5OeHLNrt3AS1MIg>
Subject: Re: [Bimi] [rfc-i] SVG P/S Feedback
X-BeenThere: bimi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Brand Indicators for Message Identification <bimi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bimi>, <mailto:bimi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bimi/>
List-Post: <mailto:bimi@ietf.org>
List-Help: <mailto:bimi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bimi>, <mailto:bimi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Aug 2020 21:09:27 -0000

On 31-Aug-20 04:12, Leonard Rosenthol wrote:
> Brian - but what you describe below is a tooling problem not a technology or format issue.

IMHO the underlying problem is that SVG allows multiple ways of representing the same image, and a subsidiary problem is that it allows positions to be represented as real numbers. The SVG spec says:
"Unless stated otherwise, numeric values in SVG attributes and in properties that are defined to have an effect on SVG elements must support at least all finite single-precision values supported by the host architecture."
In other words, the precision of positions is host-dependent. I don't know enough about PDF to know how that affects the conversion algorithm, but I suspect it means that...

> There are ways in which all of the SVG semantics - or even the entire SVG itself(!) 

... only embedding the SVG itself would be guaranteed to round-trip in all cases. Since that is exactly what we do in xml2rfcV3, I don't see what we'd gain by doing it in PDF/A instead.

> - could be included in the PDF/A file and round-tripped with correct fidelity (or even 100% identical bits).

Who is the arbiter of "correct fidelity"? The judge and jury in a patent infringement or copyright case? The only safe standard is "identical bits" or at least "identical string of UTF-8 characters". We've relied on "identical string of ASCII characters" for many years.

> Let's agree on what the goal is, come up with a standard that specifies how to achieve that, AND THEN we can get tools to comply.

Sure. We'd need to start with some canonicalization rules for SVG. We need to look again at RFC7996 in any case. But I don't think that relying on host representation of real numbers is ever going to be OK. (Is there a reason that SVG didn't use a host-independent formulation for its statement about precision?)

    Brian

> 
> Leonard
> 
> On 8/29/20, 1:04 AM, "rfc-interest on behalf of Brian E Carpenter" <rfc-interest-bounces@rfc-editor.org on behalf of brian.e.carpenter@gmail.com> wrote:
> 
>     Larry,
> 
>     On 29-Aug-20 10:55, Larry Masinter wrote:
>     > One of the functional requirements for SVG illustrations is that when
>     > converted to PDF/A that the result is "as good as it gets" so the authors
>     > don't rely on embedded animations or videos to explain the protocol they are
>     > describing.
>     > 
>     > What if you did a round trip   SVG -> PDF/A -> SVG. I think it's possible to
>     > insure that doing so is idempotent (if it isn't now).
> 
>     Only if you had a round trip tool that magically preserves the SVG dialect
>     in use. I just round-tripped a test file using https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconvertio.co%2F&amp;data=02%7C01%7Clrosenth%40adobe.com%7Cf8108cd02b334c72415d08d84bd8f976%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637342742565624784&amp;sdata=1m8XMdcHkgmgUCf%2B4%2F0wEOI37suRSejjVpsbqqsHXI4%3D&amp;reserved=0.
>     The PDF and the round-tripped SVG *look* the same as the original, but the
>     actual content of the SVG file is totally different, and fails svgcheck, so
>     is no longer conformant with RFC7996. The converter just happens to choose
>     a different way of representing the same image, since SVG is so versatile.
> 
>     The converter also messed up the scalability of the image, which is really
>     annoying if you want the image to be viewable on a tiny screen.
> 
>     Now I'll round-trip it a second time... once again, the input and output
>     SVG files are different, although only in a few places. So even the
>     conversion tools at convertio.co can't achieve idempotency with the SVG
>     that they themselves generate.
> 
>     (For the record, convertio.co doesn't claim to be PDF/A conformant,
>     but I think that's beside the point here.)
> 
>        Brian
> 
> 
>     _______________________________________________
>     rfc-interest mailing list
>     rfc-interest@rfc-editor.org
>     https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fmailman%2Flistinfo%2Frfc-interest&amp;data=02%7C01%7Clrosenth%40adobe.com%7Cf8108cd02b334c72415d08d84bd8f976%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637342742565624784&amp;sdata=kN8z9faPWo3aCpTjdQNfyHn0W%2BelVT7%2BTdIW45CBtl8%3D&amp;reserved=0
>