incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: [PROPOSAL] [DISCUSSION] Corinthia Abstract
Date Sat, 29 Nov 2014 19:55:50 GMT
I put together an abstract in the Corinthia Podling Proposal.  It is a bit lengthy and requires
review that it captures the essence of what Corinthia is for without over/under-stepping.

Here is the text also added to <>,

Corinthia converts among document file formats via transformation through an HTML-grounded
intermediary.  The selection of document file formats is expandable by addition of import
and export plugins.  

Editing in Corinthia is via a responsive editor, implemented in JavaScript and HTML (CSS),
that works on the web, in the cloud, and also adapts across device form factors for practical
use on mobile devices, tablets, and touch-enabled as well as keyboard-oriented interfaces.
 Corinthia document viewing and editing is on the intermediate form, limited to common, widely-supported
features. Corinthia is not a comprehensive substitute for format-specific authoring, editing,
and final-form printing/production software.

To avoid irreversible loss of features from imported documents, Corinthia encapsulates unsupported
feature occurrences in a form that can be recovered from the intermediate as part of subsequent
export to the same or different format.

Identification and confirmation of inter-convertible features of different formats for dependable
import and export involves development of extensive test documents in the different formats.
 There is profiling of the extent to which standardized formats are supported in practice,
with identification of deviations and implementation-dependent choices that impact convertibility.

All of the Corinthia test cases, profiling, plugin development, libraries, and utilities are
reusable resources to other projects.  All development of source-code for binaries is in portable
C Language for multi-platform compilation as well as API "wrapping" for delivery to other
programming models, such as for Python, .NET, Java, and Node.js.  Document format file import
and export plugins may be adaptable as import-export extensions used with other document-processing

-----Original Message-----
From: jan i [] 
Sent: Wednesday, November 26, 2014 03:13
Subject: Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.

Hi all.

We, at the project, hope that the lack of discussion is not a negative sign

In the meantime, we have been working behind the scenes, and a couple of
things have happened:

- The proposal is now on the incubator wiki / corinthiaProposal

- Dennis Hamilton (incubator, aoo committer) joined the initial committer
list. His expertise in especially document formats will be of great value
to the project, Dennis is also providing a lot of good feedback on our open

- Daniel Gruno (Humbedooh) has volunteered to be mentor for the project. We
look forward to guidance in all the tricky "paper work".

- Talks are being prepared for ACNA.

We are more than happy to answer any questions and make requested changes.

on behalf of the project
jan i

On 24 November 2014 at 22:14, Ross Gardler (MS OPEN TECH) <> wrote:

> There are some passing similarities with Forrest here. I'm not suggesting
> any changes to the proposal, just flagging that the intermediate format
> approach described here is the approach Forrest takes. The focus for
> Forrest was not on document format conversion but there is a lot of
> experience there in using intermediate formats.
> Microsoft Open Technologies, Inc.
> A subsidiary of Microsoft Corporation
> -----Original Message-----
> From: jan i []
> Sent: Monday, November 24, 2014 12:37 PM
> To: jan i
> Cc:
> Subject: Re: [PROPOSAL] [DISCUSSION] Corinthia for Incubation.
> Hi.
> Sorry, somebody hit me with the big GIT hammer !! I did something with git
> that should not be done.
> The correct text is:
[ ... ]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message