- From: Philip Jägenstedt <philipj@opera.com>
- Date: Wed, 28 Aug 2013 13:38:00 +0200
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: public-media-fragment@w3.org
On Tue, Aug 27, 2013 at 4:15 PM, Anne van Kesteren <annevk@annevk.nl> wrote: > I wanted to reuse the generic syntax defined in > http://www.w3.org/TR/media-frags/#media-fragment-syntax for Zip URLs. > However, the processing model is incompatible with supporting a value > that is a byte sequence. So I'll probably end up defining something > like it... In the end though I don't think we want multiple parsers > for that format laying around so some convergence is probably welcome. > Maybe even combine with > http://url.spec.whatwg.org/#application/x-www-form-urlencoded in some > way. Hi Anne, I guess you're talking about the algorithm in <http://www.w3.org/TR/media-frags/#processing-name-value-components>, right? That's my little creation, too bad it doesn't work for you. How about changing it to produce a list of (name, value) tuples where name and value are byte sequences, and then letting MF do UTF-8 conversion while discarding invalid input? In other words, remove step 2b and add it as a separate step. Can you give an example of how a Zip URL will look like? Nothing in <https://gist.github.com/annevk/6174119> looks anything like a MF URL. Philip
Received on Wednesday, 28 August 2013 11:38:28 UTC