村田真のXMLブログ
日本人で唯一W3CのXMLワーキンググループに参加しXMLの標準化プロセスに携わったXMLの生みの親、村田真さんのブログです。
OOXMLへの投票私案
まだまだ、OOXML Part 1とスキーマぐらいしか見ていないので、もっとコメントすべきところは多いと思う。追加すべきことを指摘していただけるとありがたい。
なお、ODFとOOXMLの関係についてはまったく触れていない。これは、技術委員会で議論すべきことであるし、他の人より適切なコメントが私に出せるかどうかも分からない。私だけに言えることがあるとしたら、ODF規格書の品質がきわめて低いこと、過去の文書交換フォーマットはすべて無残に失敗してきたことの二つだろう。
1. Major Technical
- MSXML can handle the W3C XML Schema version of the OOXML schemas,
but we find no other validators can handle it. Reorganize it so that
it can be handled by Xerces-J and MSV at least.
- The RELAX NG version of the OOXML schemas are incorrect. Replace it
by the upcoming proposal from the Japanese member body for SC34.
- Unless the "pack" URI scheme is endorsed by IETF, it should be
dropped.
- OPC, without interleaving, should become an independent standard.
- Non-ASCII characters should be allowed as part names without relying
on %HH.
- The Custom XML Mappings Part of the SpreadsheetML should allow the
use of RELAX NG. At present, it is restricted to W3C XML Schema.
- Markup Compatibility, without PreserveELements and
PreserveAttributes, should become an independent standard.
- Application Conformance should be dropped. Better leave users make
the call. Moreover, by dropping application conformance, it becomes
obvious that implementations are allowed to ignore legacy features
and so forth.
- WordProcessingML should become a single part of the OOXML standard,
and document conformance for WordProcessingML should be clearly
defined.
- PresentationML should become a single part of this standard, and
document conformance for PresentationML should be clearly defined.
- SpreadsheetML should become a single part of this standard, and
document conformance for SpreadsheetML should be clearly defined.
- Is it possible to use VML and Math without standardizing them as
part of OOXML? Note that macros are already used without
standardization and the namespace of VML is Microsoft-specific.
- DrawingML should be devided into more than one sub-language. (See
http://www.asahi-net.or.jp/~eb2m-mrt/ooxml/dependencies.html.)
One possiblity is to introduce one sub-language per namespace. The
namespaces are:
http://schemas.openxmlformats.org/drawingml/2006/chart
http://schemas.openxmlformats.org/drawingml/2006/chartDrawing
http://schemas.openxmlformats.org/drawingml/2006/compatibility
http://schemas.openxmlformats.org/drawingml/2006/diagram
http://schemas.openxmlformats.org/drawingml/2006/lockedCanvas
http://schemas.openxmlformats.org/drawingml/2006/main
http://schemas.openxmlformats.org/drawingml/2006/picture
http://schemas.openxmlformats.org/drawingml/2006/spreadsheetDrawing
http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawing
2. Major Editorial
- Do not use "may not".
- Do not introduce yet another definition of the word "type".
We already have at least three (XML, W3C XML Schema, and MIME).
3. Minor Technical
- Why XSLT transformation is optional? Why it is applied only on save
(not on read)?
- Are arbitrary binary data allowed as custom property parts? If so,
why is the content type fixed?
投稿者: 村田 真 ／ 日時: 2007.06.22
トラックバック
このエントリーのトラックバックURL:
http://blog.xmlmaster.org/mta/mt-tb.cgi/25
関連情報
<< 前回の記事：「SC34の参加国がまた増えた」
>> 次の記事：「OOXML Part 2 (Open Packaging Conventions)についてのコメント私案」
