Consider referencing codecs parameter in §3.1 (1).

[skynavga]

No description provided.

[nigelmegitt]

We should do this; the section already references to the profile parameter but not codecs. But I think bigger changes are warranted, because the way profile is referenced at the moment leaves a lot unsaid. I propose:

1. Move the reference to the profile parameter in Document Conformance out of bullet 1 and into a new note under the bullet list that says that alongside the MIME type the optional profile and codecs parameters are available to allow processors to make an a priori acceptance or rejection of the document, and, if accepted, the chosen processor profile forms part of the document processing context, and implementations can use this to override the effective processor profile.
2. Clarifying in construct effective processor profile that the use of the profile or codecs parameter can (typically?) result in a document processing context override.

I've left this as a "can" override effective processor profile, for now; perhaps we should discuss if this would be better strengthened to a "should" or even a "must".