Lists Home |
Date Index |
- From: "Jonathan Borden" <email@example.com>
- To: "Andrew Layman" <firstname.lastname@example.org>, "xml-dev Mailing List (E-mail)" <email@example.com>
- Date: Wed, 21 Apr 1999 12:55:59 -0400
>Jonathan Borden asks what "local scope" means. Consider the example
> <title>The Virgin Queen</title>
> <subject>Queen Elizabeth</subject>
>The elements "title" and "subject" have different meaning in the two cases.
>When the meaning, definition, etc. of a name is determined by its
>that is, when the thing the name denotes is determined by its enclosure,
>that is "local scope".
Ok fine, then my question stands: Isn't the dt:dt attribute a perfectly
good way to distinguish value types *despite* local scope intentions e.g.
<title>The Virgin Queen</title>
And if this objection to the use of elements is sufficiently handled in
this fashion, are there other pressing reasons why values (particularly
table columns) ought be expressed as attributes rather than elements? To me
the most pressing reason to use elements to encode "recordsets" is that in
the absense of a schema decl or DTD, the content can be correctly
interpreted. For example when converting to and from SQL, "int" values
though textualy represented are not 'quoted' while character values are
e.g.: UPDATE table SET intval = 3, charval='3' or
SELECT FROM table WHERE intval = 3 OR charval = '3'
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)