[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] XML2.0: Comments (Was: Towards XML 2.0)
- From: Dave Pawson <davep@dpawson.co.uk>
- To: "XML Developers List" <xml-dev@lists.xml.org>
- Date: Sun, 5 Dec 2010 14:25:32 +0000
On Sun, 5 Dec 2010 14:10:16 -0000
"Pete Cordell" <petexmldev@codalogic.com> wrote:
> Original Message From: "Dave Pawson"
>
> >> There seems to be two main uses of comments in XML today which is
> >> aligned with the two schools of thought in this thread:
> >>
> >> 1.] Simply commenting out code or adding TODOs etc. - similar use
> >> to standard code comments.
> >> ...
>
> > With a KISS hat on, Use Mikes idea,
> > and don't parse them any differently to any other element.
> > That would answer the basic need, 1 above.
>
> But the problem I see with Mike's <xml:comment/> proposal is that it
> implies that the body of the comment is well-formed. I think this is
> too onerous if you're trying to hack stuff out to see where it's
> broken, and likely to push someone over the edge.
More included unecessary complexity Pete?
That's why I'm suggesting a -1. Removes parser complexity
and user headaches.
>
> That's what I tried to convey in my example; where the start tag and
> end tag don't match:
>
> <!-- Ignore this until I fix it --
> <MyElement>
> <!-- The price is changed by the controller -->
> <price>100.00</price>
> </BrokenMyElement> <!-- Is this the problem? -->
I'm suggesting fix it now, not later?
No extra effort, just when you fix it.
--
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]