Hi,
Consider the follow piece of schema:
<xsd:element name="B3" type="xsd:NCName" sql:someparameter="true"/>
Since there is no child annotation, there is no way in the XSModel to
recover the non-schema attribute sql:someparameter. If however, the schema
was:
<xsd:element name="B3" type="xsd:NCName" sql:someparameter="true">
<xsd:annotation>
<xsd:documentation>Annotation documentation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
then the attribute sql:someparameter will be available on a XSAnnotation in
the XSModel. The fgXercesGenerateSyntheticAnnotations feature is designed
to synthesize annotations so that non-schema attributes are available in
the XSModel on a XSAnnotation even when there are no child annotations in
the original schema.
Regards,
David A. Cargill
XML Parser Development
IBM Toronto Lab
(905) 413-2371, tie 969
[EMAIL PROTECTED]
"Elisha Berns"
<[EMAIL PROTECTED]
.org> To
<[email protected]>
09/13/2005 03:00 cc
PM
Subject
RE: FW: Enumeration Annotations
Please respond to
c-dev
>From the documentation for fgXercesGenerateSyntheticAnnotations:
"Enable generation of synthetic annotations. A synthetic annotation will
be generated when a schema component has non-schema attributes but no
child annotation."
Well, to be honest, I haven't a clue what this means. Can somebody on
the Xerces team give an example of what this means?
Elisha
> -----Original Message-----
> From: Jeroen N. Witmond [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 13, 2005 8:29 AM
> To: [email protected]
> Subject: Re: FW: Enumeration Annotations
>
> > I have come across several XSD schemas that also document
enumeration
> > elements with annotations. Xerces accepts these as valid XSD on one
> > hand, but on the other doesn't create any annotation object(s) for
the
> > enumeration(s).
>
> I recently and accidentally came across the XercesDOMParser Supported
> Features, one of these being setGenerateSyntheticAnnotations. (See
> http://xml.apache.org/xerces-c/program-dom.html#DOMBuilderFeatures for
> details.) I'm just guessing, but could this be applicable to your
case?
>
> Jeroen.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
