From: Dick Hamilton Date: Mon, 15 May 2006 21:47:59 +0000 (+0000) Subject: Copy edit pass over the version numbering description. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=afed59ff68c507162a22c976caba02575d837c80;p=docbook-dsssl Copy edit pass over the version numbering description. --- diff --git a/docbook/relaxng/docbook/howto/howto.xml b/docbook/relaxng/docbook/howto/howto.xml index c42397037..8dbb22ba5 100644 --- a/docbook/relaxng/docbook/howto/howto.xml +++ b/docbook/relaxng/docbook/howto/howto.xml @@ -1599,14 +1599,14 @@ db.spacing.enumeration |= "large"]]> DocBook V5.0 is not tightly coupled with some particular validation technology like DTDs. This also means that DocBook V5.0 -documents doesn't have to (and usually really doesn't) start with -document type declaration (<!DOCTYPE…>) which can specify schema -(DTD) to use. Instead, DocBook V5.0 instance can be easily -distinguished from other XML vocabularies by using elements in +documents don't have to (and usually don't) start with a +document type declaration (<!DOCTYPE…>) to specify the schema +(DTD) to use. Instead, DocBook V5.0 instances can be easily +distinguished from other XML vocabularies by using elements in the http://docbook.org/ns/docbook namespace. This namespace is -enough to distinguish DocBook from other XML based formats. But -DocBook schema evolves over the time and there are several versions of -DocBook (e.g. 3.1, 4.2, 4.5 and 5.0). Since DocBook version 5.0 the +enough to distinguish DocBook from other XML based formats. But the +DocBook schema evolves over time and there are several versions of +DocBook (e.g. 3.1, 4.2, 4.5 and 5.0). Since DocBook version 5.0, the actual version used is indicated in the version attribute on a root element. @@ -1616,19 +1616,20 @@ class="attribute">version attribute on a root element. ]]> Future versions of DocBook documents will start with the same -markup, only version number will be raised like 5.1 or 6.0. The -namespace will remain same until semantic of elements will change in -a backward incompatible way which is very unlikely to happen. +markup, except the version number will be raised, for example to 5.1 +or 6.0. +The namespace will remain the same until the semantics of the elements +change in a backward incompatible way, which is very unlikely to happen. -If you create DocBook schema customization you must change If you create a DocBook schema customization you must change the version attribute to distinguish your -customization from the official DocBook. Namespace -change is not recommended because it would break all processing -tools. Remember that changing namespace is the same as renaming all +customization from the official DocBook. Changing the +namespace is not recommended because that would break the processing +tools. Remember that changing namespaces is the same as renaming all elements in the namespace. -Your own version identifiers should use the following syntax in -order to record their DocBook derivation: +When you customize the schema, use the following syntax to +identify your DocBook derivation: base_version-[subset|extension|variant] [name[-version]?]+ @@ -1639,7 +1640,7 @@ order to record their DocBook derivation: 5.0-variant ASMBook-2006 5.0-extension MathML-2.0 SVG-1.1 -The first part of version identifier is a version number of the +The first part of the version identifier is the version number of the DocBook schema from which you derived your customization. If your schema is a proper subset, you can advertise this status @@ -1649,8 +1650,8 @@ this status by using the extension keyword. If you'd rather not characterize your variant specifically as a subset or an extension, use the variant keyword. -After these keywords you can place whitespace separated list of -customization identifiers. Each name can be optionally followed by its +After these keywords you may add a whitespace separated list of +customization identifiers. Each name may be optionally followed by its version number.