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

Re: Sequence <was> Access Languages ...

• From: "Rick Jelliffe" <ricko@a...>
• To: "Mark L. Fussell" <fussellm@a...>, <xml-dev@i...>
• Date: Sun, 23 Nov 1997 02:43:39 +1100

 
> From: Mark L. Fussell <fussellm@a...>

> I am not saying sequence is unimportant, but I think SGML is overly 
> focused on it (from an IM perspective) because it comes from a 
> paper/linear background.  Information is rarely linear: it is only time 
> that is, which has caused some media [and the humans who use them] to be 
> (mostly) linear also.  It can be difficult to break that linear 
> assumption when it doesn't apply if your tools keep reinforcing it.

But do you think HTML would have become a popular markup language if its DTD
was like this?

<!ELEMENT html 
	( h1*, h2*, h3*, p*, I*, table*, tr*, td*, th*)>


This is reductio ad absurdum of what you are saying.  A DTD where all
sequence information is made explicit.

In such a DTD, all the elements would have IDs, and either some
external specification to set the sequence/containment, or 
a "next" IDREF attribute.   

SGML is not overly focused on sequence.  Sequence is such a basic
property of text that having to always mark it up explicitly is just 
bizarre.   

Of course boilerplate text can be removed and added. And of course 
chunks in one part can be usefully reflected into another part. 
But sequence is important because it is a prime property of language.
Databases contain words and pictures and various fragments.  However
SGML/XML must be a format to allow these to be placed as cohesive
language-mediating documents.

If people just want a database dump format for nice relational tables,
comma-delimiter formats are available and attractive.  But when they have
text which they don't want to have desequenced, SGML/XML can be useful. 

I think the other big trouble with trying to view SGML/XML as a poor database
dump format, is that when you get too far from a markup paradigm, you 
have to involve programmers rather than writers.  Just folks can write
HTML, at a pinch. If you go too much to a database mentality, you move
to requiring custom-tools for data entry, rather than simple text-editors. 


Rick Jelliffe

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: Sequence <was> Access Languages ...
    • From: "Mark L. Fussell" <fussellm@a...>

• Prev by Date: Is XDEV useful? (was re: XDEV proposals)
• Next by Date: Re: Is XDEV useful? (was re: XDEV proposals)
• Previous by thread: Sequence <was> Access Languages ...
• Next by thread: Re: Sequence <was> Access Languages ...
• Index(es):
  • Date
  • Thread