Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | richard@cogsci.ed.ac.uk (Richard Tobin) |
|---|---|
| Newsgroups | comp.text.xml |
| Subject | Re: Specifying an executable string in XML terms |
| Date | 2014-06-29 11:40 +0000 |
| Organization | HCRC, University of Edinburgh |
| Message-ID | <lootus$15tk$1@macpro.inf.ed.ac.uk> (permalink) |
| References | <lon0oi$371$1@speranza.aioe.org> |
In article <lon0oi$371$1@speranza.aioe.org>, Victor Porton <porton@narod.ru> wrote: ><command>python %s</command> ><command>python <script/></command> If that's all there's ever going to be, it doesn't really make much difference. But if you plan to extend it in the future, the second has advantages. The first implies an uninterpreted string, with natural extension only to other C-style formats. The second would allow variants such as <file/> or <date/> or <string/> which might be subject to different checks or escaping. It also allows additional structure (e.g. an attribute <file writable="yes"/>). -- Richard
Back to comp.text.xml | Previous | Next — Previous in thread | Find similar
Specifying an executable string in XML terms Victor Porton <porton@narod.ru> - 2014-06-28 21:15 +0300
Re: Specifying an executable string in XML terms Victor Porton <porton@narod.ru> - 2014-06-28 21:19 +0300
Re: Specifying an executable string in XML terms Peter Flynn <peter@silmaril.ie> - 2014-07-13 23:44 +0100
Re: Specifying an executable string in XML terms richard@cogsci.ed.ac.uk (Richard Tobin) - 2014-06-29 11:40 +0000
csiph-web