https://issues.apache.org/bugzilla/show_bug.cgi?id=56205
Bug ID: 56205
Summary: [PATCH] Upgrade OOXML schema to 3rd edition
(transitional)
Product: POI
Version: 3.11-dev
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: POI Overall
Assignee: [email protected]
Reporter: [email protected]
Created attachment 31358
--> https://issues.apache.org/bugzilla/attachment.cgi?id=31358&action=edit
[PATCH] Upgrade OOXML schema to 3rd edition (transitional)
The currently used OOXML schema is a bit outdated and therefore hasn't got a
few of the recently added Office features (e.g. XSSF sheetProtection is missing
a few attributes).
The ECMA site [1] has already provided a 4th edition of the schemas.
After fiddling around a bit with the schemas, I think it's ok to use the 3rd
edition of the transitional schema, as its main incompatibility (to the 1st
edition) are length and percent definitions. The 4th edition would cause much
more changes in the current POI codebase.
Although the testcases run through with some modifications, I'm not sure about
the impact, which this patch would have on users code, especially when the
xmlbeans classes are used directly.
Therefore I'd like to discuss in this entry, if features which aren't covered
by the 1st edition schema, should be created dynamically without a backing
schema or if it's ok to potentially break user code which works with the
internal xml representation.
[1] http://www.ecma-international.org/publications/standards/Ecma-376.htm
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
