OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oiic-formation-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [oiic-formation-discuss] (1)(d) A list of deliverables,with projected completion dates.

Hi Dave,

Dave Pawson wrote:
> 2008/6/13 Michael Brauer - Sun Germany - ham02 - Hamburg
> <Michael.Brauer@sun.com>:
>>>> I think we should focus on those features actually that are
>>>> widely used rather than on test cases where we know that the features
>>>> are not widely implemented.
>>> With what objective please?
>>> A conformance check on the easily implemented tests (or weakly defined
>>> features)?
>> No, this is not what I meant. What I meant is that we should aim to measure,
>> improve or write guidelines for those ODF features that are commonly used
>> rather than caring about a few features that are seldom used.
> Since we have no evidence as to 'what is commonly used' (and by whom)
> I think that would be difficult.

But do we have evidence what is "not widely implemented"?

You argument may be right, but it when applies also "not widely 

>>>> So far we have suggestion for tests, but we do not have suggestion how
>>>> we can help implementors in their implementation work.
>>> I didn't read that in the charter Michael. Could you point it out please?
>> Sorry, but to which charter you are referring. The purpose of this group is
>> to discuss a charter, but I don't think this list has a charter itself. But
>> actually implementation guidelines are included as item 4 in the
>> announcement of this list:
>> http://lists.oasis-open.org/archives/oiic-formation-discuss/200806/msg00001.html
>> So, its not out of scope.
> Oh dear.
> 1.	To publish test suites of ODF for applications of ODF to check their
> conformance with the Standard and to confirm their interoperability;
> 2.	To provide feedback, where necessary, to the ODF TC on ways in which the
> standard could improve interoperability;
> 3.	To produce a set of implementation guidelines;
> 4.	To define interoperability with related standards by the creation of
> profiles or technical reports;
> 5.	To coordinate, in conjunction with the ODF Adoption TC,  OASIS InterOp
> demos related to ODF;
> I interpreted item for in context.
> I.e. guidelines on implementing tests. Not implementing ODF.

I read it differently. My interpretation is that guidelines for 
implementing ODF are meant.

Anyway, this list is not our charter. It contains only suggestion.

> I wonder how many other misinterpretations there are
> by myself and other people.
> AFAIK you are the first person to mention ODF implementation
> guidelines on this list.
> regards

Michael Brauer, Technical Architect Software Engineering
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500

Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
	   D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]