Moving forward on ISSUE-19


I've drafted what I think the first steps towards resolving ISSUE-19  
should look like:


The main changes are:

* I've split the syntax into two levels: (1) the general name-value  
structure (namevalues production) and (2) the dimension syntaxes,  
operating on the Unicode strings extracted from the first pass. I've also  
been clear(er) on what components are, and note that as a result the URI  
spec requires percent-decoding to happen after parsing out the names and  

* I've reworked the section "Processing name-value components" and  
"Processing name-value lists" and made them normative by moving them into  
section 5. They still contain algorithms, but they are much smaller than  
before. If anyone can express the same thing in prose, that would be fine.

* I've removed the production rules that are not used and were in any case  
nowhere in the normative part of the spec before I began editing. This  
includes, notably, the mediasegment production.

What's left to do:

* The dimension sections need to be cleaned up and be given better hooks  
for section "Processing name-value lists", so that it is abundantly clear  
what happens with e.g. #t=10&t=20.

* There needs to be stronger language about validity. We should state that  
any unrecognized names or values are invalid, as is repeating the same  
dimension twice.

To make it simpler to review the changes, I've also prepared a set of  
patches that apply to WWW/2008/WebVideo/Fragments/WD-media-fragments-spec  
in CVS.


0005, 0007 and 0008 are the most important, the others are fixing small  

Please take the time to review this so that we can perhaps finally move on  
with ISSUE-19.

Philip Jägenstedt
Core Developer
Opera Software

Received on Thursday, 4 November 2010 10:01:18 UTC