ISSUE-19 (parsing): Parsing must be defined normatively in the MF spec itself

• From: Media Fragments Working Group Issue Tracker <sysbot+tracker@w3.org>
• Date: Mon, 05 Jul 2010 08:50:31 +0000
• To: public-media-fragment@w3.org
• Message-Id: <E1OVhNn-00020S-44@stu.w3.org>

ISSUE-19 (parsing): Parsing must be defined normatively in the MF spec itself

http://www.w3.org/2008/WebVideo/Fragments/tracker/issues/19

Raised by: Philip Jägenstedt
On product: 

MF parsing must be defined normatively in the MF spec itself, meeting these conditions:

1. should handle all valid productions of the ABNF syntax correctly and, where necessary, input which is not valid per the syntax.

2. must be forward-compatible, so that future extensions to MF do not break existing MF parsers. (Compare to how new HTML elements and attributes or CSS properties degrade in implementations that don't understand them.)

3. should match as closely as possible how query components on the form a=1&b=2 are parsed by existing server-side software (e.g. ASP, PHP, JSP, Perl CGI)

Received on Monday, 5 July 2010 08:50:32 UTC