|
|
 top
|
  Subject: Validating constraints
Author: paul elzinga
Date: 12 Oct 2005 07:56 AM
|
Problem is solved, thanks a lot!!
>This happens due to the
>different types of the
>attributes used as key and as
>a reference. ID attribute has
>a type "xs:string" and
>"IDActiviteit", for example,
>is missing type declaration,
>so by default it is of type
>"anySimpleType". This is what
>written in specification:
>
>"
>§ 2.2.1.2
>
>The mapping from lexical space
>to value space is unspecified
>for items whose type
>definition is the simple
>ur-type definition.
>Accordingly this specification
>does not constrain processors'
>behaviour in areas where this
>mapping is implicated, for
>example checking such items
>against enumerations,
>constructing default
>attributes or elements whose
>declared type definition is
>the simple ur-type definition,
>checking identity constraints
>involving such items."
>
>So, if you want all processors
>to provide same results you
>have
>to declare attributes used as
>a references as "xs:string"
>attributes.
>
>At the same time several
>validators will perform
>mapping automatically, for
>example .NET, XSV or Xerces-J.
>You can pick one you want to
>use from the dropdown list
>attached to the "Validate
>Document" toolbar button.
|
|
|
|
next
exampleBV.zip