OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bdxr message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [bdxr-comment] Question on SMP CS03 chapter 3.2.1


Hi Philip

I will bring your question up at our TC meeting tomorrow to make we get the input from all the group.

My understanding of HTTP 1.1 is that that any application sending data of type “text” MAY send the optional character set parameter for clarification, and MUST send the character set parameter if the content type uses a character set different than ISO-8859-1. This is by my understanding a clarification of the character set used for the “text” type content (and in the case of SMP, the “xml” subtype) and not a modification of the content type/subtype.

So by my best understanding of HTTP, a “Content-Type” header set to "text/xml; charset=UTF-8" is still having the Content-Type value set to content type/subtype “text/xml” and as such is fully conformant with SMP and with the intention if section 3.2.1.

Best regards,

Kenneth


On 10/25/16, 5:10 AM, "bdxr-comment@lists.oasis-open.org on behalf of philip@helger.com" <bdxr-comment@lists.oasis-open.org on behalf of philip@helger.com> wrote:

    Dear BDXR group!

    Chapter 3.2.1 states that the http header "Content-Type" must have a
    value of "text/xml".
    Do you think a value of "text/xml;charset=UTF-8" (so using additional
    parameters as per RFC 2045, chapter 5.1) is conformant to the
    specification?

    Thanks,
       Philip

    --
    This publicly archived list offers a means to provide input to the
    OASIS Business Document Exchange (BDXR) TC

    In order to verify user consent to the Feedback License terms and
    to minimize spam in the list archive, subscription is required
    before posting.

    Subscribe: bdxr-comment-subscribe@lists.oasis-open.org
    Unsubscribe: bdxr-comment-unsubscribe@lists.oasis-open.org
    List help: bdxr-comment-help@lists.oasis-open.org
    List archive: http://lists.oasis-open.org/archives/bdxr-comment/
    Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
    List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
    Committee: http://www.oasis-open.org/committees/bdxr
    Join OASIS: http://www.oasis-open.org/join/


    Thank you for offering to provide input to the
    OASIS Business Document Exchange (BDXR) TC.



Este correo electrónico y cualquier archivo transmitido con él son propiedad de Efact S.A.C., contiene información confidencial, y están destinados exclusivamente al uso de la persona o entidad a la que van dirigidas. Si usted no es el destinatario señalado, no puede difundir y distribuir o copiar este e-mail. Por favor notifique inmediatamente al remitente por correo electrónico si usted ha recibido este correo electrónico por error, y eliminar este correo electrónico de su sistema. Si usted no es el destinatario, se le notifica que revelar, copiar, distribuir o tomar cualquier acción basada en el contenido de esta información está estrictamente prohibida. This email and any files transmitted with it are the properties of Efact S.A.C., contains confidential information, and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you may not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake, and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]