This is the mail archive of the docbook@lists.oasis-open.org mailing list for the DocBook project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: markup suggestions for protocol descriptions?


/ "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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]