[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: about another default value proposal
Dear TC members,
Just on the TC call, folks discussed the proposal "attribute default values"(http://wiki.oasis-open.org/office/proposal%3Adefault-values). This proposal is about the default value presenting form, i.e. using a RNG schema or a comment in the specification. I've no strong concern about that.
But besides the default value form in the specification, what I'm interested in are the default value contents. You know it is another proposal for default values initially proposed by Helen Yue(http://lists.oasis-open.org/archives/office/200708/msg00120.html), collected data from OpenOffice,KOffice and Symphony, latest updated document by Michael(http://lists.oasis-open.org/archives/office/200804/msg00092.html), which has been under discussion for a long time. Obviously, the default value inconsistency will impact the interoperability between different ODF applications, so I think we need to continue discussing this issue. Actually, this proposal already made a big progress, and Michael has summarized a comprehensive comparison document based on different application default values. But how to process these default values next seems still unclear(IMHO)now, what I understand can be:
1)Each application representative needs to review the comparison document, check whether something is lost or incorrect;
2)Those n/a values in the comparison document can be regarded as "consistent" with other specified values; right?
3)Most of default values are consistent, which will be put into ODF1.2 specification; right?
4)Make sure those non-necessary defined values(marked as yellow) are really not necessary defined;
5)Unify the length unit for the floating values, whether using metric "cm" or "inch";
6)Some of conflict values(marked as red) need to discuss in the mailing list or TC call, resolve the conflicts and make the consensus. I saw Michael already give the proposal values for some conflict values, and some are still blank. I've done an easy thing, that extracted the conflict values (totally 42) from the comparison document as this spreadsheet:(See attached file: ConflictDefaultValues.ods). FYR.
Hope everyone have a nice day!
IBM Lotus Symphony Development
IBM China Software Development LAB, Beijing
Tel: 86-10-82452493 Fax: 86-10-82452887
NOTES:Ming Fei Jia/China/IBM E-mail: firstname.lastname@example.org
Address: 4/F, DeShi Building No.9, East Road, ShangDi, Haidian District, Beijing 100085, PRC