[rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elements and Attributes Deprecated from v2"

julian.reschke at gmx.de (Julian Reschke) Tue, 15 March 2016 22:29 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 15 Mar 2016 23:29:16 +0100
Subject: [rfc-i] [IAB] draft-iab-xml2rfc-03, "1.3.3 Elements and Attributes Deprecated from v2"
In-Reply-To: <F1280AEF-7ACA-43A9-8814-B3F9B00E3868@cisco.com>
References: <56E85AA1.2060002@gmx.de> <01B2F0F9-1664-43D9-B95A-883AC38B973F@cisco.com> <56E888BB.9050701@gmx.de> <F1280AEF-7ACA-43A9-8814-B3F9B00E3868@cisco.com>
Message-ID: <56E88CBC.1040708@gmx.de>

On 2016-03-15 23:20, Joe Hildebrand (jhildebr) wrote:
> On 3/15/16, 4:12 PM, "Julian Reschke" <julian.reschke at gmx.de> wrote:
>
>
>
>>> I think the intent is that anytime there is text inside the xref, it acts like format="none", and the format attribute would be ignored.
>>
>> Well, that would be a breaking change from v2!
>
> The last time we talked about this, nobody wanted to specify what happens if there is text inside the xref, and the format isn't "none".  If we want to specify these, by, for example, calling all of those an error, I'd be fine with it.

I agree nobody had the energy to research it and to write it down. But 
it doesn't mean it isn't used, and doesn't have use cases.

I'll start by counting how much it is used in AUTH48 XML.

Best regards, Julian