Crashing when saving as .xml

[Stamm, David-P45904]

Jeremy - 

With the \.dtd we're required to use, many of the attributes of these
top-level (that is, chapter-level) elements are optional.  So, yeah.  Go
figure.

Thanks.
Dave Stamm
Publications Specialist, Senior Staff
General Dynamics C4 Systems, Inc.
Battle Management Systems Division
1700 Magnavox Way, Suite 200       We'll hit your targets from here.(tm)
Fort Wayne, Indiana  46804-1552
US
tel:  260-434-9620
fax:  260.434.9606
dave.stamm at gdc4s.com
http://www.gdc4s.com/

This message and / or attachments may include information subject to
GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be
accessed only by authorized recipients.  Use, storage and transmission
are governed by General Dynamics and its policies.  Contractual
restrictions apply to third parties.  Recipients should refer to the
policies or contract to determine proper handling.  Unauthorized review,
use, disclosure or distribution is prohibited.  If you are not an
intended recipient, please contact the sender and destroy all copies of
the original message.

-----Original Message-----
From: Jeremy H. Griffith [mailto:jeremy at omsys.com] 
Sent: 2010-January-19-Tuesday 16:11
To: FrameMaker user's list posting
Cc: generic668 at yahoo.ca; Stamm, David-P45904
Subject: Re: Crashing when saving as .xml

On Tue, 19 Jan 2010 15:30:26 -0500, "Stamm, David-P45904" 
<Dave.Stamm at gdc4s.com> wrote:

>Yes and no:  in our context, in both problematic files, and in other 
>five files, the top-level elements have id attributes with values = <no

>value>.

And they still validated???  They shouldn't have; that would be a bug in
the validator.  In XML, the ID attribute cannot be empty, and must start
with a letter (after which it can contain only letters, digits, hyphens,
and underscore).  You can just make it "x", or else remove it entirely.


Also note that within any particular XML file, IDs must be unique; it's
OK for IDs in different files to be the same.

HTH!

-- Jeremy H. Griffith, at Omni Systems Inc.
  <jeremy at omsys.com>  http://www.omsys.com/