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

Sequence <was> Access Languages ...

• From: "Mark L. Fussell" <fussellm@a...>
• To: xml-dev@i...
• Date: Sat, 22 Nov 1997 01:33:43 -0800 (PST)

Rick Jelliffe <ricko@a...> wrote:
> I think you miss what is perhaps *THE* most important thing that SGML 
> content models represent:  sequence.
> This is one of the essential distinguishing features of SGML.
> If I have 
> 
> <p>Refer also to 
> <citation>
>         <title>XML draft</title>
>         <text>at</text>
>         <url>http://www.w3c.org/TR</url>
> </citation> for more info.</p>
> 
> then the sequence of elements and data in to citation element 
> are vitally critical.  Sequence is not an artifact of formatting,
> in many cases, but as intrinsic to the data as encapsulation
> and so on.  
[SNIP to possible Content Model]
>        <!ELEMENT citation   ( title, text, url)>

I think your example shows the opposite.  There is no information change 
between any of the orderings within the citation:  <title><text><url> vs. 
<title><url><text> vs. <url><title><text> etc.  You may consider the 
desired presentation and encoding order to be only the first but that 
would be a view onto the information and not a property of the 
information itself.  You could alternatively define an attribute that 
says citations look good in English in that particular order.  Or maybe 
the 'at' should be derived and the content model is simply:
         <!ELEMENT citation   ( title & url)>

This works well with your next example too:
>       <!ELEMENT citation   ( title, text, name, text, url )>
becomes:
        <!ELEMENT citation   ( title & editor? & url )>

Depending on whether the editor is included or not, different text would 
be generated at presentation.  

The generated text could still be encoded in SGML but as separate 
information:
<CitationPresentationInfo>
    <urlPrefix>at</urlPrefix>
    <editorPrefix>edited by</editorPrefix>
</CitationPresentationInfo>

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.

--Mark 
mark.fussell@c...


  i   ChiMu Corporation      Architectures for Information
 h M   info@c...         Object-Oriented Information Systems
C   u    www.chimu.com         Architecture, Frameworks, and Mentoring

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...)

• Prev by Date: Recipes for Information
• Next by Date: Re: Integrity in the Hands of the Client
• Previous by thread: Recipes for Information
• Next by thread: Re: Sequence <was> Access Languages ...
• Index(es):
  • Date
  • Thread