[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Simplify XML Now?


perc
/ "cr88192" <cr88192@h...> was heard to say:
| ----- Original Message ----- 
| From: "Bullard, Claude L (Len)" <len.bullard@i...>
| To: "'Oleg Tkachenko'" <oleg@t...>; "Michael Champion"
| <michaelc.champion@g...>
| Cc: "Robin Berjon" <robin.berjon@e...>; <xml-dev@l...>
| Sent: Tuesday, November 23, 2004 8:14 AM
| Subject:  Simplify XML Now? (Was RE:  Re: Hostility
| to "binary XML" (was Re:  XML 2004 weblog items?))
|
|> Norm makes good points.  Derek has made good points in his blogs.
|> That is what makes me think the time has come to consider this.
|> There is sufficient shared experience to do it just as there
|> was when it was done to SGML.
|>
|> It seems that is what experience teaches in every creative
|> endeavour:  what to leave out.
[...]
| I feel a little unsure of merging in qnames, and his proposed syntax
| was just ugly. others were proposing overloading '&'. at least this
| looks better imo, but seems to solve one issue with another.

Yeah, & is better.

| I think someone else suggested using '%'.

I was trying specifically not to add a new metacharacter. Adding a new
metacharacter has the potential to break a lot of existing documents.
I was explicitly trying to avoid that.

| probably %% could be used as an escaped form of %.

That'd be very non-XML. &perc; would seem more palatable. We don't
need a new paradigm for escaping, IMHO.

| &:prefix:name;
| imo, could make sense for a kind of entity.
| entities could be namespace qualified like everything else, and if the
| app doesn't recognize a character's namespace, it is sol, and will
| have to deal with it somehow (the box character comes to mind).
| ok, so the parser sees this, and possibly resolves the mark to some
| specific character (eg: internally parts of the character space could
| be defined dynamically), and inserts that character in place of the
| original mark, or failing that, inserts some default.

In my ramblings, &:prefix:name; was not an entity, it was a QName.
Yes, you could use QNames for entities (in fact, I've implemented it
in XSLT 2.0 and may write a SAX filter to do it, just for fun) but
they're also used in XPath expressions and other places where they
aren't macros of any kind.

| I would personally just rather stick with the predefined ones. custom
| entities are probably necessary somehow, oh well.

Yep.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@n...> | Blessed is he who expects nothing, for
http://nwalsh.com/            | he shall never be disappointed.-- Pope

PGP signature


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.