Julian Reschke wrote:
- is it intentional that 4.1.3.3 says ``If the value of "type" ends with "+xml" or "/xml"'',
This means the element content is some kind of XML: text/xml, application/xml and any "+xml" type. However, it excludes {text,application}/xml-external-parsed-entity.
Maybe the wording should be � If the value of "type" is a MIME media type whose subtype begins with "xml" or ends with "+xml" �
while 4.1.3.2 used ``If the value of type begins with "text/" or ends with "+xml"''?
This means the element content is some kind of "text- or xml-based content": text/plain, text/xml and any "+xml" type (image/svg+xml, application/xhtml+xml, etc.). However it excludes application/xml, as well as application/xml-external-parsed-entity.
Maybe the wording should be � If the value of type is a MIME media type
whose type is "text" or whose subtype begins with "xml" or ends with
"+xml" �.
Although it depends what's the wanted meaning of the statement: should XML-based contents be provided inline when they are some kind of "human readable text content" (falls in the text/xml "group" as defined in [RFC3023], section 3. XML Media Types), or when they are "text-based" and can therefor be included without further "encoding" (other than "charset recoding" when necessary), which also includes "computer-only content" such as MathML, SVG, CSV, etc. ?
Moreover, the SHOULD in this section might be too strong: if you include XML content, you loose DTD (thus validity) and, more important, entity definitions (such as and others).
Please note that in the two previous wording proposals, � subtype begins with "xml" � might be restricted to � subtype is "xml" or "xml-external-parsed-entity" �.
Robert Sayre wrote:
Yes. In 4.1.3.3, you're supposed to apply them in order. Is that what you find confusing?
I don't think Julian talked about it but, yes it's quite confusing...
Julian Reschke wrote:
- also, if content for +xml SHOULD be local (4.1.3.2), why does 4.1.3.3. point 4, make statements about situations where it comes with @src attribute?
Because in 4.1.3.2 it was a SHOULD, not a MUST, so XML content MAY be provided "outline".
[RFC3023] http://www.ietf.org/rfc/rfc3023.txt
-- Thomas Broyer
