OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oic message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [oic] Groups - ApplicationScenarioTesting-wd1.odt uploaded


What is an Application Scenario?  This may be obvious, but I think we 
should explicitly say, something like "An Application Scenario is an ODF 
document containing the following required "parts", which describe ..."

Maybe even the the prescribed template for an application scenario is 
included as an annex?

Note that DITA XML is ideal for this, since DITA was designed to describe 
steps in technical documentation, which is essentially what we are doing 
here.  So we could easily design a DITA "topic" for an Application 
Scenario and then use the DITA Open Toolkit to generate HTML or PDF from 
the DITA. 

ID -- how does an author ensure uniqueness?  Should we namespace it 
somehow, like combine the submitters name, as in Weir.Robert.00001 ? 

Scenario step -- the key thing I think is that it needs to bebe written as 
a goal-oriented user instruction.  If you make it goal-oriented, then the 
application-neutral part comes along.  So say "create a table", not "chose 
Create/Table from the menu".

scenario checks -- this is interesting.  I suppose you could also refer to 
an anonymous "target" editor and define a check on how things appear when 
loading it there.  And how is this different than a test assertion?

Submitting and approving -- I would do those as a Standing Rule for the 
TC.  It really doesn't fit well in a specification, since it is a 
statement about process.  We can adopt any written Standing Rule by 
majority vote at any TC meeting.  But the file naming conventions are 
good.

We probably need a statement on any associated documents or files needed 
for the scenario, such as image files, TXT files to import, etc.  How are 
these associated with the scenario?

Regards,

-Rob

Hanssens Bart <Bart.Hanssens@fedict.be> wrote on 06/28/2009 02:01:21 PM:

> From:
> 
> Hanssens Bart <Bart.Hanssens@fedict.be>
> 
> To:
> 
> "oic@lists.oasis-open.org" <oic@lists.oasis-open.org>, Stephen 
> Peront <Stephen.Peront@microsoft.com>, "Dennis E. Hamilton" 
> <dennis.hamilton@acm.org>, Robert Weir <robert_weir@us.ibm.com>
> 
> Date:
> 
> 06/28/2009 02:03 PM
> 
> Subject:
> 
> Re: [oic] Groups - ApplicationScenarioTesting-wd1.odt uploaded
> 
> Hi,
> 
> 
> I've created a document on how to create Application Scenarios, like the
> expense sheet example I've created a few weeks ago, but slightly
> simplified: 
> 
> - just use the OASIS doc repository, we already know how to handle that
> - use an ODF template instead of XHTML experiment I've done earlier on
> (most people are more at ease with a word processor than an XML editor)
> 
> I've used the categorization from 
http://wiki.oasis-open.org/oic/AppScenarios
> (not sure who came up with that first: Stephen ? Dennis ?)
> 
> 
> Most people already are familiar with the concept of application 
scenarios
> (especially those who were present at the The Hague ODF event), so it
> should be fairly easy to come to a formal OIC TC agreement on this.
> 
> As Rob noted during the The Hague event, having the OIC to provide 
solid,
> well-defined Application Scenarios is very useful for testers outside 
the TC
> (and the TC could reuse the results - after removing the names of the
> implementations being tested - for reporting on the status of 
interoperability
> and/or define profiles)
> 
> 
> Best regards,
> 
> Bart
> 
> ________________________________________
> From: bart.hanssens@fedict.be [bart.hanssens@fedict.be]
> Sent: Sunday, June 28, 2009 7:40 PM
> To: oic@lists.oasis-open.org
> Subject: [oic] Groups - ApplicationScenarioTesting-wd1.odt uploaded
> 
> The document named ApplicationScenarioTesting-wd1.odt has been submitted 
by
> Mr. Bart Hanssens to the OASIS Open Document Format Interoperability and
> Conformance (OIC) TC document repository.
> 
> Document Description:
> Document describing how a Application Scenario should look like, how to
> store it etc
> 
> View Document Details:
> http://www.oasis-open.org/committees/document.php?document_id=33144
> 
> Download Document:
> http://www.oasis-open.org/committees/download.php/33144/
> ApplicationScenarioTesting-wd1.odt
> 
> 
> PLEASE NOTE:  If the above links do not work for you, your email 
application
> may be breaking the link into two pieces.  You may be able to copy and 
paste
> the entire link address into the address field of your web browser.
> 
> -OASIS Open Administration



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]