- From: Jack Jansen <Jack.Jansen@cwi.nl>
- Date: Fri, 18 Sep 2009 02:19:27 +0200
- To: Raphaël Troncy <Raphael.Troncy@cwi.nl>
- Cc: Media Fragment <public-media-fragment@w3.org>, Yves Lafon <ylafon@w3.org>
On 17 sep 2009, at 13:42, Raphaël Troncy wrote: > All, > > The minutes of today's F2F meeting are available for review at http://www.w3.org/2009/09/17-mediafrag-minutes.html > > Jack (and Yves), I encourage you to go through it and let us know if > you have any concerns with the taken resolution. I agree with the decisions taken. I do share Conrad's view that (at least in the IRC) I didn't see this distinction on using the one for transcoding, the other for non- transcoding, though, but maybe that was in the audio only? Here's a wild idea that just came up (note: it's two in the morning, and I've had a fair share of alcoholic beverages, after a long day of meetings, so I may not agree with this idea myself tomorrow morning:-): could we use profiles to allow implementations to adhere only to the # or the ? or both? What I mean is that we would define three profiles: - MF fragment profile: the whole spec, but only insofar as it uses # fragment addressing; - MF query profile: ditto, but for ? query addressing; and - MF full profile: both of them. That way, if it turns out that people out there like one scheme but not the other they can adhere to one of the partial profiles. In addition, if it turns out that the whole world prefers one method over the other, for MF 2.0 we can deprecate the other one and have it be phased out. It does however require a bit of extra work on our side, because (especially on the protocol side) we have to flag each bit of prose as to which of the profiles it is valid for. -- Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman
Received on Friday, 18 September 2009 00:20:15 UTC