XML usage in OPC

[Chris Rae]

Let’s chat in Japan, but my thoughts on these:

Rule #1: I think you might be right, there’s no value to prohibiting this in OPC
Rule #2: I think you’re right here too, although we should maybe have an informative note recommending against use of DTDs
Rule #3: ‘d agree that it’s up to the consuming specification to determine whether MCE is used in their markup. The only wrinkle in this is whether MCE is to be permitted inside the OPC portions of the package itself (rels files etc) – this needs some more thinking
Rule #4: I think this bullet should remain but should be better scoped

I’m not sure I completely understand rule #5. I’d rather assumed these were prohibited by XML itself.

Chris


From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA Makoto
Sent: 14 September 2014 15:11
To: SC34
Subject: Re: XML usage in OPC

We can even drop the first two bullets.  The first one disallows non-Unicode encodings,
while the second disallows the use of DTDs.  Although I understand the desire to
disallow them, is OPC the right place for introducing such rules?  I do not believe
that OPC processing is hampered by them.

Regards,
Makoto


2014-09-15 7:02 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp<mailto:eb2m-mrt at asahi-net.or.jp>>:
Folks,

There are five bullets in "XML Usage" in 29500-2.  The
last three are questionable.

The third bullet makes the MCE processing mandatory.  I
am not sure if it is a good idea.  Why should OPC force
the use of MCE?

> If the XML content contains the Markup Compatibility
> namespace, as described in Part 3, it shall be
> processed by the package implementer to remove Markup
> Compatibility elements and attributes, ignorable
> namespace declarations, and ignored elements and
> attributes before applying subsequent validation
> rules. [M1.19]

The fourth bullet mandates validaity against "the
corresponding XSD schema defined in this Open Packaging
specification".  This appears to disallow the use of
XSDs defined in Part 1!  What is more, XSD-less
documents (e.g, RDF) are disallowed.  I do not think
that this makes sense.

> XML content shall be valid against the corresponding
> XSD schema defined in this Open Packaging
> specification. In particular, the XML content shall
> not contain elements or attributes drawn from
> namespaces that are not explicitly defined in the
> corresponding XSD unless the XSD allows elements or
> attributes drawn from any namespace to be present in
> particular locations in the XML markup. Package
> implementers shall enforce this requirement upon
> creation and retrieval of the XML content. [M1.20]

The last bullet disallows the use of the prefix "xml"
and "xsi" unless the XSD schema for the XML content
explicitly allows them.  Thus, XSD-less XML contents
cannot use them.

> XML content shall not contain elements or attributes
> drawn from “xml” or “xsi” namespaces unless they
> are explicitly defined in the XSD schema or by other
> means described in this Open Packaging
> specification. Package implementers shall enforce
> this requirement upon creation and retrieval of the
> XML content. [M1.21]

--
Regards,
Makoto



--

Praying for the victims of the Japan Tohoku earthquake

Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20140915/796d6031/attachment.html>