See also: IRC log
<wiecha> http://lists.w3.org/Archives/Public/public-xg-app-backplane/2009May/0005.html
<scribe> scribe: John
Charlie: {Discusses expense report sample}
<scribe> scribenick: John_Boyer
Charlie: sample gives people idea
of relevance of recognizing ODF markup directly in the web
browser
... rules language in ODF that generates something like table
of contents based on markup in body of document
... conditional rules for content like only show expenses if
you have them
... as prototype, would like to put xf:group in the text
content to do relevance on the ODF content.
... Presumably you'd want something to only show in table of
contents if it was relevant
... So, would show second order ODF language constructs
consuming relevance information applied to other parts of
document
... Explains that some of the content like "Actual Expenses"
will have draw:control elements to expose actual results like
"You claimed $200" and possibly even date ranges over which the
claimed expenses were made
... An ODF-level calculation could make "clip-level"
calculations, but not sure if it should go at the view level or
if it would sink down into the XForms application level.
John: Think that it would likely be either a constraint or an attenuating calculate to express difference between "expense you had" versus "expense reimbursable according to policy"
Charlie: Is there some other calculations that could reasonably be done at the ODF presentation layer?
John: There are lots of
calculated results that are for presentation only but aren't
really needed by the back-end system.
... the expense report total is for the user and the
client-side total calculation would not be needed or even
necessarily trusted by the server side app
Charlie: whole document goes back to the server side
John: yes, but document is archived, and data is extracted to drive back end transaction. Data needs only the inputs, not the calculated totals
Charlie: This app including svg, smil, odf shows an emerging set of vocabularies that could be dealt with on the web using a ubiquity approach
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: John Found ScribeNick: John_Boyer WARNING: No "Topic:" lines found. WARNING: No "Present: ... " found! Possibly Present: Charlie IBM John John_Boyer scribenick wiecha You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Agenda: http://lists.w3.org/Archives/Public/public-xg-app-backplane/2009Jun/0014.html Got date from IRC log name: 30 Jun 2009 Guessing minutes URL: http://www.w3.org/2009/06/30-backplane-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]