/ Martin Duerst [EMAIL PROTECTED] was heard to say:
| If there is actual non-determinism now in the Atom core, that would be
| a reason for concern. If there is potential non-determinism in the
Look at the content model for entry: it's a bag o' stuff some of which
is required and some of which is
Norman Walsh wrote:
Look at the content model for entry: it's a bag o' stuff some of which
is required and some of which is optional (and optionally repeatable)
and it's all allowed to occur in any order.
I've forgotten the details of XSD's support for content models, but
I'm pretty sure
Hello Thomas,
At 07:34 05/05/22, Thomas Broyer wrote:
I'm sorry to raise this issue back again but...
The Atom Publishing Protocol defines SOAP bindings. This (in my mind)
means there will be WSDL files over there. WSDL rely on XML Schema which in
turn are limited to deterministic content
Martin Duerst wrote:
At 07:34 05/05/22, Thomas Broyer wrote:
I'm sorry to raise this issue back again but...
The Atom Publishing Protocol defines SOAP bindings. This (in my mind)
means there will be WSDL files over there. WSDL rely on XML Schema
which in turn are limited to
/ Thomas Broyer [EMAIL PROTECTED] was heard to say:
| I'm sorry to raise this issue back again but...
|
| The Atom Publishing Protocol defines SOAP bindings. This (in my mind)
| means there will be WSDL files over there. WSDL rely on XML Schema
| which in turn are limited to deterministic content
Norman Walsh wrote:
There is no 1:1 correspondence between schemas and documents. You can
have as many schemas as you want. If your application demands
additional constraints, such as determinism, you can define your own
schema that enforces them. Then your system will reject documents
Thomas Broyer wrote:
I Agree, though many HTML pages which I've looked at the source has
their HEAD content in the form:
* TITLE
* META
* LINK
* STYLE or SCRIPT
* SCRIPT or STYLE
so a deterministic content model would be a pain I think...
Wow! Sorry, it would NOT be pain
I'm sorry to raise this issue back again but...
The Atom Publishing Protocol defines SOAP bindings. This (in my mind)
means there will be WSDL files over there. WSDL rely on XML Schema which
in turn are limited to deterministic content models.
Will the APP limit Atom entries in SOAP
