Subject: Re: DTD element ordering From: SNOJOW@MVS.sas.com (Jim Ward) Date: Mon, 03 Apr 1995 13:05:07 -0700 (PDT)
How the Web Was Won
Subject: Re: DTD element ordering From: SNOJOW@MVS.sas.com (Jim Ward) Date: Mon, 03 Apr 1995 13:05:07 -0700 (PDT)
Sender: MVS NNTP News Reader 
Message-ID: <19950411142511SNOJOW@MVS.sas.com>
X-Nntp-Posting-Host: sdcmvs.mvs.sas.com
Reply-To: snojow@mvs
References: <1995Mar28.225425.29439@rsg1.er.usgs.gov>
Organization: SAS Institute Inc.
Lines: 44

In article <1995Mar28.225425.29439@rsg1.er.usgs.gov>,
peter@geochange.er.usgs.gov (Peter N. Schweitzer) writes:
 
>I have a DTD with an element like this:
>
>
>
>This means that NAME must contain A and C, and may contain any number
>of B's.  Further, it means that the elements A, B, and C can occur
>in any order (because I used '&' rather than ',' to separate them).
>However, I observe (using sgmls 1.1.91) that if B is repeated, all
>occurrences of B must be together, i.e. I get errors from
>
>
>a
>b
>c
>b again
> 
>
>Is there any way to fix my element declaration so that the elements
>of type B can occur in any order just like the elements A and C?
 
Well, my knowledge of SGML is very limited, but it seems to me that
a fairly simple, albeit very possibly ambiguous, solution is:
 
  
 
If this really is ambiguous, I'd appreciate a succinct explanation as
to why!
 
--
Jim Ward             | My wife and I were happy for twenty years.  Then
SAS Institute Inc.   | we met.
SAS Campus Drive     |
Cary, NC 27513       |             - Rodney Dangerfield
 
--
Jim Ward            | If all of the people who go to sleep in church
SNOJOW@MVS.SAS.COM  | were laid end to end, they'd be a lot more
SAS Institute Inc.  | comfortable.
SAS Campus Drive    |
Cary, NC 27513      |
(919) 677-8000      |


From rballard@cnj.digex.net Fri Apr 11 19:24:30 1995
Status: RO
X-Status: 
Newsgroups: comp.text.sgml
Path: news3.digex.net!news2.digex.net!howland.reston.ans.net!ix.netcom.com!netcom.com!mlt