|Subject:||RE: [oic] Document Interoperability Test Scenarios|
|From:||Hanssens Bart (Bart...@fedict.be)|
|Date:||Jan 29, 2009 3:34:23 pm|
Stephen (and the other members of course)
that's quite a list, very nice !
I think Dennis is still on a well-deserved break, but it would indeed be wise to check with him to organize these scenarios on the wiki.
Since SVN is up and running: proposals for a layout are welcome :-) Probably the classic trunk-tag-branch, perhaps with subdivisions like
/documents (the ODF docs) /results (test results in an XML schema) /scenarios (the steps for a scenario, in an XML schema or plain text) /upload (various stuff)
Maybe we have to create more subdirs (or maybe not...)
Not sure though if, for instance, a result ODF-document and a result ODF-metadata file should go in the same directory or not, so we need to give it some thought...
As promised, the list below details a set of document test scenarios that we
believe are a solid representation of the real-world documents that exist out
there today. If there are no objections to these items, then I will work with
Dennis to get them posted to the wiki tomorrow/early next week.
Presentations that are highly customized, well polished and represent something
larger than the particular individual.
Presentations that are either oriented around informal meetings such as internal
team meetings ( e.g., a simple agenda slide to team status ).
Presentations that are created on the fly and used to capture meeting minutes or
Presentations that are photo-heavy and provide simple slide shows with photos as
the primary content.
Presentations that are very information dense and often used in the financial
Presentations that are designed to be given to a potential customer with the
goal of distinguishing the presenter/presenter's organization from the
Presentations that are generally used as kiosks ( both interactive and not ) as
well as self-paced training and education.
Single-slide presentations generally used for creating certificates, posters and
Spreadsheets that contain code which provides custom functions, macros (to
automate tasks), or UI to make the user more efficient when working with the
Spreadsheets that are information dense, usually rolling up a company's
financial situation through many formulas and relationships.
Spreadsheets that contain copious amounts of information (often from another
application, external data sources, or copy/paste) and are then used to
summarize the information, turning it into data.
Spreadsheets that are used to convey information from one application to another
- usually in the form of CSV/TSV.
Spreadsheets that consolidate information from various data sources (or manual
entry) and then clean the data through a series of macros or user interaction in
order to make it more reliable for consumption by other LOB applications
Financial Statements / Balance Sheets
Spreadsheets that contain an income statement, balance sheet, and cash flow
statement. Relatively simple in that they contain Text, numbers, formatting,
and a few formulas.
Forms and Calculators
Spreadsheets that are used to input data that is later used for other LOB
systems or for a calculator in the same workbook. These spreadsheets often have
very locked down sheets, where the user can only select certain options or enter
data in certain cells.
Spreadsheets that are used as a 2 dimensional layout surface (for the structure
of the grid) in order to build a well laid out document.
Spreadsheets that are used like a Presentation, generally with one "slide" per
Spreadsheets that are used to track resources and work items for a project,
often including a Gantt chart of the project timeline using a grid.
Stochastic Modeling / Simulation
Spreadsheets that are used to perform iterative analysis of/prediction of an
event taking place in order predict the outcome of said event. These
spreadsheets that contain information that models a real-life system (oil
production, factory floor, financial vehicles, etc.) to which inputs can be
inserted and the results analyzed in order to find efficiencies.
Spreadsheets consisting of a list (or lists) of data, usually manually entered
into the spreadsheet.
Documents that contain carefully formatted content intended for publication in a
Documents that are used to compile the manuscript of a book in a format ready
Documents containing several pages of basic, unformatted text, without specific
Documents used as marketing materials - single page, designed for 6+ foot
Documents that contain a page of label templates, which are merged with
addresses and printed.
Documents used in legal proceedings - must conform to a specific layout/form,
and are typically built over many revisions by many authors.
Documents containing plain, unformatted text, intended for personal
Documents used to capture the results of a meeting- often informal, created
ad-hoc during the meeting itself.
Documents used to formally present a small amount of information (e.g. an
initiative or concept).
Documents containing multiple streams of specially laid out content (typically a
fixed layout making use of 2D aspects of the page).
Notes / Lists
Documents that are created on demand to store informal information (e.g.
Documents that contain an outline of a larger document, but little/none of the
Documents containing a customer proposal, compiled from several authors and many
sources (spreadsheets, presentations, etc.).
Research Papers / Reports
Documents that are highly technical and conform to a specific layout - common
usage of academic features like equations/bibliography.
Short, highly structured documents intended to convey information in a single
page. Formatting is used to customize the structured base.
Structured Documents / Forms
Documents that contain structured content intended to be populated from data
sources (e.g. a database) or form input from the user.