[rfc-i] [IAB] draft-iab-rfcv3-preptool-01, "5. What the v3 Prep Tool Does"

julian.reschke at gmx.de (Julian Reschke) Mon, 14 March 2016 18:38 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Mon, 14 Mar 2016 19:38:35 +0100
Subject: [rfc-i] [IAB] draft-iab-rfcv3-preptool-01, "5. What the v3 Prep Tool Does"
In-Reply-To: <4B994C8E-7DBC-41BC-9000-C8781A429D90@cisco.com>
References: <56E6A9F9.4010302@gmx.de> <4B994C8E-7DBC-41BC-9000-C8781A429D90@cisco.com>
Message-ID: <56E7052B.5030006@gmx.de>

On 2016-03-14 19:20, Joe Hildebrand (jhildebr) wrote:
> On 3/14/16, 6:09 AM, "IAB on behalf of Julian Reschke" <iab-bounces at iab.org on behalf of julian.reschke at gmx.de> wrote:
>
>
>
>> <http://greenbytes.de/tech/webdav/draft-iab-rfcv3-preptool-01.html#rfc.section.5>:
>>
>>> 15. Add a ?slugifiedName? attribute to each <name> element that does not contain one; replace the attribute if it contains a value that begins with ?n-?.
>>
>> a) Shouldn't this say "replace the attribute in any case, no matter what
>> it contains"? Or what is the expected behavior when it is present but
>> does not start with "n-"?
>
> That would have been fine with me, but it's not worth the change at this point.

OK; just trying to understand whether I missed something.

>> b) What's the use of a slugifiedName when the parent element has an
>> anchor attribute?
>
> Nothing I can think of.  I would have also been fine with the preptool adding an "n-" anchor if one doesn't exist, and getting rid of sluggifiedName.  Actually, I could probably be talked into that now as a simplifying change (modulo whatever we learn from prototyping), if you think it's really important.

That would work for me as well...

Best regards, Julian