2008/6/20 Hurley, Garry (L&I - OIT) <>:
> I commented on some of Dave's comments to Rob's points. Some I agree with, others I thought to clarify or seek input. Please consider what I wrote (included in rows of asterisks ['*']) and add input as necessary. My suggestions for profiles may be off-base for some, but dead on for others. And they are not detailed, just considerations I thought were necessary for what I see as different classifications of profiles. Please note, I did not specify that these were application profiles, testing profiles, etc. I think I generalized the considerations pretty well, but I could have missed one or twenty. Feel free to tear me apart.
>> 2) Researching the best practices in profiles, and issuing a "ODF Profiles
>> Requirements" document
>
> I'd like the TC to go further than this and define an appropriate
> profiles list.
>
> *******
> How does this sound for a partial list?
Put it on the 'wiki' page Garry. Useful.
I'm of the opinion that the TC should define a profile
then generate a useful list of profiles?
On that basis only I'm -1 on including them in the scope/deliverables.
If the TC come up with more they won't be able to add them?
<snip/>
> *******
>> 3) Creating an "ODF Conformance Test Requirements" document that details the
>> exact items required to test conformance of an ODF document and of an ODF
>> application to the ODF standard.
>
> +1. Clarification. "exact items required" means how each atomic item
> in the standard
> is to be tested.
>
> *******
> See what I wrote above and use the 'bullets' beneath as a guide for test requirements. Flesh them out if you want, I just generalized things a bit for brevity.
> *******
I don't understand how the references to various profiles will help
with the rest Garry?
Would you explain please.
regards DaveP
>
>> 4) Creating an ODF Interoperability Test Requirements document that defines
>> additional tests, including an Acid-like test and other interoperability
>> tests.
>
> *******
> See what I wrote in response to #3.
> *******
>
>
>> 6) Write profile of ODF to improve interoperability in specific areas. I've
>> heard ODF for archiving and ODF for web mentioned.
>
> *******
> See number 3.
> *******
>
>
>> 7) Write guidelines for ODF implementors on various topics, i.e., how to use
>> the internationalization features of ODF.
>
>
> *******
> See again number 3.
> *******
>
>
>
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
