W3C home > Mailing lists > Public > xmlschema-dev@w3.org > August 2001

validating elements problem

From: <Holger.Joukl@LBBW.de>
Date: Fri, 3 Aug 2001 15:18:58 +0200
Message-Id: <200108031300.PAA11513@bank.de>
To: xmlschema-dev@w3.org
Hi there,
I have some problems understanding the REC part 1, structures, once again.

This is taken from chapter 3.3.4, Validation Rule: Element Locally Valid
(Element)

<snip>
5 The appropriate case among the following must be true:
    5.1 If the declaration has a {value constraint}, the item has neither
element nor character [children] and clause 3.2 has not applied, then all
of the following must be true:
     5.1.1 If the ·actual type definition· is a ·local type definition·
then the canonical lexical representation of the {value constraint} value
must be a valid default for the ·actual type definition· as defined in
       Element Default Valid (Immediate) (§3.3.6).
     5.1.2 The element information item with the canonical lexical
representation of the {value constraint} value used as its ·normalized
value· must be ·valid· with respect to the ·actual type definition· as
       defined by Element Locally Valid (Type) (§3.3.4).
    5.2 If the declaration has no {value constraint} or the item has either
element or character [children] or clause 3.2 has applied, then all of the
following must be true:
     5.2.1 The element information item must be ·valid· with respect to the
·actual type definition· as defined by Element Locally Valid (Type)
(§3.3.4).
     5.2.2 If there is a fixed {value constraint} and clause 3.2 has not
applied, all of the following must be true:
       5.2.2.1 The element information item must have no element
information item [children].
       5.2.2.2 The appropriate case among the following must be true:
         5.2.2.2.1 If the {content type} of the ·actual type definition· is
mixed, then the ·initial value· of the item must match the canonical
lexical representation of the {value constraint} value.
         5.2.2.2.2 If the {content type} of the ·actual type definition· is
a simple type definition, then the ·actual value· of the item must match
the canonical lexical representation of the {value constraint}
          value.
</snip>

Take a look at 5.1.1: "...the canonical lexical representation of the
{value constraint} value must be a valid default for the ·actual type
definition· as defined in
       Element Default Valid (Immediate) (§3.3.6)."

But isn´t the schema itself invalid if the "{value constraint} value" is
not a valid default for the "actual type definition"?
I thought this is exactly what [§3.3.6: Element Declaration Properties
Correct] ensures?

Any comments are appreciated,
Best regards,
  Holger

_________________________

Holger Joukl
LBBW
2342 Z - IT/Org II Handel
Tel. +49 (711) 124 - 7078
_________________________



______________________________________________________________________


--------------------------------------------------------------------------------------------
Bitte beachten Sie, dass der Inhalt dieser E-Mail einschließlich eventuell
angehängter Dokumente vertraulich ist. Falls Sie nicht der angegebene
Empfänger sind oder falls diese E-Mail irrtümlich an Sie adressiert wurde,
dürfen Sie die E-Mail und eventuell angehängte Dokumente weder öffnen,
lesen, kopieren, verbreiten noch ihren Inhalt in irgendeiner Weise nutzen.
Bitte verständigen Sie den Absender sofort und löschen Sie die E-Mail
sodann.

Die Sicherheit von Übermittlungen per E-Mail kann nicht garantiert werden.
Per E-Mail übermittelte Informationen können abgefangen oder geändert
werden, verloren gehen oder zerstört werden, verspätet oder unvollständig
ankommen, oder Viren enthalten. Der Absender übernimmt daher keine Gewähr
für Irrtümer oder Auslassungen jeder Art im Inhalt sowie sonstige Risiken,
die auf die Übermittlung per E-Mail zurückzuführen sind. Falls Sie eine
Bestätigung wünschen, fordern Sie bitte den Inhalt der E-Mail als Hardcopy
an.


This e-mail and any attached files are confidential. If you are not the
named addressee or if this transmission has been addressed to you in error,
any disclosure, reproduction, copying, distrubtion, or other dissemination
or use of this communication is prohibited. If you have received this
transmission in error please notify the sender immediately and then delete
this e-mail.

E-mail transmission cannot be guaranteed to be secure or free from error as
information could be intercepted, corrupted, lost, destroyed, arrive late
or incomplete, or contain viruses. The sender therefore does not accept
liability for any errors or omissions in the contents of this message or
any other of such risks which arise as a result of e-mail transmission. If
verification is required, please request a hard copy version.
---------------------------------------------------------------------------------------------
Received on Friday, 3 August 2001 09:19:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:23 GMT