Rahul Gupta
Rahul Gupta
> Cdn-Loop is... 1. Is not a Structured Header. 2. Does not contain an example of repetition of the same CDN in the list, nor does it specify how to...
Neither am I saying that. But there is nothing to specify how the repetition should be handled either?
Yes. Is that not odd? Because, it is semantically ambiguous when you add in different parameters.
OK! I was thinking of cases where you would need to list a particular item at most once (though I did not imply combining condiments with your hotdogs was the...
Exactly that! Something like: > "Members of a List are allowed to repeat. A structured field definition MUST specify how such repetitions are to be handled." or, to exclude the...
> A list is, well, a list. The default expectation is that repetitions are allowed. This was not obvious to me (because of parameters being involved, this is not an...
> If you don't want repetitions in your header, then you need to say something. Maybe we can say that explicitly (not having to co-relate with Section 2 to interpret...
> it seems you're ascribing some special meaning to them What I am saying is that it is possible to assign special meaning to repeated items when including parameters (the...
Tommy, as the document shepherd for this spec has already noted my objection. So yes, we can close this issue!
Excuse my ignorance, but I do not understand how this is a breaking change? Even with this feature, all existing fields that parse successfully will continue to parse exactly as...