Re: SD1 - Short End Tags [fmt]

That would work if the transmission is long enough.  Of course, it would make
my life (and that of the DPH) more complicated.  Isn't this possible:

<?XML version="1.0" RMD='INTERNAL'?>
<!doctype bogus [
<!entity of "<firstname>">
<!entity cf "</firstname>">
<!entity ol "<lastname>">
<!entity cl "</lastname>">
]>
<author>
  &of;foo&cf;
  &ol;bar&cl;
</author>

Then I could have the parse worry about it, and not me.  Here, including some
of the DTD is even shorter than an alternative.

Matthew Fuchs
matt@wdi.disney.com

On May 20,  2:03pm, lee@sq.com wrote:
> Subject: Re: SD1 - Short End Tags [fmt]
> > I would much rather have 8 versions of:
> > > <author>
> > > 	<firstname>foo</firstname>
> > > 	<lastname>bar</lastname>
> > > </author>
> >
> > than have each server alpha-rename the tags to different
> > incomprehensible tags,
>
> Another approach is to have a header,
> <header>
>  <field element="a" name="firstname">First Name</field>
>  <field element="b" name="lastname">Last Name</field>
>  <field element="c" name="author">Warpper for Author record</field>
>  <field element="d" name="id">Unique ID for database key</field>
> </header>
> <body>
> <c><a>Parcival</a><b>Snitterpoop</b><d>1</d></c>
> <c><a>Priscilla</a><b>Winterbottom</b><d>2</d></c>
>
> and so forth.
>
> This maps conveniently into typesetting tables, and also into the
> common variant of CSV files in which the first line lists the field names:
>     firstname,lastname,author,id
>     Parcival,Snitterpoop,1
>     Priscilla,Winterbottom,2
> in which you can't actually distinguish the first line from the others
> except by human understanding and inspection (ugh!).
>
> I have added textual descriptions in the header; these could be omitted if
> unavailable, with the possibility of making the "field" element EMPTY.
>
> Lee
>
>-- End of excerpt from lee@sq.com



--

Received on Tuesday, 20 May 1997 17:07:01 UTC