https://bz.apache.org/bugzilla/show_bug.cgi?id=57699

--- Comment #22 from Asbjørn S. <[email protected]> ---
(In reply to PJ Fanning from comment #20)
> Asbjorn - supporting strict ooxml strict format is a massive task. poi-ooxml
> uses generated classes based on the OOXML Transitional XSDs. Generating the
> same classes for OOXML Strict XSDs and then having the all the XSSF classes
> or variants of them work with the OOXML Strict generated classes would be
> months of work and noone is volunteering to do it.
> 
> The best I can offer is https://github.com/pjfanning/excel-streaming-reader
> can read OOXML Strict files because it does not use the XSDs - but its API
> support is more limited than POI.
> 
> I do not have Excel installed but use https://onedrive.live.com/ to work
> with excel files. This hosted version of Excel doesn't even offer the
> ability to save in OOXML Strict format - only supports OOXML Transitional.
> As far as I can see OOXML Strict files are rare compared to OOXML
> Transitional files.


The lack of software support for conversion to and validation of OOXML Strict,
might inform us to adopt OOXML Transitional for long-term preservation of
archived spreadsheets, but it is not ideal, because we expect OOXML
Transitional to be replaced by OOXML Strict in the future, hence we will have
to migrate any already submitted OOXML Transitional spreadsheets. The question
is really, will OOXML Strict ever replace OOXML Transitional!? As you say,
OOXML Strict files are very rare today and software support both from MS and
open-source community is insufficient.

Having Apache POI support conversion and validation would have tremendous
impact from an archival point of view. I understand it is a huge task and no
one is voluntering. I wanted to share our usercase, however, so the community
will know demand exists, however marginal it might be.

-- 
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]

Reply via email to