Re: Problem inserting XML with DTD

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello Tobias,

thank you for the response.

Unfortunately not using DTDs is currently not an option (large set of
technical documentation from customer, who is not prepared for switching to
schemas).

So if we decide to work with SQL-Server we will need some kind of
workaround:
usage of partial schemas for indexing (performance) purposes
storage of XML with resolved entities
....

Anyway, a very important requirement is to reproduce an identical copy of
the original document on store/retrieve operations. We will therefore need
some type of replace/restore operations (the way you mentioned in your
response). As an alternative we could try to store a copy of the original
XML to a simple "varchar" column. The first solution has the disadvantage of
producing extra computational overhead. It also ev. manipulates the original
document structure (ev. infuencing search operations). The second solution
produces redundant data with possible problems on data modification
activities.

Kind regards,
Erwin


"Tobias Thernström" <ttnospam@xxxxxxxxxxxxxx> schrieb im Newsbeitrag
news:ufcBW6pbGHA.4716@xxxxxxxxxxxxxxxxxxxxxxx
Hello Erwin,

Since DTDs are not supported by SQL Server (but XML Schemas are :-) ) you
will have to replace the &uuml; with something else (like <uuml/>, &#252;
or ü) and then replace it again on the client side (with &uuml;) when you
fetch it back to the client.

You should however consider not using DTDs.

HTH
/Tobias



.

Relevant Pages

  • Re: XSL for recursive transformation
    ... I agree that schemas are taking longer to find their way in than might have been expected, partly because they're a syntax only a database expert or computer science geek could love. ... properly investigating the possibility of adding datatyping to DTDs ... XML-Data folks saw the market for the syntax (and that's something else ...
    (comp.text.xml)
  • Re: XSL for recursive transformation
    ... I agree that schemas are taking longer to find their way in than might have been expected, partly becuase they're a syntax only a database expert or computer science geek could love. ... If we'd designed XML completely before releasing it to the public, we would have started with the infoset, then designed the syntax and APIs from that, Instead the W3C started with the syntax and a known-inadequate schema language (DTDs), and has build everything out from there. ... The upside is that folks had a chance to start using XML much earlier, and we've gotten some benefit from seeing which directions everyone has gone with it. ...
    (comp.text.xml)
  • Re: Namespace question
    ... As others have said, one DTD per document, made up of an External Subset and an Internal Subset. ... If you're working with namespaced documents, do not waste time studying DTDs; go directly to schemas, or drop back to well-formed rather than validated. ...
    (comp.text.xml)
  • Re: Famous XML cliches
    ... [Bear in mind that by "it" I am referring to the belief that using XML ... Virtually everyone in the e-commerce field who took one look at DTDs ... documents will have to use W3C Schemas because DTDs will be dead soon. ...
    (comp.text.xml)