sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-assembly] Issue 123
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: OASIS Assembly <sca-assembly@lists.oasis-open.org>
- Date: Tue, 31 Mar 2009 10:26:58 +0100
Folks,
I take this discussion to mean that
my original proposal to use ##any with mixed='true' is the right one.
Anish points out that this does mean
that the schema is more permissive than we want,
but this is the case all over our specifications
- that's what the additional normative
statements are about. We can't
expect XSD to provide everything we need.
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com
From:
| Anish Karmarkar <Anish.Karmarkar@oracle.com>
|
To:
| OASIS Assembly <sca-assembly@lists.oasis-open.org>
|
Date:
| 30/03/2009 22:29
|
Subject:
| Re: [sca-assembly] Issue 123 |
If the type is xsd:string with mixed='true' then the
following will not
be valid:
<value>
<someValue>
<someSubelement>...</someSubelement>
</someValue>
</value>
The <value> element is meant to allow "inlining" of simple
type values
as well as elements whose type is complex. A true 'mixed' type isn't
what we want to allow but instead allow either inlined text (such as a
string, int etc) or element(s) but not both. I.e. the following won't be
allowed (by SCA not by schema):
<value>
This is some value <ele>another value</ele>
</value>
I know the current schema allows this, but I don't of a way to design
the schema to prevent it.
-Anish
--
ashok malhotra wrote:
> The XML Schema primer http://www.w3.org/TR/xmlschema-0/
> has an example of how to define an element that can contain mixed
content.
> This is exactly the same as Mike Edwards' suggestion except that the
> sequence is
> typed as xsd:string rather than xsd:any.
>
> I suspect Mike used ##any to allow simple data values but that not
helpful.
> because you don't know what the simple types are and cannot validate
them.
> Thus 5.0 will look like a string in any case. The simple types
will be
> validated
> in the specific context where they are used.
>
> Thus, unless Mike has other reasons to prefer ##any, xsd:string seems
> simpler and equally effective.
---------------------------------------------------------------------
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
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]