Cart
[Home] [By Thread] [By Date] [Recent Entries]
John L. Clark <jlc6@p...> writes: > > On Tue, Oct 26, 2004 at 04:22:22PM -0500, Hunsberger, Peter wrote: > > > > Ok. Any parties interested in posting their favorite five bad > > > > problems with XML in order here? I wonder what the > consensus is > > > > on the top two. (XML, not XML apps like > > > > XSD.) > > Man, how can I resist the "come up with your own list!" urge? > > > Since I don't have to write any tools to actually support DTDs they > > actually sort of, almost, help me more than they hinder. Maybe Len > > needs to divide the question between two (more?) camps: 1) > XML users, > > 2) XML tool builders? > > I think this might be a useful distinction. I think I > primarily fall into the former category. Here's my shot at a list: > > 1. Only one tree per file allowed > 2. Limitations of trees on expression[0] > 3. Remembering XML namespace *URI values* > 4. Getting character references right > 5. Lack of nesting of comments > > Take care, > > John L. Clark > > [0] For (a very simple introductory) example, I can't say the > following: > > <p>Some content, <em>some of which is emphasized, <ins>and > furthermore,</em> some of which has been recently > inserted.</ins></p> > > Where the "elements" have "the same" semantics as in HTML, only I > want to express the addition of content across an element > boundary. > Hah. Welcome to the "After Xquery, are we done?" thread and the discussion on tree's vs. graphs...
|
