DR 10-0026 ? OPC: dc:creator only once within a coreProperties element

Jesper Lund Stocholm jesper.stocholm at ciber.dk
Fri Nov 12 10:41:01 CET 2010

Hello all,

This is to me more an "internationalization" issue than a "new feature"
issue. OOXML should in its base schemas be suitable for use-cases like
these from users in East-Asia.

There are two issues at stake here:

1. Will future applications support this?
2. Will existing applications crash due to this?

The first is impossible to predict - but the latter is a rather trivial
task to test.

The schemas-changes should be relatively benign and I am alongside
Murata-san here - let's test (or inquiry makers of-) existing
applications and their behaviour when encountering documents with e.g.
multiple cd:creator elements.

Med venlig hilsen / Best regards

Jesper Lund Stocholm

CIBER Danmark A/S
Mobil: +45 3094 5570
Email: jesper.stocholm at ciber.dk

materials in this electronic transmission (including attachments) may be
subject to attorney-client or work product privilege, may be private and
confidential and are the property of the sender. The information
contained is intended only for the named addressee(s) and should not be
considered evidence of intent to be bound to any agreement. The taking
of any action in reliance on the contents is strictly prohibited. If you
are not the intended recipient of this message, please immediately
notify the sender and promptly delete this message.

> -----Original Message-----
> From: MURATA Makoto (FAMILY Given) [mailto:eb2m-mrt at asahi-net.or.jp]
> Sent: Friday, November 12, 2010 5:21 AM
> To: e-SC34-WG4 at ecma-international.org
> Subject: Re: DR 10-0026 ? OPC: dc:creator only once within a
> element
> > http://cid-
> c8ba0861dc5e4adc.office.live.com/view.aspx/Public%20Documen
> > ts/2010/DR-10-0026.docx
> >
> > This DR concerns the fact that there is no ability to specify
> elements twice (once for Kanji; once for Kana).
> This issue is common to EPUB, OOXML, and ODF (even ODF 1.2).  I would
> to have the same solution for all of them, which is to allow more than
> dc:creator element (for example) having diffent values for @xml:lang.
> > This is a useful concern but I don't think that the way to add this
> > feature is to modify the base standard and risk breaking existing
> applications.
> Some changes in our CORs theoretically destroy some implementations.
> Let alone AMDs.  In this case, will some real implementations really
> have troubles?   If not, I would like to use the simplest solution
> common to all relevant specifications.
> Cheers,
> Makoto

More information about the sc34wg4 mailing list