[prev in list] [next in list] [prev in thread] [next in thread]
List: ws-general
Subject: Re: How many XML Schema libraries at ASF is too many XML Schema
From: Benson Margulies <bimargulies () gmail ! com>
Date: 2009-04-07 20:26:34
Message-ID: 61b5d9410904071326r686fb51r9ff210341bd0643a () mail ! gmail ! com
[Download RAW message or body]
It might be worth noting that the original code was written at IBM a long
time ago and then contributed to the ASF :-) How it relates historically to
the Eclipse code I cannot say.
On Tue, Apr 7, 2009 at 11:35 AM, Tom Jordahl <tjordahl@adobe.com> wrote:
> Ø I don't know about you, but I'm left feeling that this conversation
> has ended up revealing that the Xml Schema library isn't pointless.
>
>
>
> +1 – we use it in a few places to read/write Schema and it is very useful.
> Xerces does not do what we want.
>
>
>
> Tom Jordahl
>
>
>
> *From:* Benson Margulies [mailto:bimargulies@gmail.com]
> *Sent:* Tuesday, April 07, 2009 8:35 AM
> *To:* j-dev@xerces.apache.org
> *Cc:* Daniel Kulp; general@ws.apache.org; Lawrence Mandel
> *Subject:* Re: How many XML Schema libraries at ASF is too many XML Schema
> Libraries?
>
>
>
>
>
>
> FYI: Annotations aren't a good example. They are part of the component
> model and do get preserved in Xerces.
>
> Just out of perverse curiosity: an annotation on an attribute group:
> disappears, or pushes down onto the resulting objects?
>
>
>
> > A programmer working, say, with the CXF Aegis binding, can open a
> > book on Xml Schema, and find an API that corresponds to the
> > constructs he or she sees there. In the model you are describing,
> > that person would need to become familiar with the underlying model.
> > I'm not by any means describing this as a fatal flaw, just a
> consideration.
>
> Different goals. Xerces' API represents the abstract model described for
> PSVI and a consumer of that would expect this component view and should
> already be familiar with it given that they are interested in processing
> PSVI.
>
>
> In CXF, which I assume is not a bad model of Axis or even Glassfish/Metro,
> we have a number of schema-ish things going on.
>
> We have to examine schema, since some of the JAX-? standards tell us to
> condition behavior on schema facts. I'm sure we could mine the PSVI-related
> information just as well; there sure aren't any attribute groups at this
> level.
>
> We have to create schema based on code introspection and on @nnotations.
> Here I have some worries: it would not surprise me if somewhere in here was
> a requirement to create a W3C Xml Schema element that is not part of the
> PSVI model. And, in any case, we'd need an API to create.
>
> We support application programmers in specifying the schema for custom
> Java/XML type mappings. They could probably handle PSVI.
>
> I don't know about you, but I'm left feeling that this conversation has
> ended up revealing that the Xml Schema library isn't pointless.
>
>
>
[Attachment #3 (text/html)]
It might be worth noting that the original code was written at IBM a long time ago \
and then contributed to the ASF :-) How it relates historically to the Eclipse code I \
cannot say.<br><br><br><div class="gmail_quote">On Tue, Apr 7, 2009 at 11:35 AM, Tom \
Jordahl <span dir="ltr"><<a \
href="mailto:tjordahl@adobe.com">tjordahl@adobe.com</a>></span> wrote:<br> \
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); \
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p style="text-indent: -0.25in;"><span style="font-family: Wingdings;"><span>Ø<span \
style="font-family: "Times New Roman"; font-style: normal; font-variant: \
normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: \
none; font-stretch: normal;"> </span></span></span>I don't know about you, but \
I'm left feeling that this conversation has ended up revealing that the Xml \
Schema library isn't pointless.</p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">+1 – we use it in a few \
places to read/write Schema and it is very useful. Xerces does not do what we \
want.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Tom Jordahl</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) \
-moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: \
3pt 0in 0in;">
<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> \
Benson Margulies [mailto:<a href="mailto:bimargulies@gmail.com" \
target="_blank">bimargulies@gmail.com</a>] <br> <b>Sent:</b> Tuesday, April 07, 2009 \
8:35 AM<div class="im"><br> <b>To:</b> <a href="mailto:j-dev@xerces.apache.org" \
target="_blank">j-dev@xerces.apache.org</a><br> </div><b>Cc:</b> Daniel Kulp; <a \
href="mailto:general@ws.apache.org" target="_blank">general@ws.apache.org</a>; \
Lawrence Mandel<br> <b>Subject:</b> Re: How many XML Schema libraries at ASF is too \
many XML Schema Libraries?</span></p>
</div><div><div></div><div class="h5">
<p> </p>
<p> </p>
<div>
<blockquote style="border-style: none none none solid; border-color: \
-moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); \
border-width: medium medium medium 1pt; padding: 0in 0in 0in 6pt; margin-left: 4.8pt; \
margin-right: 0in;">
<div>
<p><br>
<tt><span style="font-size: 10pt;">FYI: Annotations aren't a good example. They
are part of the component model and do get preserved in Xerces.</span></tt></p>
</div>
</blockquote>
<div>
<p>Just out of perverse curiosity: an annotation on an
attribute group: disappears, or pushes down onto the resulting objects? </p>
</div>
<blockquote style="border-style: none none none solid; border-color: \
-moz-use-text-color -moz-use-text-color -moz-use-text-color rgb(204, 204, 204); \
border-width: medium medium medium 1pt; padding: 0in 0in 0in 6pt; margin-left: 4.8pt; \
margin-right: 0in;">
<div>
<div>
<p style="margin-bottom: 12pt;"><br>
<span style="font-size: 10pt; font-family: "Courier New";"><br>
<tt>> A programmer working, say, with the CXF Aegis binding, can open a </tt><br>
<tt>> book on Xml Schema, and find an API that corresponds to the </tt><br>
<tt>> constructs he or she sees there. In the model you are describing, </tt><br>
<tt>> that person would need to become familiar with the underlying \
model.</tt><br> <tt>> I'm not by any means describing this as a fatal flaw, \
just a consideration.</tt></span></p>
</div>
<p><tt><span style="font-size: 10pt;">Different goals. Xerces'
API represents the abstract model described for PSVI and a consumer of that
would expect this component view and should already be familiar with it given
that they are interested in processing PSVI.</span></tt></p>
</div>
</blockquote>
<div>
<p><br>
In CXF, which I assume is not a bad model of Axis or even Glassfish/Metro, we
have a number of schema-ish things going on.<br>
<br>
We have to examine schema, since some of the JAX-? standards tell us to
condition behavior on schema facts. I'm sure we could mine the PSVI-related
information just as well; there sure aren't any attribute groups at this \
level.<br> <br>
We have to create schema based on code introspection and on @nnotations. Here I
have some worries: it would not surprise me if somewhere in here was a
requirement to create a W3C Xml Schema element that is not part of the PSVI
model. And, in any case, we'd need an API to create.<br>
<br>
We support application programmers in specifying the schema for custom Java/XML
type mappings. They could probably handle PSVI.<br>
<br>
I don't know about you, but I'm left feeling that this conversation has ended
up revealing that the Xml Schema library isn't pointless.</p>
</div>
</div>
<p> </p>
</div></div></div>
</div>
</blockquote></div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic