My proposals: content type and media ypest

[MURATA Makoto]

Here are my two cents.

First, which term?
Proposal: Use "media type" except for existing element/attribute names.

Second, which RFC should we reference?
Proposal:  RFC 7231 rather than RFC 2616.   Certainly,
RFC 7231 depends on other RFCs even for the definition
of media types, but we do not have to worry about that.

Third, which regular expression?
Proposal:

Here is a relevant part of opc-contentTypes.xsd.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE xs:schema
[
<!ENTITY X "[\p{IsBasicLatin}-[\p{Cc}\(\)<>@
,;:\\"/\[\]\?=\{\}\s\t]]">
<!ENTITY Y
"[\p{IsBasicLatin}-[\p{Cc}\\"]]|[\p{IsLatin-1Supplement}\t]">
]>
<xs:schema xmlns="
http://schemas.openxmlformats.org/package/2006/content-types"
  xmlns:xs="http://www.w3.org/2001/XMLSchema"
  targetNamespace="
http://schemas.openxmlformats.org/package/2006/content-types"
  elementFormDefault="qualified" attributeFormDefault="unqualified"
blockDefault="#all">

...

  <xs:simpleType name="ST_ContentType">
    <xs:restriction base="xs:string">
      <xs:pattern

value="$X+/$X+(\s*;\s*($X+=(($X+)|("(&Y;|(\\[\p{IsBasicLatin}\p{IsLatin-1Supplement}))*"))))*"/>
    </xs:restriction>
  </xs:simpleType>

...
</xs:schema>


Regards,


Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20150221/5039b22a/attachment.html>