This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: markup suggestions for protocol descriptions?
- To: docbook at lists dot oasis-open dot org
- Subject: Re: DOCBOOK: markup suggestions for protocol descriptions?
- From: Norman Walsh <ndw at nwalsh dot com>
- Date: Thu, 30 Mar 2000 11:56:52 -0500
- References: <NDBBIIHEHKELNKJMKEKGOEFECDAA.gershon@mainsoft.com>
- Reply-To: docbook at lists dot oasis-open dot org
/ "Gershon Leib Joseph" <gershon@mainsoft.com> was heard to say:
| information you supplied, you could perhaps add something like the following
| to a DocBook driver file (untested):
|
| <!ELEMENT packet - - ( title, field+ ) >
|
| <!ELEMENT field - - ( type, size, name, required, range ) >
|
| <!ELEMENT (type | size | name | range) #PCDATA >
|
| <!ELEMENT required - o EMPTY >
| <!ATTLIST required yesno "no" >
|
| Now authoring will be a breeze. You have to add support for these new
| elements to your stylesheets.
Right. So the question is, what *structure* do these binary messages
actually have. If the preceding fragment captures them well, that may
be the way to go. If it doesn't, what structure do they have?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Happiness is a how, not a what; a
http://www.oasis-open.org/docbook/ | talent, not an object.--Herman
Chair, DocBook Technical Committee | Hesse