[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office] Custom display names in data pilot tables
Hi Kohei, Thanks for sending this proposal along. As you said, "lots of things have changed" on the TC. Let me quickly bring you up to speed on where we are with ODF 1.2. Last November we asked had a "last call" for ODF 1.2 feature proposals, and asked TC members to make any remaining proposals. We then went through those proposals in December and January, refining some of them while deferring others to the next release, "ODF-Next". Patrick then integrated all of the new proposals into the draft, which we approved as a Committee Draft earlier in the spring. Since then we have been working on resolving defects reported via the public comment list and doing the final editorial touches. We're very close to having ODF 1.2 ready for public review. So, although I won't say that we absolutely, positively cannot accept any new proposals at this point, I do think that there would need to be a very good argument for adding a new feature now, and a very high degree of consensus on the TC that we should introduce such a new feature. And I'd certainly be afraid that if we open it up for new features, we'll find that almost every TC member has something they want to add in as well. And then we'll never end. So would it be possible to add your proposal to the list of features for ODF-Next? The hope is that after the redfrafting of ODF 1.2 is done, which has had a rather long development cycle, we can produce future reversions more easily and at more frequent intervals. If you can do this, you would add the proposal to JIRA and set the "fix version" field to ODF-Next. Thanks! -Rob From: Kohei Yoshida <kyoshida@novell.com> To: office@lists.oasis-open.org Cc: robert_weir <robert_weir@us.ibm.com>, Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM> Date: 09/10/2009 11:52 AM Subject: Re: [office] Custom display names in data pilot tables Sorry for asking again, but do I need to file this to a JIRA and request a discussion? Lots of things seem to have changed on this TC lately. Kohei On Wed, 2009-09-02 at 15:27 -0400, Kohei Yoshida wrote: > Sorry I lost track of this proposal, but I had proposed this, solicited > feedback but got nothing so far. Does this mean this proposal is good > to go? > > If yes, I would like to request a vote on this proposal, or whatever is > required to bring this proposal to the next step. > > Comments would be great. > > Thanks, > Kohei > > On Mon, 2009-05-04 at 22:28 -0400, Kohei Yoshida wrote: > > On Mon, 2009-05-04 at 22:12 -0400, Kohei Yoshida wrote: > > > I'm looking forward to your feedback. > > > > Oh I almost forgot. Here is the requested change: > > > > 8.7.x table:data-pilot-grand-total (new) > > > > The <table:data-pilot-grand-total> element stores attributes associated > > with the grand total results of a data pilot table. Each data pilot > > table may display column grand total, row grand total, or both. This > > element stores visibility of each grand total result and optionally an > > alternative text to be displayed in lieu of the default text. When this > > element is absent, both the column and row grand totals should be > > present and visible. > > > > The <table:data-pilot-grand-total> element replaces the deprecated > > table:grand-total attribute, which was previously used as an attribute > > of the <table:data-pilot-table> element to store visibility information > > of the grand total results. For backward compatibility, however, the > > application should, when writing to a document, store the visibility > > information with the table:grand-total attribute even when the > > <table:data-pilot-grand-total> element is provided. When loading a > > document, the visibility information stored with the > > <table:data-pilot-grand-total> elements shall take precedence over the > > one stored with the table:grand-total attribute of the > > <table:data-pilot-table> element. > > > > The <table:data-pilot-grand-total> element may be used within the > > following element: <table:data-pilot-table>. > > > > The <table:data-pilot-grand-total> element may have the following > > attributes: table:display, table:orientation, table:display-name. > > > > 18.x table:display-name (new) > > > > 18.x.1 General (new) > > > > The table:display-name attribute in general is used with an element that > > has a "name" attribute associated with it (primary name), to specify an > > alternative name for display purposes. When this attribute is absent, > > the value of the display name equals the value of the primary name of > > that element. > > > > The table:display-name may be used with the following elements: > > <table:data-pilot-grand-total>, <table:data-pilot-field>, > > <table:data-pilot-member>, and <table:data-pilot-subtotal>. > > > > 18.x.2 <table:data-pilot-subtotal> (new) > > > > The table:data-pilot-subtotal element may use the table:display-name > > attribute to store an alternative subtotal text. When the value of the > > table:function attribute is "auto", the alternative text specified by > > the table:display-name attribute shall be used instead of the default > > subtotal text. > > > > When the alternative subtotal text is used, a backslash character ('\') > > must escape a question mark ('?'), while all un-escaped question marks > > shall be interpreted as the respective field member name when the text > > is displayed on screen. A literal backslash character is represented by > > two successive backslash characters ('\\'). > > > > 18.972 table:display (change) > > > > The table:display attribute may be used with the following elements: > > <style:table-properties> 16.8, <table:data-pilot-grand-total> 8.7.x, > > <table:data-pilot-member> 8.7.11, <table:error-message> 8.4.3.2, > > <table:help-message> 8.4.3.1, <table:table-column-group> 8.1.9 and > > <table:table-row-group> 8.1.8. > > > > 18.1041.x <table:data-pilot-grant-total> (new) > > > > The table:orientation attribute specifies the orientation of a grand > > total result. The possible values are: row, column, or both. The > > default value is both. > > > > Schema changes/additions: > > > > <define name="table-display-name" combine="interleave"> > > <optional> > > <attribute name="table:display-name"> > > <ref name="string"/> > > </attribute> > > </optional> > > </define> > > > > <define name="table-data-pilot-grand-total"> > > <element name="table:data-pilot-grand-total"> > > <group> > > <attribute name="table:orientation"> > > <choice> > > <value>row</value> > > <value>column</value> > > <value>both</value> > > </choice> > > </attribute> > > <attribute name="table:display"> > > <ref name="boolean"/> > > </attribute> > > <ref name="table-display-name"/> > > </group> > > </element> > > </define> > > > > <define name="table-data-pilot-table"> > > <element name="table:data-pilot-table"> > > <ref name="table-data-pilot-table-attlist"/> > > <optional> > > <choice> > > <ref name="table-database-source-sql"/> > > <ref name="table-database-source-table"/> > > <ref name="table-database-source-query"/> > > <ref name="table-source-service"/> > > <ref name="table-source-cell-range"/> > > </choice> > > </optional> > > <zeroOrMore> > > <ref name="table-data-pilot-grand-total"/> > > </zeroOrMore> > > <oneOrMore> > > <ref name="table-data-pilot-field"/> > > </oneOrMore> > > </element> > > </define> > > > > <define name="table-data-pilot-field-attlist" combine="interleave"> > > <ref name="table-display-name"/> > > </define> > > > > <define name="table-data-pilot-member-attlist" combine="interleave"> > > <ref name="table-display-name"/> > > </define> > > > > <define name="table-data-pilot-subtotal-attlist"> > > <choice> > > <attribute name="table:function"> > > <choice> > > <value>average</value> > > <value>count</value> > > <value>countnums</value> > > <value>max</value> > > <value>min</value> > > <value>product</value> > > <value>stdev</value> > > <value>stdevp</value> > > <value>sum</value> > > <value>var</value> > > <value>varp</value> > > <ref name="string"/> > > </choice> > > </attribute> > > <group> > > <attribute name="table:function"> > > <value>auto</value> > > </attribute> > > <ref name="table-display-name"/> > > </group> > > </choice> > > </define> > > > > Regards, > > > > Kohei > > > > > --------------------------------------------------------------------- > 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 >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]