From: Norman Walsh Date: Fri, 13 Sep 2002 14:56:19 +0000 (+0000) Subject: Renamed and updated X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f0d5a4c6f55d5d0ff31afa8f59d81df607227eff;p=docbook-dsssl Renamed and updated --- diff --git a/docbook/svg/spec/svg.xml b/docbook/svg/spec/svg.xml deleted file mode 100644 index 3f74d6034..000000000 --- a/docbook/svg/spec/svg.xml +++ /dev/null @@ -1,257 +0,0 @@ - - - -]> -
- - -The DocBook SVG Module -Version 1.0 Beta 2 -OASIS DocBook Technical Committee - - - NormanWalsh - - Sun - Sun Microsystems, Inc. -
Norman.Walsh@Sun.COM
- - - -21 May 2002 - -$Id$ - -20012002 - -The Organization for the Advancement of Structured Information -Standards [OASIS]. All Rights Reserved. - - -This document and translations of it may be copied and furnished to -others, and derivative works that comment on or otherwise explain it -or assist in its implementation may be prepared, copied, published and -distributed, in whole or in part, without restriction of any kind, -provided that the above copyright notice and this paragraph are -included on all such copies and derivative works. However, this -document itself may not be modified in any way, such as by removing -the copyright notice or references to OASIS, except as needed for the -purpose of developing OASIS specifications, in which case the -procedures for copyrights defined in the OASIS Intellectual Property -Rights document must be followed, or as required to translate it into -languages other than English. - -The limited permissions granted above are perpetual and will not be -revoked by OASIS or its successors or assigns. - -This document and the information contained herein is provided -on an AS IS basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE -INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED -WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. - - - -Status of this Document - -This is a working draft constructed by the editor. It is not -an official committee work product and may not reflect the consensus -opinion of the committee. - - - - - -Abstract - -DocBook is a general purpose XML and SGML document type -particularly well suited to books and papers about computer hardware -and software. SVG (Scalable Vector Graphics) is an XML document type -designed for describing two-dimensional graphics (vector graphic -shapes, images, and text). - -This module integrates SVG into DocBook, allowing elements from the -SVG namespace to be used in DocBook documents. - - - - - Beta Release 2 - 21 May 2002 - - - - -
-Introduction - - -is a general purpose XML and SGML document type particularly well -suited to books and papers about computer hardware and software -(though it is by no means limited to these applications). - - - -(Scalable Vector Graphics) is an XML document type designed for describing -two-dimensional graphics (vector graphic shapes, images, and text). - -This module integrates SVG into DocBook, allowing elements from the -SVG namespace to be used in imageobjects. - -The DocBook -Technical Committee maintains the DocBook schema. - -The W3C maintains SVG. - -The 1.0 Beta 2 release of this module is based on the -SVG 1.1 Candidate Release -DTD. - -The DocBook Technical Committee welcomes bug reports and -requests for enhancement (RFEs) from the user community. The current list -of outstanding requests is available through the -SourceForge -tracker -interface. This is also the preferred mechanism for submitting new requests. -Old RFEs, from a previous legacy tracking system, are -archived -for reference. - -
- -
Terminology - -The key words must, must -not, required, -shall, shall not, -should, should not, -recommended, may, and -optional in this &standard; are to be -interpreted as described in . Note that for -reasons of style, these words are not capitalized in this -document. - -
- -
-The DocBook SVG Module V1.0b2 - -This module integrates SVG into DocBook by incorporating the SVG -V1.1 DTD using a namespace prefix and extending the content model of -DocBook's imageobject element to allow those -elements to occur. - -
-Usage - -To use this module, specify the public and system identifiers of this -module in your document type declaration. For example, to use this module -to write a book, use the following document type declaration: - -]]> - -Naturally, you can include an internal subset if you wish. - -This module declares svg: as the namespace -prefix for SVG. If you wish to change that prefix, you may declare an alternative -by changing the declaration of the parameter entity SVG.prefix. - - -For example, to write an article using this module and to specify that -the namespace prefix for SVG elements should be s:, you could -use the following document type declaration: - - -]>]]> - -To incorporate this module into a higher-level customization layer, use the -public and system identifiers of this module in your customization layer. For -example: - - -%docbooksvg;]]> - -
- -
-Limitations - -This module is DTD-based. DTDs and -do not work together with perfect harmony. In particular, although you -can change the namespace prefix used for SVG diagrams on a -per-document basis, you cannot change it on a per-diagram basis. You -simply cannot use svg: as the prefix on one diagram -and s: as the prefix in another diagram within the -same document. Such a document may be well-formed, and many XML tools -may process it correctly, but it cannot be validated against this -module's DTD. - -The SVG module overrides the declaration of the imageobject -element. In order to write a customization layer that also changes the declaration -of imageobject, that customization layer must -disable docbook.svg.imageobject.element -before including the SVG module. -
-
- -
Release Notes - -This module is a customization layer on top of DocBook XML V4.2 -Candidate Release 2. The DocBook Candidate Release specification may -change without warning. This module will not (can not) be published in -final form until DocBook V4.2 is officially published. - -This module is currently based on the -SVG 1.1 Candidate Release -specification. The Candidate Release specification may change without -warning. This module will not (can not) be published in final form until -the SVG 1.1 Recommendation is released. -
- - -OASIS DocBook Technical Committee - -The following individuals were members of the committee during -the formulation of this &standard;: - - -Dennis Evans -Paul Grosso (prospective) -Dick Hamilton -Nancy (Paisner) Harrison -Sabine Ocker -Michael Sabrio -Michael Smith -Tim Teebken (prospective) -Norman Walsh (Chair, Editor) - - - - -References - -Normative - - - - - - - - - - -
diff --git a/docbook/svg/spec/wd-docbook-svg.xml b/docbook/svg/spec/wd-docbook-svg.xml new file mode 100644 index 000000000..3c1c1d52c --- /dev/null +++ b/docbook/svg/spec/wd-docbook-svg.xml @@ -0,0 +1,356 @@ + + + +]> + +
+ + +wd-docbook-svg +1.0-CR1 + +XML +HTML +PDF + +http://www.oasis-open.org/docbook/specs + +The DocBook SVG Document Type + + + + NormanWalsh + + Sun + Sun Microsystems, Inc. +
Norman.Walsh@Sun.COM
+ + + + +12 Sep 2002 + +20012002 +OASIS Open, Inc. All Rights Reserved. + + + +DocBook SVG Document Type is a modular superset of DocBook XML V4.2. +It is a DocBook extension to allow Scalable Vector Graphics (SVG) in +DocBook images. SVG is an XML document type designed for describing +two-dimensional graphics (vector graphic shapes, images, and +text). + + +Status + +This is a working draft constructed by the editor. It is not +an official committee work product and may not reflect the consensus +opinion of the committee. + + + +Please send comments on this specification to the +docbook@lists.oasis-open.org list. To subscribe, send +an email message to +docbook-request@lists.oasis-open.org with the word +subscribe as the body of the +message. + + + + + + + + +
+Introduction + +DocBook is general purpose document type particularly well +suited to books and papers about computer hardware and software +(though it is by no means limited to these applications). + + +Scalable Vector Graphics is an XML +document type designed for describing two-dimensional graphics (vector +graphic shapes, images, and text). + +This module integrates SVG into DocBook, allowing elements from the +SVG namespace to be used in imageobjects. + +The DocBook +Technical Committee maintains the DocBook SVG schema. +DocBook SVG is officially available as an Document Type +Definition (DTD). + +The Version 1.0 release is based on and +. + + +The DocBook Technical Committee welcomes bug reports and +requests for enhancement (RFEs) from the user community. The current list +of outstanding requests is available through the +SourceForge +tracker +interface. This is also the preferred mechanism for submitting new requests. +Old RFEs, from a previous legacy tracking system, are +archived +for reference. + +
+ +
Terminology + +The key words must, must +not, required, +shall, shall not, +should, should not, +recommended, may, and +optional in this &standard; are to be +interpreted as described in . Note that for +reasons of style, these words are not capitalized in this +document. + +
+ +
+The DocBook SVG Document Type V1.0CR1 + +The DocBook SVG Document Type is a superset of +. +It is distributed from the +DocBook site at +OASIS. + + +This module integrates SVG into DocBook by incorporating the SVG +V1.1 DTD using a namespace prefix and extending the content model of +DocBook's imageobject element to allow those +elements to occur. + +
+Usage + +To use this module, specify the public and system identifiers of this +module in your document type declaration. For example, to use this module +to write a book, use the following document type declaration: + +]]> + +Naturally, you can include an internal subset if you wish. + +This module declares svg: as the namespace +prefix for SVG. If you wish to change that prefix, you may declare an +alternative by changing the declaration of the parameter entity +SVG.prefix. + + +For example, to write an article using this module and to +specify that the namespace prefix for SVG elements should be +s:, you could use the following document type +declaration: + + +]>]]> + +To incorporate this module into a higher-level customization layer, use the +public and system identifiers of this module in your customization layer. For +example: + + +%docbooksvg;]]> + +
+ +
+Limitations + +This module is DTD-based. DTDs and +do not work together with perfect harmony. In particular, although you +can change the namespace prefix used for SVG diagrams on a +per-document basis, you cannot change it on a per-diagram basis. You +simply cannot use svg: as the prefix on one diagram +and s: as the prefix in another diagram within the +same document. Such a document may be well-formed, and many XML tools +may process it correctly, but it cannot be validated against this +module's DTD. + +The SVG module overrides the declaration of the +imageobject element. In order to write a +customization layer that also changes the declaration of +imageobject, that customization layer must disable +docbook.svg.imageobject.element +before including the SVG module. + +
+
+ +
+Changes in DocBook SVG V1.0CR1 + +This release updates DocBook SVG to be a customization of DocBook XML V4.2. + + +There are no substantive changes to the SVG-specific markup. + +
+ +
Release Notes + +This module is currently based on the SVG 1.1 Candidate +Recommendation specification. The Candidate Recommendation +specification may change without warning. This module will not +be published in final form until the SVG 1.1 Recommendation is +released. + +
+ + +OASIS DocBook Technical Committee + +The following individuals were members of the committee during +the formulation of this &standard;: + + +Dennis Evans +Patricia Gee-Best +Paul Grosso +Dick Hamilton +Nancy (Paisner) Harrison +Richard Lander +Sabine Ocker +Michael Sabrio +Michael Smith +Tim Teebken +Norman Walsh (Chair, Editor) + + + + + +Notices + +Copyright © 2001, 2002 OASIS Open, Inc. All Rights Reserved. + + +OASIS takes no position regarding the validity +or scope of any intellectual property or other rights +that might be claimed to pertain to the implementation +or use of the technology described in this document +or the extent to which any license under such rights +might or might not be available; neither does it represent +that it has made any effort to identify any such rights. +Information on OASIS's procedures with respect to rights +in OASIS specifications can be found at the OASIS website. +Copies of claims of rights made available for publication +and any assurances of licenses to be made available, +or the result of an attempt made to obtain a general +license or permission for the use of such proprietary +rights by implementors or users of this specification, +can be obtained from the OASIS Executive Director. + +OASIS invites any interested party to bring to +its attention any copyrights, patents or patent applications, +or other proprietary rights which may cover technology +that may be required to implement this specification. +Please address the information to the OASIS Executive +Director. + +This document and translations of it may be copied +and furnished to others, and derivative works that comment +on or otherwise explain it or assist in its implementation +may be prepared, copied, published and distributed, +in whole or in part, without restriction of any kind, +provided that the above copyright notice and this paragraph +are included on all such copies and derivative works. +However, this document itself may not be modified in +any way, such as by removing the copyright notice or +references to OASIS, except as needed for the purpose +of developing OASIS specifications, in which case the +procedures for copyrights defined in the OASIS Intellectual +Property Rights document must be followed, or as required +to translate it into languages other than English. + +The limited permissions granted above are perpetual +and will not be revoked by OASIS or its successors or +assigns. + +This document and the information contained herein +is provided on an AS IS basis and OASIS DISCLAIMS +ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT +LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION +HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES +OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. + +OASIS has been notified of intellectual property +rights claimed in regard to some or all of the contents +of this specification. For more information consult +the online list of claimed rights. + + + + +Intellectual Property Rights + +For information on wether any patents have been disclosed that may be +essential to implementing this specification, and any offers of patent +licensing terms, please refer to the Intellectual Property Rights section +of the DocBook web page +() + + + + + +Revision History + + + + 1.0-CR1 + 12 Sep 2002 + + + + Beta Release 2 + 21 May 2002 + + + + + + +References + +Normative + + + + + + + + + + + +