I think of it more like deprecating the DTD in favor of XSD; but I am known for
unique views on deprecation :)
-- Sent from my Palm Pre
st...@hibernate.org
http://hibernate.orgOn Aug 20, 2010 10:52 AM, Paul Benedict
wrote:
Interesting. That is a good way to get the commu
Interesting. That is a good way to get the community testing it out. In
fact, perhaps you can label the XSD feature as "caveat emptor" (pun) until
it rolls out officially in 4.0?
On Fri, Aug 20, 2010 at 10:48 AM, Steve Ebersole wrote:
> Do we offer both for 3.6 to start working out any kinks in t
Do we offer both for 3.6 to start working out any kinks in the XSD for
4? I think that seems reasonable, provided we are good about not doing
DTD changes after 3.6.0.Final.
On Fri, 2010-08-20 at 09:27 -0500, Paul Benedict wrote:
> I don't vote for keeping them in sync. DTDs can't compete with the
I don't vote for keeping them in sync. DTDs can't compete with the
validation of XSD. I would favor making this a 4.0 feature.
Paul
On Fri, Aug 20, 2010 at 7:20 AM, Steve Ebersole wrote:
> *If* we are going to keep both then we need to keep them in-synch and so
> I'd prefer a java or command li
*If* we are going to keep both then we need to keep them in-synch and so
I'd prefer a java or command line tool that we could use to automate the
process (obviously if we drop dtd for xsd this is not a concern).
I had seen both Trang as well as the w3c tool. I guess more I was
asking if anyone
On Thu, 19 Aug 2010 22:07:31 +0200, Steve Ebersole
wrote:
> Any objections to either converting to XSD completely or publishing in
> both formats?
+1 for XSD only. Not sure if there is any use in keeping the DTD.
> Anyone recommend a good DTD -> XSD tool?
Oxygen can do it. That would be my f
Any objections to either converting to XSD completely or publishing in
both formats?
What I'd really like is to be able to parse and validate a mapping
document in separate steps. The validation would come from
javax.xml.validation package. However that package does not support
DTD, only XSD.