--- author: - Jirka Kosek jirka@kosek.cz - Norman Walsh ndw@nwalsh.com §convert4to5, proofreading - Dick Hamilton rlhamilton@frii.com §changes-removed, customization, proofreading subtitle: The Transition Guide title: DocBook V5.0 --- This document is targeted at DocBook users who are considering switching from DocBook V4.x to DocBook V5.0. It describes differences between DocBook V4.x and V5.0 and provides some suggestions about how to edit and process DocBook V5.0 documents. There is also a section devoted to conversion of legacy documents from DocBook 4.x to DocBook V5.0. At the time this was written the current version of DocBook V5.0 was 5.0. However, almost all of the information in this document is general and applies to any newer version of DocBook V5.0. # Introduction The differences between DocBook V4.x and V5.0 are quite radical in some aspects, but the basic idea behind DocBook is still the same, and almost all element names are unchanged. Because of this it is very easy to become familiar with DocBook V5.0 if you know any previous version of DocBook. You can find a complete list of changes in DB5SPEC, here we will discuss only the most fundamental changes. ## Finally in a namespace {#introduction-ns} All DocBook V5.0 elements are in the namespace . XMLExtensible Markup Language namespaces are used to distinguish between different element sets. In the last few years, almost all new XML grammars have used their own namespace. It is easy to create compound documents that contain elements from different XML vocabularies. DocBook V5.0 is following this design rule. Using namespaces in your documents is very easy. Consider this simple article marked up in DocBook V4.5:
Sample article This is a really short article.
The corresponding DocBook V5.0 article will look very similar:
Sample article This is a really short article.
The only change is the addition of a default namespace declaration (`xmlns="http://docbook.org/ns/docbook"`) on the root element. This declaration applies the namespace to the root element and all nested elements. Each element is now uniquely identified by its local name and namespace. :::: note ::: title ::: The namespace name serves only as an identifier. This resource is not fetched during processing of DocBook documents, and you are not required to have an Internet connection during processing. If you access the namespace URI with a browser, you will find a short explanatory document about the namespace. In the future this document will probably conform to (some version of) RDDL and provide pointers to related resources. :::: ## Relaxing with DocBook {#introduction-rng} For more than a decade, the DocBook schema was defined using a DTD. However, DTDs have serious limitations, and DocBook V5.0 is thus defined using a very powerful schema language called RELAX NG. Thanks to RELAX NG, it is now much easier to create customized versions of DocBook, and some content models are now cleaner and more precise. Using RELAX NG has an impact on the document prolog. The following example shows the typical prolog of a DocBook V4.x document. The version of the DocBook DTD (in this case 4.5) is indicated in the document type declaration (!DOCTYPE) which points to a particular version of the DTD. :::: {#ex.docbook45 .example} ::: title DocBook V4.5 document :::
Sample article This is a very short article.
:::: In contrast, DocBook V5.0 does not depend on DTDs anymore. This mean that there is no document type declaration and the version of DocBook used is indicated with the version attribute instead. :::: {#ex.docbook5 .example} ::: title DocBook V5.0 document :::
Sample article This is a very short article.
:::: As you can see, DocBook V5.0 is built on top of existing XML standards as much as possible, for example the lang attribute is superseded by the standard xml:lang attribute. Another fundamental change is that there is no direct indication of the schema used. Later in this document, you will learn how you can specify a schema to be used for document validation. :::: note ::: title ::: Although we recommend the RELAX NG schema for DocBook V5.0, there are also DTD and W3C XML Schema versions available (see [Where to get the schemas](#schemas)) for tools that do not yet support RELAX NG. :::: ## Why switch to DocBook V5.0? {#introduction-why-to-switch} The simple answer is "because DocBook V5.0 is the future". Apart from this marketing blurb, there are also more technical reasons: - *DocBook V4.x is feature frozen.*DocBook V4.5 is the last version of DocBook in the V4.x series. Any new DocBook development, like the addition of new elements, will be done in DocBook V5.0. It is only matter of time before useful, new elements will be added into DocBook V5.0, but they are not likely to be back ported into DocBook V4.x. DocBook V4.x will be in maintenance mode and errata will be published if necessary. - *DocBook V5.0 offers new functionality.* DocBook V5.0 provides significant improvements over DocBook V4.x. For example there is general markup for annotations, a new and flexible system for linking, and unified markup for information sections using the info element. - *DocBook V5.0 is more extensible.* Having DocBook V5.0 in a separate namespace allows you to easily mix DocBook markup with other XML-based languages like SVG, MathML, XHTML or even FooBarML. - *DocBook V5.0 is easier to customize.* RELAX NG offers many powerful constructs that make customization much easier than it would be using a DTD (see [Customizing DocBook V5.0](#customizations)). ## Schema jungle {#introduction-schemas} Schemas for DocBook V5.0 are available in several formats at (or the mirror at ). Only the RELAX NG schema is normative and it is preferred over the other schema languages. However, for your convenience there are also DTD and W3C XML Schema versions provided for DocBook V5.0. But please note that neither the DTD nor the W3C XML schema are able to capture all the constraints of DocBook V5.0. This mean that a document that validates against the DTD or XML schema is not necessarily valid against the RELAX NG schema and thus may not be a valid DocBook V5.0 document. See [Schema Comparison](#t.schema-comparison) for summary of constraints that are checked by different schemas. DTD and W3C XML Schema versions of the DocBook V5.0 grammar are provided as a convenience for users who want to use DocBook V5.0 with legacy tools that don\'t support RELAX NG. Authors are encouraged to switch to RELAX NG based tools as soon as possible, or at least to validate documents against the RELAX NG schema before further processing. Some document constraints can\'t be expressed in schema languages like RELAX NG or W3C XML Schema. To check for these additional constraints DocBook V5.0 uses Schematron. We recommend that you validate your document against both the RELAX NG and Schematron schemas. ------------------------------------------------------------------------------------------------------------- Description DTD W3C XML Schema W3C XML RELAX NG RELAX NG + Schema + Schematron/NVDL Schematron ------------------------------- -------------- -------------- -------------- -------------- ----------------- Basic document structure [✔]{.unicode [✔]{.unicode [✔]{.unicode [✔]{.unicode [✔]{.unicode .yes} .yes} .yes} .yes} .yes} ID/IDREF datatypes [✔]{.unicode [✔]{.unicode [✔]{.unicode [✔]{.unicode [✔]{.unicode .yes} .yes} .yes} .yes} .yes} Datatypes[^1] [✘]{.unicode [✘]{.unicode [✘]{.unicode [✔]{.unicode [✔]{.unicode .no} .no} .no} .yes} .yes} Co-occurrences[^2] [✘]{.unicode [✘]{.unicode [✘]{.unicode [✔]{.unicode [✔]{.unicode .no} .no} .no} .yes} .yes} Hooks for MathML and SVG [✘]{.unicode [✘]{.unicode [✘]{.unicode [✔]{.unicode [✔]{.unicode content .no} .no} .no} .yes} .yes} Link type integrity[^3] [✘]{.unicode [✘]{.unicode [✔]{.unicode [✘]{.unicode [✔]{.unicode .no} .no} .yes} .no} .yes} Presence of version attribute [✘]{.unicode [✘]{.unicode [✔]{.unicode [✘]{.unicode [✔]{.unicode on the root element .no} .no} .yes} .no} .yes} Miscellaneous checks[^4] [✘]{.unicode [✘]{.unicode [✔]{.unicode [✘]{.unicode [✔]{.unicode .no} .no} .yes} .no} .yes} Element exclusions[^5] [✘]{.unicode [✘]{.unicode [✔]{.unicode [✘]{.unicode [✔]{.unicode .no} .no} .yes} .no} .yes} ------------------------------------------------------------------------------------------------------------- : Schema Comparison {#t.schema-comparison} ### Where to get the schemas {#schemas} The latest versions of schemas can be obtained from . At the time this was written the latest version was 5.0. Individual schemas are available at the following locations: RELAX NG schema : RELAX NG schema in compact syntax : DTD : W3C XML Schema : Schematron schema with additional checks : These schemas are also available from the mirror at . ### DocBook documentation {#docs} Detailed documentation about each DocBook V5.0 element is presented in [the reference part of DocBook: The Definitive Guide](http://docbook.org/tdg5/en/html/pt02.html). :::: note ::: title ::: Other parts of DocBook: The Definitive Guide have not yet been updated to reflect the changes made in DocBook V5.0. Please do not be confused by this. :::: # Tool chain {#tools} This section briefly describes tools and procedures to edit and process content stored in DocBook V5.0. ## Editing DocBook V5.0 {#editors} Because DocBook is an XML-based format and XML is a text-based format, you can use any text editor to create and edit DocBook V5.0 documents. However, using "dumb" editors like Notepad is not very productive. You will do better if you use an editor that supports XML. Although there are DTD and W3C XML Schemas available for DocBook V5.0, which means you can use any editor that works with DTDs or W3C XML Schemas, we recommend that you use the RELAX NG grammar with DocBook V5.0. The rest of this section contains an overview of XML editors (listed in alphabetical order) that are known to work with RELAX NG schemas and that offer guided editing based on the RELAX NG schema. ### Emacs and nXML {#editors-nxml} [nXML mode](http://www.thaiopensource.com/nxml-mode/) is an add-on for the GNU Emacs text editor. By installing nXML you can turn Emacs into a very powerful XML editor that offers guided editing and validation of XML documents. ![Emacs with nXML mode provides guided editing and validation](images/emacs.png){#f.emacs} nXML uses a special configuration file named `schemas.xml` to associate schemas with XML documents. Often you will find this file in the directory `site-lisp/nxml/schema` inside the Emacs installation directory. Adding the following line into the configuration file, will associate DocBook V5.0 elements with the appropriate schema: :::: note ::: title ::: Please note that nXML ships with a file named `docbook.rnc`. This file contains the RELAX NG grammar for DocBook V4.x. Be sure that you associate the DocBook V5.0 namespace with the corresponding DocBook V5.0 grammar. :::: If you can\'t edit the global `schemas.xml` file, you can create this file in the same directory as your document. nXML will find associations placed there also. In this case you must create a complete configuration file like: ### oXygen {#editors-oxygen} oXygen is a feature rich XML editor. It has built-in support for many schema languages including RELAX NG and it is preconfigured with many document types including DocBook. oXygen will assist you with writing DocBook V5.0 content, and you will be able to validate your documents against both RELAX NG and Schematron schemas. ![DocBook V5.0 document opened in oXygen](images/oxygen4.png){#f.oxygen.open5 width="100%"} ![DocBook V5.0 document opened in oXygen in Author mode](images/oxygen5.png){#f.oxygen.author.mode width="100%"} ### XML Mind XML editor {#editors-xxe} XML Mind XML editor (XXE) is a visual validating XML editor that provides a wordprocessor-like interface to users. It is available in two versions, Standard and Professional. The Standard version is free and provides everything you need to edit DocBook V5.0 documents. ![XML Mind XML Editor -- feels almost like MS Word but real DocBook V5.0 markup is created](images/xxe.png){#f.xmlmind width="100%"} In order to use DocBook V5.0 in XXE you have to install an add-on. Go to [Options \> Install Add-ons...]{.menuchoice}. Then choose DocBook 5 configuration and press the OK button. After restart, XXE is ready to work with DocBook V5.0 documents. ## Validating DocBook V5.0 {#validators} If you are not using a RELAX NG-based validating editor when you create documents, we strongly recommend that you validate your documents against RELAX NG and Schematron schemas before processing them. Only after successful validation can you be sure that your document is really DocBook V5.0 and that processing tools will be able to process it correctly. For validation you can use tools that support simultaneous RELAX NG and Schematron validation, or you can use NVDL to orchestrate validation using the two schemas. ### Using RELAX NG and Schematron {#validators-rng-sch} You can find a list of RELAX NG validators at . It is best to use validators with support for embedded Schematron rules inside RELAX NG schemas. Schematron is a rule-based validation language which is used to impose additional constraints on DocBook documents. Schematron rules assert conditions which are impossible or difficult to express in a pure RELAX NG schema. Sun Multi-Schema XML Validator (MSV) is able to validate an XML document against a RELAX NG schema and Schematron rules at the same time. To install and use MSV follow these steps: 1. Download `relames.zip` from . 2. Unpack the downloaded file into an arbitrary directory. 3. Validate your document using the following command: java -Xss512K -jar /path/to/relames.jar /path/to/docbook.rng document.xml :::: note ::: title ::: The switch `-Xss512K` increases the stack size of the Java virtual machine. This is necessary because the DocBook schema is quite large. If you get stack overflow errors from MSV, increase this value. You may get spurious error messages if the value is too small, so if you get a stack overflow error, ignore any other error messages and try a larger value for the stack size. If you are not using Sun\'s Java implementation, please consult the documentation for your virtual machine to learn how to increase the stack size. :::: There is also an [on-line DocBook V5.0 validator](http://relaxed.vse.cz/docbookvalidator/) that validates DocBook V5.0 documents against the normative RELAX NG schema with embedded Schematron rules. ### Using NVDL NVDL is a meta-schema language which can validate a document against several schemas. DocBook V5.0 comes with a NVDL schema which specifies that DocBook documents should be validated against both RELAX NG and Schematron schemas. You can find a list of NVDL validators at . The following procedures show how to install and use the oNVDL and JNVDL validators. 1. Download `onvdl-20070517.zip`. 2. Unpack the downloaded file into an arbitrary directory. 3. Validate your document using the following command: java -jar /path/to/oNVDL/bin/onvdl.jar /path/to/docbook.nvdl document.xml 1. Download the latest release of JNVDL from . 2. Unpack the downloaded file into an arbitrary directory. 3. Modify file `jnvdl.bat` (or `jnvdl.sh` on Unix based systems) to include `-Xss512K` switch directly after `java` command. 4. On Windows systems, validate your document using the following command: /path/to/jnvdl/jnvdl -nt -s /path/to/docbook.nvdl document.xml On Unix systems, validate your document using the following command: /path/to/jnvdl/jnvdl.sh -nt -s /path/to/docbook.nvdl document.xml ## Processing DocBook V5.0 {#processing} Part of DocBook\'s great success can be attributed to the availability of free tools that can be used to transform DocBook content into various target formats including HTML and PDF. The DocBook XSL Stylesheets are very popular tools. ### DocBook XSL Stylesheets {#dbxsl} The DocBook stylesheets are designed to process content written in different versions of DocBook (for example 3.1 and 4.2). Recent versions of the stylesheets are also able to process DocBook V5.0 with some limitations. You can process DocBook V5.0 documents with the DocBook XSL stylesheets in exactly the same way you process DocBook V4.x documents. You do not need special software; you can stick to your preferred XSLT processor, be it Saxon, xsltproc, Xalan or whatever else (but see the note about the lost base URI below). During document processing, the stylesheets strip namespaces from DocBook V5.0 to get a document which will be very similar to DocBook V4.x. This is necessary because from the XSLT point of view, elements from different namespaces are distinct and cannot be easily processed by the same set of templates. This process is completely transparent to the user. If you are processing DocBook V5.0 documents, the only difference is that you will see the following additional message: Note: namesp. cut : stripped namespace before processing Note: namesp. cut : processing stripped document Although you can successfully use the existing stylesheets to process DocBook V5.0, there are some limitations and unsupported features. The unsupported features include: - general annotations; - general XLink links on all elements. :::: note ::: title ::: During namespace stripping, the base URI of the document is lost. This means that in rare situations, relatively referenced resources like images or programlistings can be processed incorrectly. The stylesheets attempt to compensate for this problem, but that is not always possible. When an XSLT processor other than Saxon or Xalan is used, a warning message is generated: WARNING: cannot add @xml:base to node set root element. Relative paths may not work. :::: ### DocBook XSL-NS Stylesheets {#dbxsl-ns} As you can see from reading the previous section, namespace stripping has limitations that will cause trouble in some situations. To overcome those limitations, Bob Stayton created a build system for taking the non-namespace-aware DocBook XSL stylesheets and generating namespace-aware versions from them. The DocBook [XSL-NS stylesheets](http://docbook.sourceforge.net/release/xsl-ns/current/) are the result. The DocBook XSL-NS stylesheets are released side-by-side with the DocBook XSL stylesheets, as a separate [docbook-xsl-ns](https://sourceforge.net/project/showfiles.php?group_id=21935&package_id=219178) package. They are the recommended XSLT 1.0 stylesheets to use for transforming namespaced (DocBook V5.0) documents. ### XSLT 2.0 based re-implementation {#dbxsl2} XSLT 1.0 is missing some important features. To work around these missing features, the current DocBook XSL stylesheets use some implementation-specific extensions. XSLT 2.0 adds many new and previously missing features into the language. A new set of DocBook stylesheets is being implemented based on XSLT 2.0 to take advantage of these features and to fully support DocBook V5.0. The XSLT 2.0 based stylesheets have many new features, including: - seamless integration of profiling (conditional documents) with external bibliographies and glossaries; - no need for (most) external extensions; - internationalized indexes; - easy to customize titlepage templates. The XSLT 2.0 based stylesheets are still under development. At this writing, they only support HTML and chunked HTML output. As time permits, the stylesheet developers will be adding other formats. Since the stylesheets are developed in the limited free time the developers have, there\'s no specific schedule. There are not very many XSLT 2.0 implementations available. But, if you want to try the new stylesheets, grab a snapshot of the development version from and unpack it somewhere. Then download and install Saxon 9 from . To transform a DocBook V5.0 document to a single HTML page use the command: java -jar /path/to/saxon9.jar -o output.html document.xml /path/to/docbook-xsl2-snapshot/html/docbook.xsl To transform a DocBook V5.0 document to a set of chunked HTML pages use the command: java -jar /path/to/saxon9.jar document.xml /path/to/docbook-xsl2-snapshot/html/chunk.xsl # Markup changes {#changes} This section describes the most common markup changes between DocBook V4.x and V5.0. You can find a complete list of changes in DB5SPEC. ## Improved cross-referencing and linking {#changes-linking} In DocBook V4.x the attribute id is used to assign a unique identifier to an element. In DocBook V5.0 this attribute is renamed xml:id in order to comply with XMLID. Now you can use almost any inline element as the source of a link, not just xref or link. For example, the following DocBook 4.x content:
DIR command ...
LS command This command is a synonym for DIR command.
is written in DocBook V5.0 as:
DIR command ...
LS command This command is a synonym for DIR command.
The linkend attribute was added to all inline elements together with the href attribute from the XLink namespace. This means that you can use any inline element as the source of a hypertext link. To use XLinks you have to declare the XLink namespace (most often on the root element of your document):
Test article Emacs is my favourite text editor. … The ulink element was removed from DocBook V5.0 in favor of XLink linking. Instead of the DocBook V4.x ulink element: DocBook site you can now use link DocBook site XLink links may contain a fragment identifier, which you can use instead of linkend to form cross-references inside a document; for example: DIR However XLink links are not checked during validation, while xml:id/linkend links are checked for ID/IDREF consistency. One place where the XLink-based, fragment identifier scheme is useful is when XInclude is being used, since XML ID/IDREF links cannot span XInclude boundaries. You can use whichever approach better suits your needs. ## Renamed elements {#changes-renamed} Some elements were renamed to better express their meaning or to reduce the total number of elements available in DocBook. Old name New name ----------------------------------------------------------------------------------------------------------- ----------------------------------- sgmltag tag bookinfo, articleinfo, chapterinfo, \*info info authorblurb personblurb collabname, corpauthor, corpcredit, corpname orgname isbn, issn, pubsnumber biblioid lot, lotentry, tocback, tocchap, tocfront, toclevel1, toclevel2, toclevel3, toclevel4, toclevel5, tocpart tocdiv graphic, graphicco, inlinegraphic, mediaobjectco mediaobject and inlinemediaobject ulink link ackno acknowledgements : Renamed elements {#t.renamed} ## Removed elements {#changes-removed} The following elements were removed from DocBook V5.0 without direct replacements: action, beginpage, highlights, interface, invpartnumber, medialabel, modespec, structfield, structname. If you use one or more of these elements, here are some suggestions as to how to re-code them in DocBook V5.0. Old name Recommended mapping ------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- action Use ``. beginpage Remove: beginpage is advisory only and has tended to cause confusion. A processing instruction or comment should be a workable replacement if one is needed. highlights Use abstract. Note that because highlights has a broader content model, you may need to wrap contents in a para inside abstract. interface Use one of the "gui\*" elements (guibutton, guiicon, guilabel, guimenu, guimenuitem, or guisubmenu). invpartnumber Use ``. The productnumber element is another alternative. medialabel Use ``, where \ is the type of media being labeled (e.g.,cdrom or dvd). modespec No longer needed. The current processing model for olink renders modespec unnecessary. structfield, structname Use varname. If you need to distinguish between the two, use ``. In some contexts, it may also be appropriate to use property for structfield. : Recommended mapping for removed elements {#t.removed} # Converting DocBook V4.x documents to DocBook V5.0 {#convert4to5} The DocBook V5.0 schema ships with an XSLT 1.0 stylesheet that is designed to transform valid DocBook V4.x documents to valid DocBook V5.0 documents. To convert your document, `doc.xml` in the examples below, follow these steps: 1. Check the validity of your DocBook XML V4.x document. The conversion tool assumes that the input document is valid. If the input document contains markup errors, the results will be unpredictable at best. 2. Transform `doc.xml` to `newdoc.xml` with the `db4-upgrade.xsl` stylesheet included in the DocBook V5.0 distribution that you are using. 3. Check the validity of your DocBook XML V5.0 document against the DocBook V5.0 RELAX NG grammar. In the vast majority of cases, the resulting document should be valid and your conversion process is finished. If the document is not valid, please report the problem. (Over time, we\'ll have more experience with the sorts of things that can go wrong and we\'ll update this document to reflect that experience.) ## What About Entities? {#entities} Using XSLT to transform existing documents to DocBook V5.0 has one potential disadvantage: it removes all entity references from your document. If preserving entities is an important aspect of your production work flow, you will have to engage in a semi-manual process to preserve them. 1. Open your existing document using your favorite editing tool. You must use a tool that *is not* XML-aware, or one that allows you to edit markup "in the raw". 2. Replace all occurrences of the entity references that you want to preserve with some unique string. For example, if you want to preserve "`∏`" references, you could replace them all with "`[[[Product]]]`" (assuming that the string "`[[[Product]]]`" doesn\'t occur anywhere else in your document). 3. Copy the document type declaration off of your document and save it some place. The document type declaration is everything from "``". 4. Perform the conversion described in [Converting DocBook V4.x documents to DocBook V5.0](#convert4to5). 5. Open the new document using your favorite editing tool. Replace all occurrences of the unique string you used to save the entity references with the corresponding entity references. 6. Paste the document type declaration that you saved onto the top of your new document. 7. Remove the external identifier (the `PUBLIC` and/or `SYSTEM` keywords) from the document type declaration. A document that begins: ]> is perfectly well-formed. If you don\'t remove the references to the DTD, then your parser will likely try to validate against DocBook V4.0 and that\'s not going to work. Alternatively, you could refer to the DocBook V5.0 DTD. :::: tip ::: title ::: Steps 2 and 5 from previous procedure can be automated using the [cloak script](http://docbook.svn.sourceforge.net/viewvc/docbook/trunk/contrib/tools/cloak) written by Michael Smith. :::: ### External Parsed Entities {#extparsedentities} External parsed entities, entities which load part of a document from another file, are a special case. These can often be replaced with XInclude elements. The Perl script `db4-entities.pl`, also included in the DocBook V5.0 distribution attempts to perform this replacement for you. To use the script, perform the following steps: 1. Process your document with `db4-entities.pl`. The script expects a single filename and prints the XInclude version on standard output. 2. Process the XInclude version as described in [Converting DocBook V4.x documents to DocBook V5.0](#convert4to5). # Customizing DocBook V5.0 {#customizations} It\'s much easier to customize DocBook V5.0 than it was to customize earlier releases. This is partly because RELAX NG provides better support for modifications than DTDs and partly because the DocBook schema is designed to take full advantage of the capabilities RELAX NG provides. This section describes the organization of the RELAX NG schema for DocBook, methods and examples for adding, removing, and modifying elements and attributes, and conventions for naming and versioning DocBook customizations. It assumes some familiarity with RELAX NG. If you are unfamiliar with RELAX NG, you can find a tutorial introduction in RNCTUT. ## DocBook RELAX NG schema organization {#relaxngorg} The DocBook RELAX NG schema is highly modular, using named patterns extensively. Every element, attribute, attribute list, and enumeration has its own named pattern. In addition, there are named patterns for logical combinations of elements and attributes. These named patterns provide "hooks" into the schema that allow you to do a wide range of customization by simply redefining one or more of the named patterns. An important design characteristic of the schema is that duplication is minimized. This is done through the use of named patterns for common groupings that can be re-used. For example, the imagedata and videodata elements each have an align attribute that takes the same set of enumerated values. Rather than repeating those values, a single pattern, `db.halign.enumeration` is referenced by the `db.videodata.align.enumeration` and `db.imagedata.align.enumeration` patterns, which are in turn referenced by the `db.videodata.align.attribute` and `db.imagedata.align.attribute` patterns. While this may seem like overkill, it allows a customizer to modify the allowed enumerations for these two attributes separately or together, or to completely re-define the allowed content of either or both, by redefining one or more of these named patterns. ### Pattern Names {#patternnames} Because named patterns are used extensively, the RELAX NG schema uses several naming conventions. These are: - Names have two or more parts, separated by dots "." - The first part of each name is the prefix "db" - Each element has a named pattern in the form `db.elementname`. Elements that have different content models in different contexts will also have patterns in the form `db.context.elementname`. For example, `db.figure.info` defines the content model for the info element when it appears as a child of the figure element. \ may have several parts. For example, `db.cals.entrytbl.thead`. - Most attributes have a named pattern in the form `db.attributename.attribute`. Attributes that have different content models in different contexts will also have patterns in the form `db.context.attributename.attribute`. For example, `db.olink.localinfo.attribute` defines the content model of the localinfo attribute when it appears in olink. There are a few attributes that do not have individual named patterns. For example, the effectivity attributes are grouped into `db.effectivity.attributes` and not identified separately. - Each element has a named pattern for its attribute list in the form `db.elementname.attlist` that defines the list of attributes for that element. Elements that have different attribute lists in different contexts will also have patterns in the form `db.context.elementname.attlist` For example, `db.html.table.attlist` defines the attribute list for the html table element and `db.cals.table.attlist` defines the attribute list for a cals table element. - Each attribute that has enumerated values has a named pattern in the form `db.[context.]attributename.enumeration`. If the enumeration for a particular attribute depends on context, optional context is provided. For example, `db.verbatim.continuation.enumeration` defines the enumeration values for the continuation attribute that is used in verbatim contexts like screen. Unlike elements and attributes, there is not necessarily a named pattern for enumerated attributes outside their context. For example, there is no `db.class.enumeration` because the class attribute has a broad and non-intersecting range of uses. - There are several different groupings of elements and attributes. Here are the major ones: inlines : Combinations of inline elements, for example, `db.error.inlines`, which contains `db.errorcode`, `db.errortext`, etc. blocks : Combinations of block elements, for example, `db.verbatim.blocks`, which contains `db.programlisting`, `db.screen`, etc. attributes : Combinations of attributes, for example, `db.effectivity.attributes`, which contains the attributes arch, condition, conformance, etc. components : High level components of the schema, for example, `db.navigation.components`, which contains `db.glossary`, `db.bibliography`, `db.index`, and `db.toc`, and is used inside the content model for chapter, appendix, and preface. contentmodel : Shared content models, for example, `db.admonition.contentmodel`, which contains the content model for tip, warning, note, etc. There are a couple of other groupings designed to minimize duplication, but these are the most important. ## General customization considerations {#customconsiderations} Creating a customized schema is similar to creating a customization layer for XSL. The schema customization layer is a new RELAX NG schema that defines your changes and includes the standard docbook schema. You then validate using the schema customization as your schema. [example_title](#ex-empty) is an empty RELAX NG customization that does nothing except define the name spaces and include the standard DocBook schema. The href attribute of the include element points to the location of the standard DocBook V5.0 schema.[^6] All of the examples are given in both RNG and RNC form. :::: {#ex-empty .example} ::: title Empty customization file ::: ``` rng ``` ``` rnc namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" inherit = db # redefinitions of named patterns ``` :::: ## Elements {#cust-elements} ### Adding elements {#cust-add-elements} Adding an element typically takes two definitions. The first defines the new element and its content model, and the second adds the new element into the schema. We\'ll show two examples. [example_title](#ex-add-element-1) adds a new element, person, with the same content model as author. The new element will be allowed to appear wherever author can appear. The `db.author` pattern is copied and renamed `dbx.person`, defining a new element called person. Then, the `db.author` pattern is redefined to be a choice of the current value or `dbx.person`. The combine attribute tells RELAX NG to combine this pattern with the existing named pattern. In this case, the value of the combine attribute is "choice", which tells the parser that either the original pattern or this new pattern is a valid match. :::: {#ex-add-element-1 .example} ::: title Adding a new element by duplicating an existing one ::: ``` rng ``` ``` rnc default namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" # define the new element dbx.person = element person { db.author.attlist, db.credit.contentmodel } # redefine the db.author pattern to allow db.person in # the same places as db.author db.author |= dbx.person ``` :::: The preceding method works well when you\'d like a new element to be a clone or near-clone of an existing element. It gives you complete control over the content model, but only limited control over where the element is allowed. It works well when you want to allow the element in the same places as an existing element, and for this example that works nicely, since author is allowed in four different named patterns, each of which would have had to be redefined to allow person. But, if you can\'t find an existing element that is allowed in exactly the places you need, this method doesn\'t work as well. [example_title](#ex-add-element-2) adds two new elements by combining them into a higher level pattern. In this example, we\'ll add two new inline elements for writing about assembly language, register and instruction. We will allow them wherever programming inlines or operating system inlines are allowed. [example_title](#ex-add-element-2) defines the two elements, creates a new named pattern (`dbx.asm.inlines`) that contains them, and adds that pattern to `db.programming.inlines` and `db.os.inlines`. Since these two patterns don\'t have any elements in common, the strategy used in [example_title](#ex-add-element-1) would require selecting two different elements to "clone", which would be messy. :::: {#ex-add-element-2 .example} ::: title Adding new inline elements ::: ``` rng ``` ``` rnc default namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" # define the new elements dbx.register = element register { text } dbx.instruction = element instruction { text } # create a new pattern that contains the new inlines dbx.asm.inlines = dbx.register | dbx.instruction # add the new inlines to programming and os inlines db.programming.inlines |= dbx.asm.inlines db.os.inlines |= dbx.asm.inlines ``` :::: ### Deleting elements {#cust-delete-elements} Deleting elements is straightforward, but takes some care and planning. [example_title](#ex-delete-element) deletes the important admonition element by redefining it with a content model of `notAllowed`. Note that in this example, the redefinition is inside the include element. This is required for redefinitions that completely replace an existing pattern. Be careful; If you delete an element that is a required part of another element\'s content model, you can make it impossible to create a valid document. For example, if you delete the title element, you won\'t be able to validate a book because a book requires a title. :::: {#ex-delete-element .example} ::: title Deleting an element ::: ``` rng ``` ``` rnc namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" inherit = db { # redefine important element as notAllowed db.important = notAllowed } ``` :::: ### Customizing the content model of existing elements {#cust-modify-elements} [example_title](#ex-modify-element) expands the definition of author to include two new elements, born and died. The author element allows two content models, `db.person.author.contentmodel`, which defines an author who is a person, and `db.org.author.contentmodel`, which defines an author that is an organization. We will modify `db.person.author.contentmodel` so that only authors who are persons can have the new elements. :::: {#ex-modify-element .example} ::: title Modifying the content model of an element ::: ``` rng ``` ``` rnc default namespace = "http://docbook.org/ns/docbook" namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" db.person.author.contentmodel &= element born { db.date.contentmodel }? & element died { db.date.contentmodel }? ``` :::: This modification will allow instances like this: Babe Ruth 02/06/1895 08/16/1948 but because we only modified the content model for authors who are human, it won\'t allow an instance like this, which uses `db.org.author.contentmodel`: Boston Red Sox 1919 2004 ## Attributes {#cust-attributes} ### Adding attributes {#cust-add-attributes} The simplest way to add an attribute to a single element is to add it to the attlist pattern for that element. [example_title](#ex-add-attr) adds the optional attributes born and died to the attribute list for author. The `db.author.attlist` named pattern is redefined with the combine attribute set to "interleave", which interleaves the two new optional attributes with the existing attributes on the list. :::: {#ex-add-attr .example} ::: title Adding attributes ::: ``` rng ``` ``` rnc namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" inherit = db db.author.attlist &= attribute born { db.date.contentmodel }? & attribute died { db.date.contentmodel }? ``` :::: Unlike [example_title](#ex-modify-element), [example_title](#ex-add-attr) allows the new attributes to appear on any author element, not just those using the person content model. [example_title](#ex-add-attr-2) shows how you could limit the use of these attributes to authors who are persons. In this example, the new attributes are interleaved with the `db.person.author.contentmodel`. The only difference between this example and [example_title](#ex-modify-element) is that the added patterns are identified as attributes rather than elements. This shows some of the flexibility of RELAX NG, which treats attributes and elements very consistently. :::: {#ex-add-attr-2 .example} ::: title Adding attributes; alternate method ::: ``` rng ``` ``` rnc namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" inherit = db # redefinitions of named patterns db.person.author.contentmodel &= attribute born { db.date.contentmodel }? & attribute died { db.date.contentmodel }? ``` :::: There is one difference in the treatment of attributes and elements that is worth noting. By the XML 1.0 definition, the relative order of attributes is not significant. Therefore, the interleave block is not required for attributes, though it does no harm. ### Deleting attributes {#cust-delete-attributes} Deleting an attribute is similar to deleting an element, except that you use the RELAX NG `empty` pattern rather than `notAllowed`. [example_title](#ex-delete-attr) deletes the linking attributes, which are collected in the `db.common.linking.attributes` pattern, by defining that pattern as `empty`. :::: {#ex-delete-attr .example} ::: title Deleting an attribute ::: ``` rng ``` ``` rnc namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" inherit = db { db.common.linking.attributes = empty } ``` :::: Generally, `empty` is used when deleting attributes and `notAllowed` is used when deleting elements. ### Changing permitted content of attributes {#cust-modify-attributes} [example_title](#ex-modify-attr) modifies `db.spacing.enumeration` to add the additional value "large". Note that to remove a value from an enumeration, you need to redefine the entire enumeration, minus the values you don\'t need. :::: {#ex-modify-attr .example} ::: title Deleting an attribute ::: ``` rng large ``` ``` rnc namespace db = "http://docbook.org/ns/docbook" include "docbook.rnc" inherit = db # add value to an enumeration db.spacing.enumeration |= "large" ``` :::: ## Naming and versioning DocBook customizations {#cust-naming} DocBook V5.0 is not tightly coupled with some particular validation technology like DTDs. This also means that DocBook V5.0 documents don\'t have to (and usually don\'t) start with a document type declaration (\) 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 namespace. This namespace is 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. … Future versions of DocBook documents will start with the same 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 a DocBook schema customization you must change the version attribute to distinguish your 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. When you customize the schema, use the following syntax to identify your DocBook derivation: base_version-[subset|extension|variant] [name[-version]?]+ For example: 5.0-subset simplified-1.0 5.0-variant ASMBook 5.0-variant ASMBook-2006 5.0-extension MathML-2.0 SVG-1.1 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 by using the `subset` keyword in the description. If your schema contains any markup model extensions, you can advertise 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 may add a whitespace separated list of customization identifiers. Each name may be optionally followed by its version number. # FAQ ## Authoring **Q:** How do I attach a schema to a DocBook V5.0 document when I do not want to use DTDs and !DOCTYPE? **A:** There is no standard way of associating a RELAX NG schema with a document. Most tools provide some mechanism for performing this association, consult the documentation for your application. In some tools you must specify schema manually each time you want to edit/process your document. **Q:** How do I use entities like ndash in DocBook V5.0? **A:** Modern schema languages (including RELAX NG and W3X XML Schema) do not provide any means to define entities that can be used for easier typing of special characters. Some editors provide functions or special toolbars that allow you to easily pick necessary character and insert it into document as a raw Unicode character or a numeric character reference. Another possibility is to include entity definitions in the prolog of your document. [Entity definition files](http://www.w3.org/2003/entities/) are now maintained by W3C. You can reference definition files with entity definitions you are interested in and then reference imported entities. For example: %isopub; ]>
DocBook V5.0 – the superb documentation format … For your convenience there is also flattened entity definition file which contains all entity definitions. %allent; ]>
DocBook V5.0 – the superb documentation format … **Q:** How to modularize documents? **A:** You can use [XInclude](http://www.w3.org/TR/xinclude/) for this task. There is an alternative schema for DocBook V5.0 that contains XInclude elements. This is necessary to make some XML editors happy. This schema can be found in files that end with letters "xi", e.g. `docbookxi.rnc` instead of `docbook.rnc`. **Q:** How to validate documents which are composed by XInclude? **A:** If you are using XIncludes you should make sure that the final document after resolving all inclusions is valid DocBook V5.0 instance. This means that all XIncludes should be processed before validation takes place. The following command can be used to enable XInclude processing in oNVDL. java -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration -jar /path/to/oNVDL/bin/onvdl.jar /path/to/docbook.nvdl document.xml For JNVDL you can use switch `-xi` to enable XInclude processing. ## Stylesheets **Q:** Will the current DocBook XSL stylesheets (XSLT 1.0 based implementation) be maintained and improved in the future since work on a new XSLT 2.0 based implementation has started? **A:** Yes, the current stylesheets (like 1.73.x) will be supported and improved further because they are very widely deployed and work with many existing XSLT processors. Surely there will be a point in a future when all new development will be switched to the XSLT 2.0 based implementation. But this will not happen until all features of the current stylesheets are implemented in the new stylesheets, and until there is more than one usable XSLT 2.0 processor available. ## Schema customizations **Q:** How can I extend the DocBook schema with MathML elements? **A:** The basic DocBook schema allows elements from the MathML namespace to appear inside the equation element. This means that you can validate a DocBook+MathML document, but MathML content will be ignored during the validation. You will also not be able to use guided editing for the MathML content. If you need strict validation of MathML content or guided editing for MathML, you can easily extend the base DocBook schema with the MathML schema. 1. Download the MathML RELAX NG schema from and unpack it somewhere (e.g. into a `mathml` subdirectory). 2. Create a schema customization in compact syntax---`dbmathml.rnc`: ``` rnc namespace html = "http://www.w3.org/1999/xhtml" namespace mml = "http://www.w3.org/1998/Math/MathML" namespace db = "http://docbook.org/ns/docbook" include "/path/to/docbook.rnc" { db._any.mml = external "mathml/mathml2.rnc" db._any = element * - (db:* | html:* | mml:*) { (attribute * { text } | text | db._any)* } } ``` Or, alternatively, you can use the XML syntax of RELAX NG---`dbmathml.rng`: ``` rng ``` 3. Now use the customized schema (`dbmathml.rnc` or `dbmathml.rng`) instead of the original DocBook schema. **Q:** How can I extend the DocBook schema with SVG elements? **A:** The situation is the same as with MathML support. You can use elements from the SVG namespace inside the imageobject element. 1. Download the SVG RELAX NG schema from and unpack it somewhere (e.g. into an `svg` subdirectory). 2. Create a schema customization in compact syntax---`dbsvg.rnc`: ``` rnc namespace html = "http://www.w3.org/1999/xhtml" namespace db = "http://docbook.org/ns/docbook" namespace svg = "http://www.w3.org/2000/svg" include "/path/to/docbook.rnc" { db._any.svg = external "svg/svg11.rnc" db._any = element * - (db:* | html:* | svg:*) { (attribute * { text } | text | db._any)* } } ``` Or, alternatively, you can use the XML syntax of RELAX NG---`dbsvg.rng`: ``` rng ``` 3. Now use the customized schema (`dbsvg.rnc` or `dbsvg.rng`) instead of the original DocBook schema. **Q:** Is it possible to use the previous two customizations for MathML and SVG together? **A:** Yes, you can create a special schema customization that combines both MathML and SVG with the DocBook schema. In compact syntax, the merged schema is: ``` rnc namespace html = "http://www.w3.org/1999/xhtml" namespace mml = "http://www.w3.org/1998/Math/MathML" namespace db = "http://docbook.org/ns/docbook" namespace svg = "http://www.w3.org/2000/svg" include "/path/to/docbook.rnc" { db._any.mml = external "mahtml/mathml2.rnc" db._any.svg = external "svg/svg11.rnc" db._any = element * - (db:* | html:* | mml:* | svg:*) { (attribute * { text } | text | db._any)* } } ``` Or alternatively in the full RELAX NG syntax: ``` rng ``` **Q:** Are there any other examples of schema customization available? **A:** Sure. Some of the are listed bellow: - [Sample customization of ITS and DocBook](http://www.w3.org/TR/xml-i18n-bp/#docbook-plus-its) - [Examples on DocBook WiKi](http://wiki.docbook.org/topic/DocbookSchemas) ## Tool specific problems **Q:** I\'m using Altova XMLSpy to validate DocBook V5.0 instances against the W3C XML Schema (`docbook.xsd`). XMLSpy complains about undefined xml:id attributes? **A:** XMLSpy always uses its own bundled version of `xml.xsd` which unfortunately doesn\'t define the xml:id attribute. The bundled version of `xml.xsd` is hardwired into the program and cannot be replaced by a newer version. To solve this problem you must upgrade to version 2006 SP1. # {#references} RNCTUT Clark, James -- Cowan, John -- MURATA, Makoto: . Working Draft, 26 March 2003. OASIS. NVDLTUT Nálevka, Petr: . XMLID Marsh, Jonathan -- Veillard, Daniel -- Walsh, Norman: . W3C Recommendation, 9 September 2005. DB5SPEC Norman, Walsh: . Working Draft 5.0a1, OASIS, 29 June 2005. [^1]: In a very few places RELAX NG specifies datatype like number (mainly for length specifications) or enumeration between `0` and `1`. In general those datatypes can be also supported in W3C XML Schema, but currently this schema is generated from DTD which lacks datatype information. [^2]: RELAX NG grammar enforces exclusivity of several elements. For example if you have title inside info then it is not allowed to have another title outside info. Similarly, models of HTML and CALS tables are separated and validated properly, where in DTD and WXS only union of both models is available. On other places co-occurrences enforces particular content model based on presence of specific attribute or attribute value. Please also note that in theory co-occurences can be validated using Schematron, but the current DocBook schema uses RELAX NG for these definitions. Schematron can be used only for validation, whereas grammar based schemas like RELAX NG are useful also for other purposes like guided editing. [^3]: Check whether ID/IDREF links are pointing to element of corresponding type. For example that footnoteref points to footnote. [^4]: For example consistency of segmented lists, only one term inside term definition etc. [^5]: Prevents improper nesting of elements, like admonition inside admonition. [^6]: The examples in this section use `docbook.rng` as the schema location. If you want to create a portable schema customization you should use a standard web-accessible location like and then use [XML catalogs](http://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html) to resolve this location to your local copy of the schema for improved performance. Unfortunately, at the time of this writing not all RELAX NG validators support XML catalogs. [Pg 74] For response, Shorty handed his cap, his gun, his bottle, his blanket-roll, his belt and haversack to Si, rolled up his sleeves, spit on his hands, doubled his fists, and stepped forward into a boxing attitude. The Deacon looked a little regretful at the shrinking of the contents of the kettle, made by taking out the cupful, and said: The negresses, who had been watching their master depart, set to screaming, and the old woman rushed back into the house and blew the horn. The Deacon thrust his revolver back into the holster, caught the old man with his sinewy hand, tore him from the seat, and flung him into the fence-corner. He sprang into the seat, turned the horse's head toward Chattanooga, and hit him a sharp cut with a switch that lay in the wagon. "I cannot get you out of the army too quickly. Sign this, and leave my office, and take off your person every sign of your connection with the army. I shall give orders that if you appear on the street with so much as a military button on, it shall be torn off you." "You will, eh?" sneered Shorty, covering him with a heavy Remington. "How'd you like the looks o' that, old butternut? Your murderin' dirk aint deuce high. Move a step, and you'll know how it feels to have daylight through you." "Then it was only a difference in degree, not kind. Was he not accomplishing what he was ordered to do?" "I don't know." Again a silence. Dodd's hands unclasped: he made a gesture as if he were sweeping something away from his face. "There ought to be something else. Even on Earth, even before the Confederation, there were conscientious objectors." "Okay, it isn't," Albin said. "So make it a game. Just for a minute. Think over all the jobs you can and make a choice. You don't like being here, do you? You don't like working with the Alberts. So where would you like to be? What would you like to do?" He came back to the chair, his eyes on Dodd, and sat suddenly down, his elbows on his knees and his chin cupped in his hands, facing Dodd like a gnome out of pre-history. "Go on," he said. "Make a choice." "Well, don't ask questions," Albin said. He kept one eye on the shifting mob. "If there's anything good for you to know, you'll be told. Meanwhile, just don't ask any questions." Norma's hand drew back again. "You can't just sit back and wait for them to come!" The daughter must be the girl who was talking to him now. She sat on a little stool by the fire, and had brought out some sewing. "He's warked fur it all the same, surelye," said Cooper of Kitchenhour. There was a wicket in the northern gate, the common outlet for the domestics, which, as Holgrave had anticipated, the servitor had not closed after him. He entered, and stood within the court-yard; he heard the sound of voices, and the tread of feet, but no human being was near: he paused an instant to consider, and then, with the swiftness of a deer, he sprung towards the stables, and entered the one appropriated to the select stud of the baron. A lamp was burning, but the men who attended on the horses were now away, quaffing ale to the long life of the heir. The baroness's favourite palfrey was lying in a stall; he stept across the animal, and, after pressing his hands on various parts of the wall, a concealed door flew open, and a dark aperture was before him. He stooped and passed through, and ascended a long, winding flight of steps, till a door impeded his progress; he opened it, and stood in a closet hung round with dresses and mantles, and displaying all the graceful trifles of a lady's wardrobe. There was a door opposite the one at which he had entered, which led into the baroness's chamber, where there were lighted candles, and a blazing fire on the hearth. The floor was thickly strewn with rushes, and he could just perceive the high back of a chair, with the arms of the family wrought in the centre; he paused and listened; he heard the faint cry of a babe, and discovered, by the language of the nurse, that she was feeding it; then there was the hush-a-by, and the rocking motion of the attendant. In a few minutes, the sound of a foot on the rushes, and "the lovely babe would sleep," now announced to Holgrave that the child was deposited with its mother: then he heard the curtains of the bed drawn, and the nurse whisper some one to retire, as her ladyship was inclined to sleep; there was another step across the rushes, and a door was softly closed, and then for a few minutes an unbroken silence, which the nurse at length interrupted by muttering something about "whether the good father had come yet." Again there was a tread across the rushes, and the door again was gently closed; and Holgrave, after a moment of intense listening, stepped from the closet, and entered the chamber. In an elevated alcove stood the bed of the baroness; the rich crimson hangings festooned with gold cord, the drapery tastefully fringed with gold, even to the summit, which was surmounted by a splendid coronet. Holgrave, unaccustomed to magnificence, was for a moment awed by the splendid furniture of the apartment¡ªbut it was only for a moment¡ªand then the native strength of his soul spurned the gaudy trappings; he stepped lightly across the spacious chamber; he unloosed the rich curtains¡ªthe heir of De Boteler was reposing in a deep slumber on a downy pillow; beyond him lay the exhausted mother, her eyes closed, and the noble contour of her face presenting the repose of death. For an instant, Holgrave paused: remorse for the deed that he was about to do sent a sudden glow across his care-worn face¡ªbut had not the baron destroyed his offspring? whispered the tempting spirit. He raised the babe from the pillows without disturbing its slumber¡ªhe drew the curtains, and¡ªhe reached the stable in safety, closed the secret door, and arrived at the postern, which was still unfastened, passed through, and gained his own door without impediment. HoMEÒ»¼¶×öÈË°®È«Ãâ·Ñ ENTER NUMBET 0017
dawo6.com.cn
www.fage4.net.cn
latou8.com.cn
jusan8.net.cn
renan5.com.cn
www.budou9.net.cn
desuo2.net.cn
www.hezhu0.net.cn
www.aqbe.com.cn
www.juela0.com.cn
� 全球最大西西人体网 亚洲老熟逼图 大色哥乱伦小说 欧美图片av大视频 女囚奶子 我要操成人电影 WWW.RU345.COM WWW.SXKBK.COM WWW.1111C.COM WWW.HHH563.COM WWW.33SP.COM WWW.NBZLHB.COM WWW.HHH527.COM WWW.QSYFX.COM WWW.91P05.SPACE WWW.18SUSU.COM WWW.AV6601.COM WWW.DLRYX.COM WWW.DYTTBBS.COM WWW.MHFKJ.COM WWW.188BIZ.COM WWW.IBB6.COM WWW.JJ-XX.COM WWW.SAE85.COM WWW.SEYATOU.COM WWW.YEYERE.COM WWW.SDTYJT.COM WWW.2015UZY.COM WWW.55HHH.COM WWW.XX5432.COM WWW.TJLIJIN.COM WWW.TXT35.COM 702renti 久久热gg333 丁香婷婷五月色视频 wwwOOSIHUCOMmagnet 色姑娘插妹妹 美足h 好叼色在线视频 马苏被艹下载 国外国外恋足网址大全 搜索www770wwcom www色123aaaacom 桃色天堂爱爱视频 日韩激情小说 wwe97yescom 欧美激情伦理性爱电影 偷拍自拍做爱电影wwwffff84com 师傅搞徒 淫荡的嫂子magnet 成人情涩网站 幼女高清无码 先锋97色色色 银虎导航用什播放器能看 少女乱伦短文集 迷人av 能看调教图片的网站 搜索女人爱操的黄色小说 偷偷撸在线视频2016 很多人一起乱搞做爱 seqingdianyingwangz AV幼幼 狠狠干爱橾射在线www789lllcom 大奶淫穴图 美女自摸动态图 WWW460TVCoM 播乐子成人喜欢的在线视频 超碰繁体 谁有人与狗的视屏 电车魔女野猪网 黄色视频董卿 色色色色色第四色 东方在线50o 大胸国产在线 林钰轩露两点 调教同学成熟妈妈 小宝亚洲色图 菲菲视频AV 先锋最稳定的资源站 国内饥渴少妇放荡视频 亚洲1AV 色色夜午大片 欧美制服HD 淫妻按摩录 www83lllc0m 在线视频亚洲小说专区 西西人体健康视频 怡红院首页一百度 av最大网站在线观看 爽爽爽日本在线视频 爱奶子射小穴 手机罗马影视 美女色社区 超碰在线teen 啪啪啪激情视频ed2k 淫荡少妇激情小说明星淫乱 lol撸址 东方A∨在线亚洲 百性阁另类综合人妖 奸淫幼女视频微信 换母俱乐部 www免费在线AVcom www88pepecom 222lu众里寻她千百撸 伦理乱伦zxfuli福利社 对着ladyboy撸管 丰满少妇狠狠撸 色系大片观看方法 うるや真帆影音先锋 轻射影院色播 日亚洲mywife色图 强奸幼女的大肉棒 制服AV下载 av按摩网址 巨乳波霸撸撸 成人女人裸舞 99kk7下载 porn影院 通辈乱轮 黄色J插B 性爱hh 三级经典色妹妹 欧美呦女视频 sssaoinfo 东方av官方 美国妞迅雷 1024核工厂论坛 保姆17p 加勒比套图下载 迪加客服电话升级 波多野统衣后母的诱惑 打开av2 色色就去吧mp4 变态伦理下载地址 de野外潮吹 韩国女人交媾 7sssss人与动 都市激情 综合网站 崎性交配小说 乱伦 淫 ti WWW_HH650_COM 骚货的菊花失守 弟弟色色人和动物 什么网站可以看色图 美女裸体艺术图片15p 人体模特汤芳图片百度图片搜索 万妮恩人体艺术 WWW_43SR_COM 3p美妇到高潮 国内老女人av在线视频 caoliu文学交流 大胆西西露阴艺术 振动器黄色网站 一 级黄色图片 小说y淫荡寡妇 苍井空美臀图 成人涩小说集 骚妹妹私穴 色女15 26uuu图片 av580com图片 婷婷五月天新网址 翁媳乱伦故事 母ziyinluan 按明日香 制服美女性交图 兽兽自慰视频 西西影音qvod先锋 伯乐与千里马 威海房地产信息网 色丁香色婷婷成人色 另类女子性交视频 丁香五月人与动物性交 百度影音成人高清无码 欧美老姐姐 好看丝袜av 兽兽足交 美女大鸡巴欧美 大胆美女人体私密处露阴毛套图 图片区 在线视频 操粉木耳人妻18p 大便系列种子 现代女性性交大全 浪少妇露黑逼逼图片 奏国为什么是人妖 张柏芝paoturentiyishu 性交真实图片 先锋影音撮拍 91zizicom神马电影 少女阴户 色猫网444 WWW42BOBOCOM 激情院 西西全球美女人体艺术网图 美女美穴图片30p 性色妹妹 可以用大肥佬看的色网站 cao骚bi 野兽人交 骚小姨艳照 母娘间漫画 星空宽频三味影院 插插综合图看黄色一级图片 拳交训练4torrent 看大鸡巴操逼视频 家庭教师激情乱伦小说观看 日本熟女电影说中文 97色一个导航 恋夜秀场真人裸聊 女儿引诱爹地乱伦小说 俩性网 653se 我和保安玩鸡巴 未来影院神马影院播放不了 亚洲色图另类性爱 熟女情趣泳装 喝尿饮精超长版 少妇插五月 约炮做爱全过程小说 两性的生活视频教程 韩国美女主播阿里快播 美国教育av电 日本色倩女星波多野结衣 妹乳房久草淫淫 wwwo8m7ccom 成熟夫妻自拍 淫荡少妇问 妹妹色欲 性奴晒淫图 成人消暑都市激情校园春色 掰穴pmneihan8com 偷拍自拍亚洲色图真实强奸 靓女懒鲍 强奸乱伦视频手机专区 双胞胎中出 www1234dfcom亚州在线 撸撸鸟AV亚洲色图 VS色色国王 肛交综合网 关于五月天激情 天天爱姐姐色色 搞搞电影网欧美图片 欧美大色哥 欧美课体熟女 换妻做爱小说 成人3D动漫淫淫色色 激情另类卡通亚洲欧美 野香春色 野田春色 求在线观看h网 去哪网看黄片 有名的黄色小说 QVOD影视 新日本AV片 2porn在线 美眉骚导航(荐) 韩国人为什么叫棒子 撸撸看电影 淫妻天堂 丁舌五月 真人版XO CREAM PIE漫画 深芳野磁力链接 天天一鲁 老司机影院视频福利一区 任你干AV 小姐草视频 小米手工酸辣粉手工粉jv168 (欧根纱 | 上衣) -(红米手机皮套) 强奸视频app 泄欲哥 在线里番 日韩色的 日本男优视频百度云资源 欲望人生王梦莹陈东 日本无码母子黄片v卡 余裕で三连発 在线观看皇片你的懂的 日本人啪啪啪的视频无遮 日本少妇制服丝袜高清视频 影音先锋片资源q814 重口变态区 啪啪啪研究所 亚洲在线视频中文字幕 rct中文字幕 午夜福利偷拍自拍 人休艺术张伯 免费精品成人小说视频 中文字幕 a v资源 人妻熟女小说 农村荡妇偷情-级片 三邦车视97神马电影 日本交尾图 一色屋任你搞经典免费视频 很黄很色很污的视频(高清在线) 小姐在线视频 酒店强x漫画 亚洲区自拍综合图区 adn071在线观看 jappinesemilking sese国产自拍 逢泽莉娜汽车完整磁力 有b吗一站视频在线观看 姐姐的天堂av 东方vs免费观看进入 啊啊啊欧美av 嫩穴被操 澳门皇冠国内自拍 ky福利导航 Xiao77论坛 - Powered by phpwind 初中女生磁力 大学生破处视频 自拍 致命注射地址迅雷 安装操逼小姐视频 97极品成人影院 955mmmcom 抖阴成人 182tvb直播大香蕉 美祢藤播放 iAV在线播放 日韩 在线 538po62r62n视频 马阴茎进入女人阴道视频 有色视频 黄片操逼视频 厕所自拍偷拍超碰 大吊爆 梦莉视频导航 哥哥搞在线播放 偷拍走光大尺度 濑亚美莉步兵在线视频 南日p无码午夜影院 全国最大黄网4438 魅心福利视频 丈夫酒醉老婆被同事 绝品圣手花红酒绿资源 夜视频 胖美女 999re青草草在线视频 理伦视频亚洲日本图片 日本SM在线视频 凌辱日本空姐 色先锋下药迷晕美女视频 zooski兽皇 狂草视频在线 荷花在线播放自拍 台湾无码A片 性感美女做爱视频观看 性奴调教群交文 香奈儿·普雷斯顿级网站 小清新视频污下载 一本道资源先锋站 日本黄色网站讨厌马赛克 亚洲 日韩 在线 制服 桃色影院爱啪网 jiureshipin 色综合网导 老司机福利 ae86 饭岛爱无码在线播放 图片区小说区香蕉 小鸟酱30g 密码 重口味av磁力链接 林心如与狥交 www182、com a岛国在线观看 先锋影音伦理电影单身部落 日本一本道毛片 心经日本宜春院 操美女思瑞 国产自拍ac 草榴根成人影院 人人看人人摸人人操人人草人人看 亚州欧美成人 224tt,com ed2k 八爷带你一路撸到黑 www4438x10 ipx050在线看 色悠久久桃花综合网 看电影来5566最新地址 成h人视频软件视频免费下载 sw312在线观看 被窝福利九州 成人动画片白雪公主在线观看 中国伦理自拍电影 亚洲黄网在线 老司机午夜电影在线观看 颜射大奶在线播放 caoporn在线男 午夜福利在线福利人与兽性交福利7o 色和尚36bibi 夜秀live最新v视频在线播放 日本免费强奸黄片 649c网站 橘梨纱视频在线 日本欧美成人视频 草民影院六度dy888 孕交视频javhd 线上AV高清 赶尸艳谈在线播放 欧美名人女星不雅视频 日本 变态深喉正在播放 亚洲第一在线观看视频 x视频 国产自拍肛交 国产偷干 种子 magnet 裸身美女肛门软件视频。 少妇激情插着视频 梅麻吕全集在线观看 寂寞女人的深夜自拍小视频 情迷思儿 人人看人人上 人人干操学生 七彩福利视频 前入式操逼视频 色www非洲免费视频 四虎影院176 海瑟格拉汉姆大尺度电影 狠狠搞 好日日中文字幕 牛牛在线福利视频 【黑丝蔡依林】超像蔡依林的跪坐式口爆,张嘴接下精液,超爽画面感。 很恨鲁在线视频播放 有奶水的女人伦理片 里番御姐在线 素人RBQ35v 波多野结衣人妻性奴隶的那个片子番号是多少? 爱爱视频黄片a片 周达雄男体 咪色色琪琪色 26uuu小说 magnet 美女大桥AV隐退 光棍影院 第九影院 41312 333伦理电影 超碰视频在线观看a 国语巨乳magnet视频大全 母乳熟女电影先锋影音 MIKU亚洲无码视频 。橘梨纱 mp4 crdytpzp 迅雷福利种子你懂的 sesedaxiangjiao 色图美国在线 av电影 玉蒲团 97色伦2018无密码视频 清风阁视频网战 性爱乱伦视频 永久免费成人在线高清无码 第四色先锋色色 黑人找妓女喜欢出钱,,妓女高兴马上扒光衣服裤子给黑人快上的视频播放 男人和美女人操逼 爸爸爱比综合 迅雷在线草裙 男人生殖器人体艺术图片 插插插图片网 欧美色妇乱伦15p 77dizhigmailcomm 美妞屄屄 草逼高清p 偷拍男按摩师视频 五色电影网站 女儿的嫩屄 色女淫女文 人曽交配视频 色姐jie网 动漫种子 ed2k 张莜雨大胆人体润艺术 谁知道qq空间看片的号 色性小说网 我被公狗交 膛内射精 大肉棒黑粗 五月27号出生的篮球明星 我和哥哥乱伦 天涯论坛 人体模特汤加丽兽兽门伦理电影 肏逼的游戏 大奶裸体美乳 湿润的小穴动态图 xfplay尻 林利霏李宗瑞 嫂子小婷 妹子的鲍鱼图 偷拍自拍第1弹 宬人视频在线无插件 李宗瑞完全 美女人体艺术影音先锋 日本女演员松板庆子 都来撸淫妻小说 李宗瑞视屏下载 欧美性爱第四色百度 美女裸逼屄图片欣赏 色精液大餐 极品激情电影 肛交 北妹皇后风月 关于儿子和母亲乱伦小说 巴巴人体艺木 和农村大妈做爱 真实乱伦小说 ok3699jiunengshuangle 抢票软件还能用吗 梅林传奇结局 丝袜骚女秘书系列先锋影音 美女大胆bb照 在线电影深爱五月天成人五月天 在线激情艺术 人体西西人体 美女班长被我强奸 shelang333 h版电影观看快播 夜夜嗷叫爱色综合网站 黑人大jb照片 苍井空免费在线视频 先锋影音成人云播 野营在树林里的男生女生激情四射 郭美美阴道 制服丝袜松岛枫新卒美人女教师性奴隶 幼女阴蒂 操欧美少女逼 2016妞妞 爱逼网美女喷水 色中色电影导航在线 女少妇同事贴吧 撸撸插色久久 盗摄极品来按摩的美丽女性客人rmvb 荡妇爱色 视频偷拍逼 淫荡大奶子 邓紫棋图片亚洲色图偷拍自拍 肛交尹恩惠 天臧图片大全 肥女人做爱图 亚细亚之瞳av 粗鸡巴从后面插入春暖花开 动态图片huangs 农村老汉日女儿小穴 幼女强势进入 junmeinu rbd261 99色为天论坛 萩原舞种子 讯雷成人电影网 调教上高中的小姨子 深喉手机在线bd高清 熟妇漫画合集 大乳老妈 老熟女大阴道 女神浴缸沐浴直播 爆乳女人性事 少女大黑屄 白嫩丰满骚妇视频 WWW淫民色色C0M 粉嫩私处12pwwwdizhi99com 性吧娱乐清读 狠狠撸网站打不开 亚洲色图欧美色图自拍偷拍激情小说人妻小说 发情老色鬼想女人找女人操屄摸大奶孑骚女人急摸龟头大鸡巴 老女人免费色网自拍视频色网 19isecom色哥哥帝国 世界红酒品牌 酒店约炮良家少妇露脸 熟少妇自拍偷拍图 偷拍人妻亚洲另类 日本武藤兰黄色影片 先峰撸撸电影网 97小格式在线视频 先锋巨乳涩 啊舔那里快操我 变态另类奸淫日本av 门卫大鸡巴 韩国三级电视连续剧 黑妹爱爱迅雷下载 香港哥哥天天射日日鲁 好屌日夜夜 从哪里看成人电影 我要看一丝不挂女人的逼逼和大奶子图片 搜索6666kecom 梓唯衣Av在线 无码中文字幕塞外青楼这是一个 西条琉璃巨乳姐姐内射 riyelu国语 AV淫荡妻子 k8经典先锋k8经典片影音先锋 一级黄片学生被强奸的处女 乡土乱欲小说txt下载 半夜黑人操逼 偷偷干狠狠干艺术 1免费成人网裸体会场 美女xingjiao18p 爽啊15p三洞全开 胖女同 性爱yinsipianyijei 校园激情人妻小说 2015Tv丶C0M 女性射精orange wwwonlyjizzcom 色tv网 巨乳自慰20P 日韩巨乳无码在线视频 爱打炮视颏 五月天偷拍自拍强奸乱伦影音先锋在线观看 色天使美国发部站 292kkccom 中文往往对电影 操笔小说 luo裸贷视频完整版 免费上床动态视频 东方av在线偷拍自拍正在进入 丁香五月天人与动物曾交无吗 淫荡熟妇16P av女神第一社区在线 久久资源magnet 最大胆子的裸鲍艺术 乱伦少妇magnet 超碰视频A片在线视频 搜索91 亚洲成人XX影院 疯狂狂插性爱图 欧美大奶美女做爱 色就是色111 午夜啪啪成人在线视频 色猫444 一夜五次郎导航 亚洲是色 冷艳爆乳母亲 妹妹成成人电影 大色狼免费视频 月色色女装 2233p 在线影院淫色熟妇 蝴蝶谷成人AV 米奇影院国产裸模 夫妻做爱全过程 850黄色网站人与兽交配视频 亚洲在线做爱 色姐妹插姐姐wwwhh5666combb2yycom 琪琪热热色原原网站亚洲天堂 国产寂寞少妇推油高潮 撸一撸欧洲色图操逼 国产自拍偷拍字幕 好紧爱爱 小骚货性事 欧美色图亚洲色图熟女乱伦偷拍自拍另类图片 淫姐姐影院乱伦小说 美裸体图片 大嫂的淫肌 成人搞搞电影网 看到b的美女操b 亚洲色图亚洲大色网小色网 17n17奔雷手 日日干狠狠干在线 草榴色播放器 裸体的中国女兵很性感 ymdd099磁力 做爱电影快播在线观看 www88bbbcom csss色小姐 公媳乱伦xxx wwwtt44 色尼姑av打造第一 XXX性生活群交高清视频 うるや真帆影音先锋 缴倩 纵犬渚伏mp4 ogli 先锋资源比特 制服丝袜高清无码先锋影音 手机在线播放h网站 婷婷一1138xcom 巨乳av综合 一本道色宗合 午夜免费天天看 亚洲se手机 3366vod下载 99热这里只有精品aesheencom AV亚洲色图东方 7777电影院 美女性交下载 强奸乱伦胖mm 5p口交 男男性交mp4 乱伦色93zzzzcom 移动网络偷拍自拍 俺也色20p 爱先锋多瑙电影网 与岳母乱伦肏屄小说 都市激情保姆 戴比 世界最漂亮丝袜妹妹 欧美阿姨16p 黄逼下载 第4色首页 妹妹被球干图b 欧美美女捰体 撸绿色 亚洲 嫂子 阴唇 动物性交大图 掰开人体私处 抽插朱迪 被乳交的美女 图 俄顶级性交在线观看 插进 丈母娘 阴道 自拍视频支持手机观看 摸姨妈骚穴 黄的qq 亚洲vv620 九零后大黑逼 影音先锋不能看日本片 索尼fm500h 我操了妹妹的小穴 迅雷在线观看黄色视频 溜冰草逼 黑b 少妇肥穴15p下一篇 韩国成人激情电视台 色撸撸影院导航 08艳照 女人性交变态 tuolekutoujiucaobi 苍井空的最黄影片 欧美大胸炉体 h公开插入 内涵鸡巴 康筱婕 ngf 周国平散文读后感 半球燃气灶 苏丹草 牡丹江二手房网 2013亚洲音乐节中字 七夕青色五月天 操操操狠操视频 佐久间美女人体 春光无限逼逼高清图片集锦 大鸡巴哥哥干得好爽 黑鸡巴插进去了图片 与胖妞做爱 家庭乱伦校园春色激情小说 日本美女嫩逼写真 家庭淫 o2kkkc0m 影音先锋人与动物色片 人与动动物电影网 快播兽交网站 黄色美女bb群 red549 少女阴部艺术 华语地区最大国产自拍视频 大尺度张筱雨裸体艺术图片 人体艺术开档 少妇的两片嫩肉 一骑欢射 大胆扒开阴唇图片 新亚洲第一页 狠狠啪啪精品在线 正在播放中国sm绳艺 互舔肉肉小说 papa俄罗斯美女 正在播放家庭教师母女通吃 搜索www26jjjjcom www78rbcom怎么打不开 东方成人zaixian 91promfree 直播成人狼友电影 男人天堂这里都是精品 日本av骚女成人网站 两性66妈妈和妹妹 www999udcnm 初中萝莉lulu 摩擦鲍鱼 亚洲图片妈妈供我上学 小龙女色色 powerman成人 日av动漫手机在线观看wwwho2ucom 深圳爱影dvd导航官网 伦理片百年合 夜夜鲁夜夜射 性趣阁论坛地址一 亚洲图片区自拍偷拍图片aw 人与动物杂交小说短集 欧美女同性恋自慰图图 强暴和尚影院 做爱强奸伦理图 女人肏屄图谱 有声小说官仙 春色漫画 樱井莉亚作品美誉 小泽玛利亚小礼帽 酒色网/ yeye撸在线影院 午夜看影院 免费美女视屏 快乐夫妻吧谁有E 色娃娃高清电影 新商品アダルト movies在线 采花堂G谁有E谁有E 啧啧撸 色人格阁姐妹爱 色系军团漫画全集 李宗瑞奇奥网影院 nikky case迅雷 天海翼av高清无码下载下载 ZW成人 深爱开心五月图片区 天堂av 视频av 在线av 大色哥g 明里有香中文字幕影音先锋 午夜男日B视频 日本女优的小阴唇视频播放 中文字幕国产偷拍 偶偶福利社 青青草精品三级经典 青青草原AV苍井空 秋霞网秋伦理网 秋霞偷着女厕所 日韩女优你懂得 在线内射大奶小穴 浴室淫娃 日本亚洲高清视频在线下载 日本一本道免费高清 淫夜 magnet 日本少妇cosplay母狗 日本一级性交视频 91校长视频 福利女厕偷拍视频 ts 这女的喷奶好牛逼 西瓜影音 125电影影视 七色色导航 波多也结衣步兵正线 柳岩5p haodiaoyin这里只有精 三浦春佳无码 小米粒裸播 素人搭讪开房!性交偷拍流出影像 3p舔得受不了好爽视频 大陆佖理片 主播xx秀链接 下载 艹逼图片视频软件 美国 深夜福利 直播 爆操日本女优骚逼出白浆视频 10000部小黄片 青青草青娱乐视频分类 废柴兄弟2在线观看免费 dvdes 631 在线播放 赤井美月 大喷水无码种子 草硫影院 任你爽任你干任你操 哪个网站可以看性爱大生 拉风色中色影视AⅤ 淫色视频网 在线 cao2cao 91bb91进不去 大款汤先生酒店落地窗后插极品黑丝开裆外围女完整版 处女16岁视频在线观看 大肥女视频@StopFuck 自拍偷拍 后入 天天啪久久爱国产门 韩国三级电影强奸女主播 下载 youzzjj影视 色色五月天综合 第九影院bc 帝国av手机在线观看 欧美无码三级片 黄鳝门视频福利网盘 自拍摸BB在线观看 人兽理伦理片 mp4 五月天午夜剧场 王丽丁的胸 忧忧啪啪 cop在线视频 国产成人扬桂妃在线 好吊妞av 网红自拍露脸在线观看 熟女扣逼av 957私房视频福利 梅麻吕1至12集 狼人成人 刺激，约炮骚女，直接在商场厕所开战，旁边 接摩人妻 日韩无码在线播放免费 日本美女后入视频网站 国产自啪九洲AV 501伦理 QVOD制服伦理 成人avqq163音乐 1英语影音先锋资源网 黑人磁力无码av 久久爱视频免费在线播放 浓密的体液 全裸美女巨乳视频 迅雷哥潮吹种子 小萝莉影院福利 小黄网站在线观看 小妖精影院在线无码 欧美日韩在线五码 www,6699yy,com 色老播放地址青 青草色导航 日本毛片免费视频福利社影院 卡通3D―第5页 超碰熟女人妻 国语对白国产视频区 萝莉制服自拍 色姑娘在线播放一本道 新妈妈 ftp 国产在线王小倩 操逼直播磁力 gav老司机 xo168色多在线 AV导航永久发布 集体在线无码 x╳x女孩 人人爱av 97韩国影院n g yuan 怡红院成人电影偷拍 草杨幂的av 病态爱慕百度云 苍井空a片百度云 宝贝儿好深夹的太紧了 qianbai鲁 波多野结衣加嘞比在线观看 酒店开房做爱迅雷下载 magnet 超碰视频资源免费高清人妻 内射妹子免费视频 欧美成人视频大香蕉 私密按摩师下架 强奸帅哥的视频 视频 口爆 大奶 aa免费网站 magnet 男女靠逼免费影院 高级性交视频 午夜剧场噜 北度影院 国产调教手机在线 国产自拍视频 yunfile 不卡成人啪啪 操逼动画片 不毛之地黄片 啪啪啪免费观看在线 疯狂 露脸 在线 狠狠射干在线观看 男人天堂毛片 西瓜影音 亚洲综合偷拍视频观看 咪咪网 国产自拍 制服老师视频 澳门皇冠四虎视频地址 每日更新成人电影 极品外围女模特拍摄时被摄影师勾引 前田香织380在线播放 91金龙鱼最新-气质漂亮的良家少妇苏小小偷偷兼职做楼凤 操骚乱伦电影 怡红院新网址 脱光干叉 亚洲风情偷拍区 大桥未久生物教师 抹茶视频 ?人巨大マラ VS 巨乳知的ママ 青井マ 下载 黑丝袜制服美女少妇在家被强奸视频全过程视频 皇冠国际在线看片 黄色论坛 黄本子福利全彩聚集 狠狠射干b 欧美激情在线 花花的你懂的 夫妻性了的生活一级色带 邪恶岛上帝店长 阅B影院 heshenshenzuoai 91P0RN 极品F奶素人美娘为替老公还债,被陌生猛男捆绑爆操后入强奸 人人澡夜夜澡 美上セリ91云 欧美色视频 日本片 27报电影 啪漫免费 欧美幼老色与狗色 长春一级毛片 豪乳爱爱视频 韩国限制级女主播 国产呦呦视频 下载 chinese农村夫妻vioen 经典无码a免费手机视频 动态做爱LOⅤE 三级伦理电话 美女午夜大片 15 中年露脸自拍 久久电影网2018重口味 三级无码影音 午夜福利李宗瑞 996AV免费视频 ysy成人视频 免费av短片 操逼口交内射 做爱要插在哪里 安装sao200专用播放器 淫荡女歌星 WWW_AVAVSSS_COM 磁力链接东京热 寂寞穴