This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Including OS Version information on DocBook elements
- To: docbook at lists dot oasis-open dot org
- Subject: Re: DOCBOOK: Including OS Version information on DocBook elements
- From: "Fred L. Drake, Jr." <fdrake at acm dot org>
- Date: Tue, 21 Dec 1999 12:16:39 -0500 (EST)
- Cc: bortzmeyer at debian dot org, doc at freebsd dot org, sgml-tools at via dot ecp dot fr, dssslist at mulberrytech dot com, oswg-discuss at oswg dot org
- References: <19991221122224.B75275@catkin.nothing-going-on.org>
- Reply-To: docbook at lists dot oasis-open dot org
Nik Clayton writes:
> I've set followups to the FreeBSD Doc. Proj. mailing list, doc@freebsd.org.
> You don't need to be a subscriber to post there, and most people are in
> the habit of doing 'Reply to all', so you should stay in the discussion.
I'm definately not on that list, so a "Reply to All" or CC to me
would be appreciated.
> In the FreeBSD and Linux documentation communities the problem of how to
> represent information that is only appropriate for one release of the code,
> or a limited range of releases, comes up occasionally. The common link is
...
> The last time we discussed this, the general consensus was to add three
> attributes to every element in DocBook in our customisation layers.
>
> osversionmin
> osversionmax
> osversionequal
This is probably pretty reasonable. My concern is that the
attribute names imply that the constructs are only useful for OS
versioning. I think this is likely to be useful for any large system;
perhaps different names should be chosen?
You may also want an attribute that allows specific version labels
(NMTOKENS instead of NMTOKEN); perhaps "versionequal" should be
"versionin"?
-Fred
--
Fred L. Drake, Jr. <fdrake at acm.org>
Corporation for National Research Initiatives