Part 3 MCE - some test scenario definitions (based on XSpec-style definitions)

[Shawn Villaron]

I see.  Dave or Owen, any chance you can help out? I'm in Redmond on Thursday of that week due to an EricR review.

-----Original Message-----
From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA Makoto
Sent: Thursday, September 19, 2013 10:04 PM
To: Inigo Surguy
Cc: e-SC34-WG4 at ecma-international.org
Subject: Re: Part 3 MCE - some test scenario definitions (based on XSpec-style definitions)

Inigo,

Thank you for creating this.  Since I now have an implementation of
MCE in XSLT2,
your format for test cases is very interesting.

Here are some comments.

m:expect and m:error has @understands, which specifies a collection of
understood namespaces.  But we also need an attribute for a collection
of application-defined extension elements (i.e., (namspace, localName) pairs)

anyType should be anyType*.

I  can change the schema and XSTL if I have write access.

Regards,
Makoto


2012/10/18 Inigo Surguy <inigo.surguy at gmail.com>:
> In the discussion of MCE today, I thought it would have been good to have
> some examples of the constructs we were discussing.
>
> Clearly, in order to have examples, we need to have an XML format for these
> examples that can be automatically tested, we need to have a schema for this
> XML, and some XSLT to turn it into something human readable.
>
> The definitions, the schema for them, and the XSLT to process it into
> human-readable form is at:
>
>      https://github.com/inigo/mce-tests
>
> An example of the HTML output is:
>
>
> http://htmlpreview.github.com/?https://github.com/inigo/mce-tests/blob/master/mspecOutput.html
>
> This could be extended to test an MCE implementation, but I haven't done
> anything like that.
>
> No-one's checked the scenarios, so let me know if they're wrong. You can
> send GitHub pull requests, or just email me.
>
> Inigo



-- 

Praying for the victims of the Japan Tohoku earthquake

Makoto