Re: [tamie] New "design" section in wiki

["Stephen Green" <stephen.green@documentengineeringservices.com>]

Of course it would be outside of the charter to deliberately
seek to provide for use cases other than testing and monitoring.
I just find it interesting that ETSM might be very useful in other
areas too since it provides the possibility of a general way to
make it easy to write scripts which act on XML using XSLT.
Those for whom XSLT is a challenge (due to its recursive nature)
may find it easier to use ETSM to achieve the same ends. I
accept that this is beyond the charter though. I just thought that
if we do not use the words 'test' and 'monitor' in the ETSM
language then other efforts to profile it for more general use would
not be ruled out.

I can appreciate the need to focus the terminology on testing
and monitoring though, to ensure the charter and use cases are
properly covered.

Best regards

Steve

2008/12/22 Hyunbo Cho <hcho@postech.ac.kr>:
> Stephen,
>
> Just my two cents. Do we really want a neutral term?
> Can we go with "test"+something (for example testscript) for ver 1.0.
> Then we may miss "monitoring" implication of eTSM.
>
> -Cho
>
>
> -----Original Message-----
> From: Durand, Jacques R. [mailto:JDurand@us.fujitsu.com]
> Sent: Thursday, December 18, 2008 11:04 PM
> To: stephen.green@documentengineeringservices.com
> Cc: tamie@lists.oasis-open.org
> Subject: RE: [tamie] New "design" section in wiki
>
> Stephen:
>
>
>>I like the term 'scriptlet' - more neutral
>
> I am concerned that scriptlet (with 'ptl' in the middle) is not easy to
> pronounce... I thought "scriplet" was a convenient shortcut, but I let
> the language experts decide.
> Also, "scriptlet" seems already used in Java in a slightly different
> sense:
> "scriptlet:
> In JavaServer Pages (JSP) technology, a scriptlet is a piece of
> Java-code embedded in the HTML-like JSP code."
>
>>there seems to be inconsistent use of the etsm: prefix.
>
> Right - we could set the default namespace prefix as etsm, only once,
> e.g. in every example in the root element.
>
>>I've not yet read through all of the content
>
> I have added a "Detailed Features" subsection for various features, e.g.
> the <exit> statement.
>
> Also added one more solution to Use Case #1 : Here is how Use Case #1
> would look like with the latest design:
>
> http://wiki.oasis-open.org/tamie/better-UC1-Proposal1
>
>
> Jacques
>
>
>
> -----Original Message-----
> From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] On
> Behalf Of Stephen Green
> Sent: Thursday, December 18, 2008 12:10 AM
> To: Durand, Jacques R.
> Cc: tamie@lists.oasis-open.org
> Subject: Re: [tamie] New "design" section in wiki
>
> Jacques,
>
> Very good. I like the term 'scriptlet' - more neutral so it can apply to
> all uses of the script language.
>
> Just one minor comment: there seems to be inconsistent use of the etsm:
> prefix. Maybe it should be removed everywhere to make it easy to see the
> names like 'loop' and also like 'eval' and 'decide'.
> If not removed, I would have thought it should be used everywhere
> instead, including with 'loop', etc.
>
> I've not yet read through all of the content yet but from what I have
> read it seems very much in line with our consensus in Seoul.
>
> Many thanks.
>
> Steve
>
> 2008/12/18 Durand, Jacques R. <JDurand@us.fujitsu.com>:
>> I tried to capture the latest design consensus in a new wiki section
>> titled "Scripting Design (eTSM)":
>>
>> http://wiki.oasis-open.org/tamie/FrontPage
>>
>> Please review / comment.
>>
>> I suggested a new term for testflow: scriplet....
>>
>>
>> -Jacques
>>
>>
>
>
>
> --
> Stephen D. Green
>
> Document Engineering Services Ltd
>
>
>
> http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice
>
> ---------------------------------------------------------------------
> 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
>
>
>
>
>