[jsdl-wg] Teleconfence minutes - 11 March 2009
Donal K. Fellows
donal.k.fellows at manchester.ac.uk
Mon Mar 16 06:48:40 CDT 2009
Andreas Savva wrote:
> Minutes uploaded to gridforge.
Here, somewhat late, is my suggested wording for the final paragraph of
Implicit type casting is permitted of a value of one Simple XSD type
to another Simple XSD type values, subject to the condition that the
value MUST be syntactically legal in both types (e.g. casting "42"
from xsd:integer to xsd:string). With Complex XSD content, the
replaced node MUST be an Element node or Processing Instruction node
and the replacement MUST NOT be an Attribute node or Document node. In
both cases, the resulting document MUST be a valid document (according
to the XML Schema of the document and any adopted extensions) after
all substitutions have been performed; if the result is not valid, the
JSDL Job Template document MUST be rejected.
OK, it's a bit wordier than before, but I had to write it like that to
allow the replacement of a single element with multiple elements which
is a feature I'd like to continue to permit. I'd have also written it
just to do upcasting to string (for simple content) except that that
would cause other problems when the target value is not a string in the
schema (like many places in JSDL).
More information about the jsdl-wg