Re: [office-requirements] (Draft 2) text for call for proposals

[Patrick Durusau <patrick@durusau.net>]

Rob,

Much, much better.

Still a bit dry in the middle. Suggest perhaps a one liner about ODF 1.2 
getting cleaned up to go out the door. Followed by a general call as per 
your last paragraph before the "Some things to keep in mind."

That would just about fit on the average email window and take about as 
long to read as a 15-second spot on TV.

If we can hold their attention for that long.

I would lose the "Some things to keep in mind." I rather doubt we are 
going to be overrun by suggestions that run afoul of those. May have a 
few but those will be from people who won't read/understand the rules 
anyway.

I think what we want are the immediate reaction sort of suggestions. "If 
I could have anything it would be...." sort of stuff. We can then 
massage that into features for ODF-Next.

The really long, "considered" stuff, I have a trunk full of it, people 
are going to generate anyway. ;-)

I suppose I see the ODF-Next effort as having a two-fold purpose: 1) to 
get new ideas, but just as importantly, 2) to attract new people who are 
willing to contribute on a regular basis.

Hope you are having a great day!

Patrick

robert_weir@us.ibm.com wrote:
> Here is a second draft. 
>
> Patrick suggested we have a more compelling lead paragraph.   I considered 
> saying "The Power of XML compels you !" and repeating it 3 or 4 times, but 
> on further reflection abandoned that approach.  But I did try to jazz it 
> up a little to encourage the reader to read further.
>
> Mary also brought up an interesting timing aspect of this.  Since we will 
> likely end up with proposals coming in during the ODF 1.2 pubic review 
> periods, even from people who are unaware of this ODF-Next call for 
> proposals, we should probably time the comment period accordingly.  So I'd 
> suggest that we start the call to coincide with the approval of the next 
> Committee Draft of ODF 1.2, and conclude it when the last part of ODF 1.2 
> has ended its public review.  This will likely cause us to miss the May 
> 1st deadline we originally conceived, but it will ensure that we don't 
> write up the ODF-Next report while relevant comments are still coming in.
>
> -Rob
>
> ---------------------------------------
>
> "We have it in our power to begin the world over again"  -- Thomas Paine 
> (Common Sense, 1776)
>
> You are invited to help define the feature set of the next revision of 
> OASIS OpenDocument Format (ODF). Help us take "ODF-Next" to a higher stage 
> of document evolution. Be creative.  Push the envelope.  Be provocative. 
> Change the paradigm.  Start a revolution.. The only limits on our vision 
> are our own.
>
> The OASIS ODF TC has recently finalized the approval of technical 
> proposals which will be included in ODF 1.2.  After these proposals are 
> integrated into the ODF 1.2 draft, and remaining editorial tasks are 
> completed, the draft specification will be sent on for Public Review, and 
> then finally onto a ballot for approval as an OASIS Standard. 
>
> Concurrent with these final stages of ODF 1.2 work -- which may take 
> several months -- the ODF TC wishes to start a public conversation related 
> to the technical contents of "ODF-Next", the provisional name for the next 
> major version of ODF.   The ODF TC has created a subcommittee, the ODF 
> Requirements Subcommittee, chaired by Bob Jolliffe (email address here), 
> in order to gather, categorize and prioritize proposals for ODF-Next, and 
> to report back tot he ODF TC with recommendations.  The target for this 
> report is May 1st, 2009.
>
> We wish to now start gathering proposals now, from TC members, from the 
> OASIS community, from ODF implementors, government, academia, and from the 
> public at large.  What features should be added?  What capabilities do we 
> need?  Where do we want to take ODF next?  We want you to think broadly 
> and boldly on where we can take this standard in the next major revision.
>
> Some things to keep in mind:
>
> 1) ODF is a standard for a document format.  It is not a standard for a 
> word processor or spreadsheet application.  So proposals will need to 
> touch upon items that are reflected in the stored document.  Requests to 
> change the UI of an application, or make it print faster, are examples of 
> things that are out of scope.
>
> 2) The more detail you can provide in the proposal, the better.  If a 
> specific change is requested, please give section references relative to 
> the latest ODF 1.2 Committee Draft (insert URL here).
>
> 3) All proposals will need to be submitted in accordance with OASIS IPR 
> Policy to the ODF TC's public comment list.  Information on joining this 
> list can be found here (insert URL here).  Please also indicate "ODF-Next" 
> as part of the subject line of your post.
>
> 4) All proposals previously submitted to the ODF TC's public comment list 
> will automatically be considered for ODF-Next.  So there is no need to 
> resubmit an idea if it was already previously submitted.
>
> 5) For inclusion in the ODF-Next report, proposals must be received by 
> March 31st, 2009.
>
>
> We welcome and look forward to your contributions !
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>
>   

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)