18575 2012-08-15 13:56:18 +0000 Section 2. Source Buffer Model should be non-normative 2012-12-18 18:58:13 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified All All RESOLVED FIXED tpac2012 P2 normal --- 1 philipj acolwell acolwell mike public-html-media public-html-bugzilla oldest_to_newest 72201 0 philipj 2012-08-15 13:56:18 +0000 http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#source-buffer-model Some of the things mentioned in this section look like normative requirements since the magic words may/should/must appear and there is language like "An exception is thrown if the application tries to update the attribute when only part of a media segment has been appended." To remove any doubt, the entire section should be marked as non-normative. (Not hypothetical, I was going to file a bug that it didn't say which exception to throw, before I realized it wasn't intended to be normative.) 72393 1 acolwell 2012-08-17 23:29:20 +0000 (In reply to comment #0) > http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#source-buffer-model > > Some of the things mentioned in this section look like normative requirements > since the magic words may/should/must appear and there is language like "An > exception is thrown if the application tries to update the attribute when only > part of a media segment has been appended." > > To remove any doubt, the entire section should be marked as non-normative. > > (Not hypothetical, I was going to file a bug that it didn't say which exception > to throw, before I realized it wasn't intended to be normative.) Hmm... Many of these sections were intended to convey requirements which is why the musts are in there. Perhaps this means that I should update the algorithm text to make sure these rules are enforced so the 2.x sections aren't necessary? I'd hate for a large part of the spec to become a green box. 72428 2 philipj 2012-08-20 09:52:29 +0000 Yes, I think it would be better if all the normative requirements are expressed in the algorithms, and that a high-level overview is explicitly non-normative. As it is now, some requirements are expressed twice and may not align exactly. It's of course possible to interleave the normative and the non-normative, if that would make for better reading. 76866 3 adrianba 2012-10-22 01:07:05 +0000 Assigned to Aaron. This represents a large reorganization of the content. Need to make a proposal and then discuss. Added tpac2012 whiteboard tag. 80369 4 acolwell 2012-12-18 18:58:13 +0000 I believe most of the redundant and non-normative text has been removed by the following changes. http://dvcs.w3.org/hg/html-media/rev/e1c91093dfdc http://dvcs.w3.org/hg/html-media/rev/ee6e8ae9337c http://dvcs.w3.org/hg/html-media/rev/43be42e69533 Some non-normative text still remains, but it is clearly marked as such. I also believe the various overlap sections, though under specified, now contain normative statements. These sections will include more detail in the future, but I believe they roughly capture the intended behavior that is required for implementation.