The purpose of studying the open electronic book publication structure is to provide a specification for the content expression of electronic books. In particular, it should be noted that: · This guidance technical document attempts to provide minimal general guidelines for content providers (such as publishers and other people or institutions that have displayable content) and tool providers to ensure that the content of electronic books is faithful, accurate, accessible and presentable on various electronic book platforms. · This guidance technical document attempts to reflect the existing status of various electronic book content format standards. · The goal of this guidance technical document is to provide a format for electronic book content distributors such as publishers, agency machinery and authors, so that they can provide users with electronic book content suitable for a variety of reader systems. The premise of this guidance technical document is that in order for electronic book technology to achieve greater success in the market, reader systems must be able to easily access a large number of works of various types. GB/Z 18906-2002 Open electronic book publication structure GB/Z18906-2002 standard download decompression password: www.bzxz.net
The purpose of studying the open electronic book publication structure is to provide a specification for the content expression of electronic books. In particular, it should be noted that: · This guidance technical document attempts to provide a minimum common guide for content providers (such as publishers and other people or institutions that have displayable content) and tool providers to ensure that the content of electronic books has fidelity, accuracy, accessibility and presentation on various electronic book platforms. · This guidance technical document attempts to reflect the existing situation of various electronic book content format standards. · The goal of this guidance technical document is to provide a format for publishers, agents, authors and other electronic book content publishers so that they can provide users with electronic book content suitable for a variety of reader systems. The premise of this guidance technical document is that in order to make electronic book technology more successful in the market, the reader system must be able to easily access a large number of works of various types.

TCS 35.240.30
National Standardization Guiding Technical Documents of the People's Republic of China GB/7.18906—2002
Open electronic-honk puhlicalion structure
Open electronic-honk puhlicalion structure2002-12-04 Issued
China's Long-term Common Benefit
General Administration of Quality Supervision, Inspection and Quarantine
2003-05-01 Implementation
3 Adaptive Reference Documents
Terms and Definitions
6HTMT.XMT.Direct Standard Structure
(SS Latitude Average
Attached A (Data Note) Element Loss Type Table
irKoNrKca-
CI/Z 189062002
GBz18962002
The technical document format adopts the upgraded forum bkrre ten release sub-station structure 1). The original handover book is attached with BH gas appendix (EB document DT and the total rate description is adopted, please refer to tlup://uyeneurokur for more information. This technical document is for reference only,
The technical document of this guidance document is for reference only. This technical document of this guidance document is for reference only. The technical document of this guidance document is for reference only. The information industry of the People's Republic of China is under the jurisdiction of the Ministry of Information Industry of the People's Republic of China. The technical document of this guidance document is the guiding technical document of the Aluminum Car Workshop of the Ministry of Information Industry of the People's Republic of China. The general register is: the National Institute of Technical Standardization, the Institute of Metrology Technology of the Chinese Academy of Materials Science and Technology. The drafters of this guiding technical document are: Huang Ranjun, Xiao Ming, Li Honghui, Gao Xingbao, and others. The scope of this guiding technical document is: I
iKAoNrKAca-
GB/7.18906—2C02
The structure of open electronic book publications is to provide a standard for the development of open electronic book publication sites, with special needs:
, This guiding technical document attempts to provide minimal communication for content providers: such as publishers and other people who donate content or provide content to the public (such as customers) and workers, to ensure that the e-book service on all kinds of electronic book platforms has guaranteed content, certifiable content and currentness.
·This technical guide is a collection of electronic books in various formats. This technical guide has the following objectives: 1. It provides a format for publishers, academic institutions and authors to publish electronic books. 2. Normative references
The following documents become the terms of the indicative technical documents through the reference of this technical guide. This is a detailed and small document. All amendments (including error-proof contents) or revisions are not applicable to this technical document. However, it is encouraged that the parties to this technical document should study whether the latest version of this document can be used. For any referenced document without a previous version, the latest version shall apply. This is a technical document. BT7408 Data element and information exchange format 1st edition and time representation (2VISO851GB3, "Multi-bit code symbol set (1S) Part 1: Basic aspects of the architecture (idt rIF Ios4a 1)
G3T172 Product 1 Information Technology Requirements and Guidelines for Video and Decoding of Color Video Programs (Q150/EC10918)
3 Terms and Definitions
The following terms apply to this technical document. 3.1
Basic Documentation
DKR Basic Documentation
DKR Basic Documentation is the document that defines the content of this document. 3.2
Content Provider
A publisher, author, or publisher who provides content to a publisher or publishers in a format that is intended for one or more readers.
It is recommended that The unused function depraeaterl
wood guide technical document allows the construction of continuous cutting function, which may be modified in the future version of the technology. GB/Z18905—2002
Extended OEB real file core xleledOLdaumem
In the extension defined in this guide technical document, the structure of the guide document is not specified in the document. 3.5
OEB core media type (>HBearemedlalype) must be supported by the reader system. 3.6
O document Fdomnt
Combined with the MI. document specified in this guide technical document. 3.
OEH package OFRpackARe
description of the file (publication). It identifies all the other documents in the publication and provides a description of these documents.
OE publications are a collection of documents and other files. The other files are usually presented in different formats - including structured documents and formats. They together form the components of the publication. 3.9
Readerreader
A person who reads the publication.
Reading devicerradingdevice
The platform that presents the publication! It includes hardware and software. 3.11
Readingsystem
A software system that can be used by readers to receive the publication. The biggest difference between different reading systems may be reflected in their different architectures. The reader system may be implemented on a single device or distributed across multiple devices. It should be noted that if a reader device is part of a larger reader system, it is not required that the device be able to connect to the original material. The entire reader system must be able to do this. The reader system may also include other additional functions outside the scope of this guiding technical document, such as compression, encryption, and uploading functions. 4 Overview
4.1 About this guiding technical document
This is the result of joint discussions between the developers of the reader system and relevant experts.
4.2 Relationship with other local specifications | |tt||The technical document will be a combination of H and related specifications, with examples and notes of various subjects, and clear and transparent information. Village specification: a) XML1.ts spectrum (bttp:w.3.oTR.Rc-xu>:bXM domain specification llpwnruT:RC-tlmTMT. Philosophy language ttp:og/TRRE-ht, space inch factory XHlMLl.@Fan (htiy:/w3.org.1k/xt.tml1/); dS1 style sheet (http.//woTR：1/K-CSS), can be verified at the time of SShet/!wwirKAoNrKAca=
G/18906-2 C02
W3.KF: (S> a small number of layers:
Tm:lin (orn number (up: pu-l, oda/) and sMARc and related code table http://wwwle.guv/aure/rel1ora/reuna2rt.h:nly: collection
g) special $MMF￥ body type (ht=p:ief.org/=f=/rfe173N,txt)4.2. The relationship between XMI.
(E1 Based on the original XMI, it has the characteristics of universality and convenience. And use it for this micro document to survive for a long time. Therefore, XML provides the need for specific rules for related text abuse grammar, which can reduce the text consumption Implementation or this can reduce the incompatibility of cross-system transactions. In addition, XMT. It has extensibility, because it does not limit the dragon to a specific set of types, it also supports internationalization, and the installation of the document can be more technical to describe the internal structure of the document. These tags are used to format the document and calculate the type of the document. The reading system must be XMI.1.) All ()1B documents must be in the format of XMI. There is no effective requirement that they must be valid XML documents, but in order to ensure the validity of all required documents in this technical document, the following provisions are made: valid XML documents;
.Complete the following requirements:
.XHFM1, 1.) After the video is less, it must also meet the relevant requirements of the viewer;. The last one does not require the OEH reader system to fully comply with HTM4.U. One of the main uses is ITTV! 4.0 in the application (in the test application) to support XMT. standard element syntax, but the HIM1.0 generation before XMTML1.0 does not support 1. Empty element system syntax: format good female XMT. syntax requirements can be used: any HIM1.0 browser with the requirements of the external and foreign: for example: all elements must be limited to the beginning and end tags: all elements must be limited to the end tag, all elements must be limited to the end tag, no connection is accepted! Required values ​​must be enclosed in quotation marks!
Attribute values ​​must be in non-optimal form (different from "border" and other similar expressions): The "\\" and "\" symbols used in the document must be used as "t:\ and "; all element names must remain consistent with the current specifications in XHTMI.1. All element names and attribute names in F are in lowercase form]; Some element names must follow the XML element specification (this specification also requires that the end of the tag must be blank, such as \hr/", but in XML), this format is optional in the syntax. Element * refers to the content that can be included (such as hr and 1 in HrV1., XML, the official HTM syntax is still not compatible with XML. , M]. The requirement for the end of the standard to have a space at the end of the standard is generally accepted by many customers (this is the format of the product, because XMI. wants to keep the internal secrets of the standard external, so this document requires the inclusion of ML. This (consistent) check (such as \heartbr/\) in the technical document. This is a convenient grammatical form or development, although doing so will extend the service life of the document. In a strict sense, this is not an effective TITMI. format. This can easily convert valid HTM:, the syntax is not converted to the format of the first XM. syntax: the conversion may create new information structures, but it may not add new information bits). The conversion to the effective ITML format is also easily completed through the interpretation, and it can be easily implemented by the user. , before! There is a free download tool for white animation, please refer to the website: tF://w3o:g/Ieople/Kxet=/t.dy:), it is not very hot to convert HTML into XMT.. Then its complexity is called pre-knowledge
format complete XM1.1. The core document is not necessarily a card format () EB real file, because it is a card situation guide technical document towel document to make a history of strict book restrictions on it, in order to improve the interoperability, this restriction is to define the core document to define the two MD packages and according to this article. The package code is a complete publication of the "report" reader to use it to transform the various or public organizations into a thing: this E document The XML namespaces are defined in the following document: 1.4.2.2 Relationship between XML namespaces and XMI.namespaces || tt || The current version of the XML namespaces document does not have a draft document for XML multi-domains: www.ww3.org/TR/RECxl-names> XML namespaces are defined in XML. The namespaces are separated into element and attribute names to distinguish between them. Using XMI.namespaces, you can associate an attribute with a standard namespace. For example, you can use an XMI.namespace as a default namespace and apply it to elements that lack a namespace. In XMT, namespaces are used to represent the element and attribute names.
Guidelines Technical Documents The following usages are prohibited in E3 documents: If u is used in E3 documents, various procedures such as \dix (prefix) or (FB document elements have domain names. If they are not, they will be regarded as extensions, and the number will be treated as a normal ML name symbol: the reader system will recognize them as valid E3 documents. In order to maintain the upward compatibility, the element data of the H package must be accompanied by xmns: dc=\p//ar) ,r:de/nens/.c/"and xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network. In addition, it is also necessary to package k pieces in T>11>in the search for traces of iliuTuNoYuan, and to have a useful atmosphere before\:\,4.2.3 and HMT. The relationship between
in considering the software engineering, the historical data arch, the publication of the actual content and the market case and other aspects of the re-importance. This guidance document is based on HITML, and this approach allows content providers to explore existing HITML content, tools, and technical expertise. In order to minimize the burden of new system developers (who may use various devices with limited power and display), this guidance document does not include the enterprise HITML attributes in the structure of the document. This guidance document is not a technical document and does not include the same attributes as HTM4. (Specification, in accordance with the current HTML, XHTML, and XML development direction and the principle of integration. If you want to complete the requirements of the elements, please refer to Appendix A, which contains a complete list of the types of elements in HTML, HTML, and XML. All ML constructs that are not used in this specification are not used in this specification. Or they are not used. This is the equivalent form of (SS). Style sheet structure can also be used for HTML1.4. 0) new functions other than those planned.
In order to achieve predictable consistency and maintain the time and strictness of future versions of the guidance technical document, the guidance technical document is a series of recommendations: This EI is an effective M document. This document and the relationship between [4.2.4 and C5S]
This guidance technical document defines on the basis of (Ss1) and (Ss2): and the sample or language clip. The software has long pressure \tcxt/x-ochs
As long as (ET media writing group needs to recognize The proposal for defining the media type described in the guide (.work correction (.read more.com: tTP://wWW.3OTg/TRREC-L\SS1)) did not conform to the actual situation and had to do so. This technical guideline document includes the style of SS in the construction, which has extended the dual-reference display function. In order to reduce the burden on system developers and manufacturers, this technical guideline document does not include SS1 or CSS. This technical guideline document has added a few additional features, and the use rate is one-sided. Under the condition of large number of pages and large number of visitors, this technical guideline document does not include the full display effect required by the standard group display. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color displays other than the B logo. Under this test, this guide allows the use of various (assuming) links in the technical documents and maintains its meaning. The result of doing so is not enough to meet the requirements of the reader system. The display effect is also gradually transformed into a simple flashing system. This technical document is embedded with style elements for convenience. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link elements, b) using an external identifier to describe the elements in the HTML header, or d) using the W3C protocol to describe the style sheet in XML: http://w3.The browser requires that all required elements must be between the start and end tags: All elements must be non-binding, no binding required! Required values ​​must be enclosed in quotation marks!
Attribute values ​​must be in non-optimal form (different from "border" and other similar expressions): The "\\" and "\" symbols used in the document must be used as "t:\ and "; all element names must remain consistent with the current specifications in XHTMI.1. All element names and attribute names in F are in lowercase form]; Some element names must follow the XML element specification (this specification also requires that the end of the tag must be blank, such as \hr/", but in XML), this format is optional in the syntax. Element * refers to the content that can be included (such as hr and 1 in HrV1., XML, the official HTM syntax is still not compatible with XML. , M]. The requirement for the end of the standard to have a space at the end of the standard is generally accepted by many customers (this is the format of the product, because XMI. wants to keep the internal secrets of the standard external, so this document requires the inclusion of ML. This (consistent) check (such as \heartbr/\) in the technical document. This is a convenient grammatical form or development, although doing so will extend the service life of the document. In a strict sense, this is not an effective TITMI. format. This can easily convert valid HTM:, the syntax is not converted to the format of the first XM. syntax: the conversion may create new information structures, but it may not add new information bits). The conversion to the effective ITML format is also easily completed through the interpretation, and it can be easily implemented by the user. , before! There is a free download tool for white animation, please refer to the website: tF://w3o:g/Ieople/Kxet=/t.dy:), it is not very hot to convert HTML into XMT.. Then its complexity is called pre-knowledge
format complete XM1.1. The core document is not necessarily a card format () EB real file, because it is a card situation guide technical document towel document to make a history of strict book restrictions on it, in order to improve the interoperability, this restriction is to define the core document to define the two MD packages and according to this article. The package code is a complete publication of the "report" reader to use it to transform the various or public organizations into a thing: this E document The XML namespaces are defined in the following document: 1.4.2.2 Relationship between XML namespaces and XMI.namespaces || tt || The current version of the XML namespaces document does not have a draft document for XML multi-domains: www.ww3.org/TR/RECxl-names> XML namespaces are defined in XML. The namespaces are separated into element and attribute names to distinguish between them. Using XMI.namespaces, you can associate an attribute with a standard namespace. For example, you can use an XMI.namespace as a default namespace and apply it to elements that lack a namespace. In XMT, namespaces are used to represent the element and attribute names.
Guidelines Technical Documents The following usages are prohibited in E3 documents: If u is used in E3 documents, various procedures such as \dix (prefix) or (FB document elements have domain names. If they are not, they will be regarded as extensions, and the number will be treated as a normal ML name symbol: the reader system will recognize them as valid E3 documents. In order to maintain the upward compatibility, the element data of the H package must be accompanied by xmns: dc=\p//ar) ,r:de/nens/.c/"and xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network. In addition, it is also necessary to package k pieces in T>11>in the search for traces of iliuTuNoYuan, and to have a useful atmosphere before\:\,4.2.3 and HMT. The relationship between
in considering the software engineering, the historical data arch, the publication of the actual content and the market case and other aspects of the re-importance. This guidance document is based on HITML, and this approach allows content providers to explore existing HITML content, tools, and technical expertise. In order to minimize the burden of new system developers (who may use various devices with limited power and display), this guidance document does not include the enterprise HITML attributes in the structure of the document. This guidance document is not a technical document and does not include the same attributes as HTM4. (Specification, in accordance with the current HTML, XHTML, and XML development direction and the principle of integration. If you want to complete the requirements of the elements, please refer to Appendix A, which contains a complete list of the types of elements in HTML, HTML, and XML. All ML constructs that are not used in this specification are not used in this specification. Or they are not used. This is the equivalent form of (SS). Style sheet structure can also be used for HTML1.4. 0) new functions other than those planned.
In order to achieve predictable consistency and maintain the time and strictness of future versions of the guidance technical document, the guidance technical document is a series of recommendations: This EI is an effective M document. This document and the relationship between [4.2.4 and C5S]
This guidance technical document defines on the basis of (Ss1) and (Ss2): and the sample or language clip. The software has long pressure \tcxt/x-ochs
As long as (ET media writing group needs to recognize The proposal for defining the media type described in the guide (.work correction (.read more.com: tTP://wWW.3OTg/TRREC-L\SS1)) did not conform to the actual situation and had to do so. This technical guideline document includes the style of SS in the construction, which has extended the dual-reference display function. In order to reduce the burden on system developers and manufacturers, this technical guideline document does not include SS1 or CSS. This technical guideline document has added a few additional features, and the use rate is one-sided. Under the condition of large number of pages and large number of visitors, this technical guideline document does not include the full display effect required by the standard group display. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color displays other than the B logo. Under this test, this guide allows the use of various (assuming) links in the technical documents and maintains its meaning. The result of doing so is not enough to meet the requirements of the reader system. The display effect is also gradually transformed into a simple flashing system. This technical document is embedded with style elements for convenience. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link elements, b) using an external identifier to describe the elements in the HTML header, or d) using the W3C protocol to describe the style sheet in XML: http://w3.The browser requires that all required elements must be between the start and end tags: All elements must be non-binding, no binding required! Required values ​​must be enclosed in quotation marks!
Attribute values ​​must be in non-optimal form (different from "border" and other similar expressions): The "\\" and "\" symbols used in the document must be used as "t:\ and "; all element names must remain consistent with the current specifications in XHTMI.1. All element names and attribute names in F are in lowercase form]; Some element names must follow the XML element specification (this specification also requires that the end of the tag must be blank, such as \hr/", but in XML), this format is optional in the syntax. Element * refers to the content that can be included (such as hr and 1 in HrV1., XML, the official HTM syntax is still not compatible with XML. , M]. The requirement for the end of the standard to have a space at the end of the standard is generally accepted by many customers (this is the format of the product, because XMI. wants to keep the internal secrets of the standard external, so this document requires the inclusion of ML. This (consistent) check (such as \heartbr/\) in the technical document. This is a convenient grammatical form or development, although doing so will extend the service life of the document. In a strict sense, this is not an effective TITMI. format. This can easily convert valid HTM:, the syntax is not converted to the format of the first XM. syntax: the conversion may create new information structures, but it may not add new information bits). The conversion to the effective ITML format is also easily completed through the interpretation, and it can be easily implemented by the user. , before! There is a free download tool for white animation, please refer to the website: tF://w3o:g/Ieople/Kxet=/t.dy:), it is not very hot to convert HTML into XMT.. Then its complexity is called pre-knowledge
format complete XM1.1. The core document is not necessarily a card format () EB real file, because it is a card situation guide technical document towel document to make a history of strict book restrictions on it, in order to improve the interoperability, this restriction is to define the core document to define the two MD packages and according to this article. The package code is a complete publication of the "report" reader to use it to transform the various or public organizations into a thing: this E document The XML namespaces are defined in the following document: 1.4.2.2 Relationship between XML namespaces and XMI.namespaces || tt || The current version of the XML namespaces document does not have a draft document for XML multi-domains: www.ww3.org/TR/RECxl-names> XML namespaces are defined in XML. The namespaces are separated into element and attribute names to distinguish between them. Using XMI.namespaces, you can associate an attribute with a standard namespace. For example, you can use an XMI.namespace as a default namespace and apply it to elements that lack a namespace. In XMT, namespaces are used to represent the element and attribute names.
Guidelines Technical Documents The following usages are prohibited in E3 documents: If u is used in E3 documents, various procedures such as \dix (prefix) or (FB document elements have domain names. If they are not, they will be regarded as extensions, and the number will be treated as a normal ML name symbol: the reader system will recognize them as valid E3 documents. In order to maintain the upward compatibility, the element data of the H package must be accompanied by xmns: dc=\p//ar) ,r:de/nens/.c/"and xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network. In addition, it is also necessary to package k pieces in T>11>in the search for traces of iliuTuNoYuan, and to have a useful atmosphere before\:\,4.2.3 and HMT. The relationship between
in considering the software engineering, the historical data arch, the publication of the actual content and the market case and other aspects of the re-importance. This guidance document is based on HITML, and this approach allows content providers to explore existing HITML content, tools, and technical expertise. In order to minimize the burden of new system developers (who may use various devices with limited power and display), this guidance document does not include the enterprise HITML attributes in the structure of the document. This guidance document is not a technical document and does not include the same attributes as HTM4. (Specification, in accordance with the current HTML, XHTML, and XML development direction and the principle of integration. If you want to complete the requirements of the elements, please refer to Appendix A, which contains a complete list of the types of elements in HTML, HTML, and XML. All ML constructs that are not used in this specification are not used in this specification. Or they are not used. This is the equivalent form of (SS). Style sheet structure can also be used for HTML1.4. 0) new functions other than those planned.
In order to achieve predictable consistency and maintain the time and strictness of future versions of the guidance technical document, the guidance technical document is a series of recommendations: This EI is an effective M document. This document and the relationship between [4.2.4 and C5S]
This guidance technical document defines on the basis of (Ss1) and (Ss2): and the sample or language clip. The software has long pressure \tcxt/x-ochs
As long as (ET media writing group needs to recognize The proposal for defining the media type described in the guide (.work correction (.read more.com: tTP://wWW.3OTg/TRREC-L\SS1)) did not conform to the actual situation and had to do so. This technical guideline document includes the style of SS in the construction, which has extended the dual-reference display function. In order to reduce the burden on system developers and manufacturers, this technical guideline document does not include SS1 or CSS. This technical guideline document has added a few additional features, and the use rate is one-sided. Under the condition of large number of pages and large number of visitors, this technical guideline document does not include the full display effect required by the standard group display. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color displays other than the B logo. Under this test, this guide allows the use of various (assuming) links in the technical documents and maintains its meaning. The result of doing so is not enough to meet the requirements of the reader system. The display effect is also gradually transformed into a simple flashing system. This technical document is embedded with style elements for convenience. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link elements, b) using an external identifier to describe the elements in the HTML header, or d) using the W3C protocol to describe the style sheet in XML: http://w3.This is a convenient way to do this, although it may extend the life of the document. In a strict sense, this is not a valid ITML format. This can easily be done by checking the valid HTML: syntax and converting it to a complete XML format: the conversion may create new information structures, but it may not add new information. The conversion to a valid ITML format is also easily done through interpretation, and is very easy to implement automatically by the user! There are free tools for dynamic implementation, please refer to the website: tF://w3o:g/Ieople/Kxet=/t.dy:), it is not very hot to convert HTML into XMT. The complexity is called the complete XML format () EB document. The core document is not necessarily a complete document. Because it is a technical document, the document has made strict restrictions on it. In order to improve the interoperability, this restriction is determined by the definition of the "core communication requirements GB/18905-2002" technical document definition of two MD packages and according to this article. This document defines the relationship between TMI and XMI. The current version of the XML Multi-Domain Protocol draft document does not have XML namespaces. The XML namespaces are divided into element names and attribute names to distinguish between the names in the document and the company's defined XML multi-domain protocol. Use XMI. Name domain user declaration, Sichuan will be honored with a certain standard 1I "through the line association. For external names or voice periods, or tea RI. As the default name domain, it is applied to the elements that lack a sense of name. XMT, name domain forward and backward core element point use number upgrade.
Guide document technical documents prohibit the use of the following E than the use of the name city before the DE document: if the E package uses u number disassembly medicine various purchase requests use the name of the previous lead or. (FB document elements I bitterly make the name domain before the link. It is sunk as an extension, and the number and so on play the normal ML now Title symbol: The reader system must recognize the document as a valid multiple-title number. In order to maintain the upward compatibility, the H package element data must have the xmns:dc=\p//ar),r:de/nens/.c/" property and the xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network property. In addition, it is also required that the package T>11> in the iliuTu no element trace, well with the use of the front \:\, 4.2.3 and HMT. Relationship | |tt|| Considering the importance of existing software, historical data, published records and market cases, this technical guide is based on HITML. This approach allows content providers to further explore existing HITML content, processes and technical expertise.
In order to minimize the burden of new system developers (who may use various devices that are necessarily limited in frequency and display), this technical guide does not include the enterprise IITML attributes in the structure of the document. This document is not a technical document that searches for and selects HTML4.0 specifications. It is based on the current development direction and principles of HTML, XML, and XML. If you want to know all the requirements, please refer to Appendix A, which contains a complete list of all the HTML1.2, HTML4.0, and XML file types. All HTML constructs that are not used in this technical document are not used. This is the equivalent of HTML5.0. Style sheets can also be used for HTML1.4. 0) new functions are not planned.
In order to achieve predictable consistency and maintain the time and strictness of future versions of the guidance technical document, the guidance technical document is a series of effective M documents. This document and the relationship between [4.2.4 and C5S]
This guidance technical document defines on the basis of (SS1) and (SS2: and the sample or language. The software has a long pressure of \tcxt/x-ochs
The (ET media writing team needs to recognize that the relevant media types are defined as guides (. Work correction (read more network: tTP://www.3OTg/TRREC-L\SS1) The proposal does not match the actual situation and has to do so. This technical guide includes the style of SS1 in the construction, which extends the dual-reference display effect function. In order to reduce the burden on system developers and manufacturers, this technical guide does not include SS1 or CSS. This technical guide has added some additional features. The use of one-sided cloth, page size and number of visitors, this technical guide requires that the system can provide all the required display effects when the standard display is displayed. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color displays other than the B logo. Under this test, this guide allows the use of various (assuming) links in the technical documents and maintains its meaning. The result of doing so is not enough to meet the requirements of the reader system. The display effect is also gradually transformed into a simple flashing system. This technical document is embedded with style elements for convenience. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link elements, b) using an external identifier to describe the elements in the HTML header, or d) using the W3C protocol to describe the style sheet in XML: http://w3.This is a convenient way to do this, although it may extend the life of the document. In a strict sense, this is not a valid ITML format. This can easily be done by checking the valid HTML: syntax and converting it to a complete XML format: the conversion may create new information structures, but it may not add new information. The conversion to a valid ITML format is also easily done through interpretation, and is very easy to implement automatically by the user! There are free tools for dynamic implementation, please refer to the website: tF://w3o:g/Ieople/Kxet=/t.dy:), it is not very hot to convert HTML into XMT. The complexity is called the complete XML format () EB document. The core document is not necessarily a complete document. Because it is a technical document, the document has made strict restrictions on it. In order to improve the interoperability, this restriction is determined by the definition of the "core communication requirements GB/18905-2002" technical document definition of two MD packages and according to this article. This document defines the relationship between TMI and XMI. The current version of the XML Multi-Domain Protocol draft document does not have XML namespaces. The XML namespaces are divided into element names and attribute names to distinguish between the names in the document and the company's defined XML multi-domain protocol. Use XMI. Name domain user declaration, Sichuan will be honored with a certain standard 1I "through the line association. For external names or voice periods, or tea RI. As the default name domain, it is applied to the elements that lack a sense of name. XMT, name domain forward and backward core element point use number upgrade.
Guide document technical documents prohibit the use of the following E than the use of the name city before the DE document: if the E package uses u number disassembly medicine various purchase requests use the name of the previous lead or. (FB document elements I bitterly make the name domain before the link. It is sunk as an extension, and the number and so on play the normal ML now Title symbol: The reader system must recognize the document as a valid multiple-title number. In order to maintain the upward compatibility, the H package element data must have the xmns:dc=\p//ar),r:de/nens/.c/" property and the xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network property. In addition, it is also required that the package T>11> in the iliuTu no element trace, well with the use of the front \:\, 4.2.3 and HMT. Relationship | |tt|| Considering the importance of existing software, historical data, published records and market cases, this technical guide is based on HITML. This approach allows content providers to further explore existing HITML content, processes and technical expertise.
In order to minimize the burden of new system developers (who may use various devices that are necessarily limited in frequency and display), this technical guide does not include the enterprise IITML attributes in the structure of the document. This document is not a technical document that searches for and selects HTML4.0 specifications. It is based on the current development direction and principles of HTML, XML, and XML. If you want to know all the requirements, please refer to Appendix A, which contains a complete list of all the HTML1.2, HTML4.0, and XML file types. All HTML constructs that are not used in this technical document are not used. This is the equivalent of HTML5.0. Style sheets can also be used for HTML1.4. 0) new functions are not planned.
In order to achieve predictable consistency and maintain the time and strictness of future versions of the guidance technical document, the guidance technical document is a series of effective M documents. This document and the relationship between [4.2.4 and C5S]
This guidance technical document defines on the basis of (SS1) and (SS2: and the sample or language. The software has a long pressure of \tcxt/x-ochs
The (ET media writing team needs to recognize that the relevant media types are defined as guides (. Work correction (read more network: tTP://www.3OTg/TRREC-L\SS1) The proposal does not match the actual situation and has to do so. This technical guide includes the style of SS1 in the construction, which extends the dual-reference display effect function. In order to reduce the burden on system developers and manufacturers, this technical guide does not include SS1 or CSS. This technical guide has added some additional features. The use of one-sided cloth, page size and number of visitors, this technical guide requires that the system can provide all the required display effects when the standard display is displayed. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color displays other than the B logo. Under this test, this guide allows the use of various (assuming) links in the technical documents and maintains its meaning. The result of doing so is not enough to meet the requirements of the reader system. The display effect is also gradually transformed into a simple flashing system. This technical document is embedded with style elements for convenience. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link, e) using an external identifier in the HTML element to describe the aesthetic, or d) using the W3C protocol to describe the aesthetic of the XML document style sheet <website:http://w3.org/doc/html/stylesheets/html/.It is required that the metadata of the H package contain xmlns:dc=\p//ar),r:de/nens/.c/" and xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network properties. In addition, it is also necessary to consider the relationship between 4.2.3 and HITML. In order to consider the importance of the existing software, historical data, published records and market cases, this technical guide is based on HITML. This method allows content providers to further explore existing HITML content, processes and specialized technologies. In order to reduce the burden of new system developers (who may be limited in frequency and display of various scientific equipment), this technical guide does not include the enterprise IITML element attributes in the structure of the document. This document is not a technical document that searches for and selects HTML4.0 specifications. It is based on the current development direction and principles of HTML, XML, and XML. If you want to know all the requirements, please refer to Appendix A, which contains a complete list of all the HTML1.2, HTML4.0, and XML file types. All HTML constructs that are not used in this technical document are not used. This is the equivalent of HTML5.0. Style sheets can also be used for HTML1.4. 0) new functions are not planned.
In order to achieve predictable consistency and maintain the consistency of future versions of the technical guidance document, the technical guidance document is a series of recommendations: This EI is an effective M document. This document and the relationship between [4.2.4 and C5S]
This technical guidance document defines on the basis of (Ss1) and (Ss2: And the sample or language piece. The north has entertainment software long pressure \tcxt/x-ochs
The (ET media writing team needs to know the relevant media type for the definition of the guide (. Work correction (talk more reading network: tTP:// wWW.3OTg/TRREC-L\SS1) is not in line with the proposed changes. However, it has to be done in consideration of the actual situation. This technical guideline document includes the style of SS in the construction, which has extended the display function of the dual reference. In order to reduce the burden on system developers and manufacturers, this technical guideline document does not include SS1 or CSS. This technical guideline document has added a few additional features, and the use rate is partial. Under the circumstances of the number of pages and the number of customers, this technical guideline document provides the system with standard requirements. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color machines other than the B logo. Under this test, this guide allows the use of various (assumptions) in this technical document and maintains its meaning. However, the result of doing so is not enough, and the reader system that meets the requirements of the manual will gradually transform into a simple flash display system. This document is regrettable with The style sheet is a convenient way to embed style elements in technical documents. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link elements, b) using an external identifier to describe the aesthetic of the elements in the HTML header, or d) using the W3C protocol to describe the aesthetic of the XML document.It is required that the metadata of the H package contain xmlns:dc=\p//ar),r:de/nens/.c/" and xmlaecage"E:1tp.//openebcok,org/nancspRaes/ucb-paskagt/.o/network properties. In addition, it is also necessary to consider the relationship between 4.2.3 and HITML. In order to consider the importance of the existing software, historical data, published records and market cases, this technical guide is based on HITML. This method allows content providers to further explore existing HITML content, processes and specialized technologies. In order to reduce the burden of new system developers (who may be limited in frequency and display of various scientific equipment), this technical guide does not include the enterprise IITML element attributes in the structure of the document. This document is not a technical document that searches for and selects HTML4.0 specifications. It is based on the current development direction and principles of HTML, XML, and XML. If you want to know all the requirements, please refer to Appendix A, which contains a complete list of all the HTML1.2, HTML4.0, and XML file types. All HTML constructs that are not used in this technical document are not used. This is the equivalent of HTML5.0. Style sheets can also be used for HTML1.4. 0) new functions are not planned.
In order to achieve predictable consistency and maintain the consistency of future versions of the technical guidance document, the technical guidance document is a series of recommendations: This EI is an effective M document. This document and the relationship between [4.2.4 and C5S]
This technical guidance document defines on the basis of (Ss1) and (Ss2: And the sample or language piece. The north has entertainment software long pressure \tcxt/x-ochs
The (ET media writing team needs to know the relevant media type for the definition of the guide (. Work correction (talk more reading network: tTP:// wWW.3OTg/TRREC-L\SS1) is not in line with the proposed changes. However, it has to be done in consideration of the actual situation. This technical guideline document includes the style of SS in the construction, which has extended the display function of the dual reference. In order to reduce the burden on system developers and manufacturers, this technical guideline document does not include SS1 or CSS. This technical guideline document has added a few additional features, and the use rate is partial. Under the circumstances of the number of pages and the number of customers, this technical guideline document provides the system with standard requirements. For example, a certain reader system uses a monochrome display. Therefore, this guide document does not recognize that all reader systems assume monochrome displays, nor does it require full-color machines other than the B logo. Under this test, this guide allows the use of various (assumptions) in this technical document and maintains its meaning. However, the result of doing so is not enough, and the reader system that meets the requirements of the manual will gradually transform into a simple flash display system. This document is regrettable with The style sheet is a convenient way to embed style elements in technical documents. In the process of processing various style sheets, the style sheet is associated with the document in the following ways: a) using the HTML header to link elements, b) using an external identifier to describe the aesthetic of the elements in the HTML header, or d) using the W3C protocol to describe the aesthetic of the XML document.The V1VF media type\txt/x-ebl-us\ must be convex, including all "persistent sets">[The document itself specifies all style parameters. The OFSS set must be required. 4.3.1.3 Extended OED document
The necessary and sufficient terms for this document to be an extended document are: 9) Must meet the ()EB common requirements:
irKoNrKAca=
GB/Z18905-2002
The document does not define the elements, local components or attributes in this guidance technical document, and the document has no other definitions for the two guidance technical documents! 1.1.4 Validity
Basic U R document, may be valid, but can also be invalid <its validity is defined in XMT1.1.4 Validity
All documents must be well-formed XM1.0 documents:
2,3.1.5 Conformance of publications
A document must be a complete set of "EH publications" with the following content:
... The effective XMI document!
: (including the documents related to each document in the publication, including the documents corresponding to each document in the publication, and the documents corresponding to each document in the publication. The document type is defined in the M[ME coal type definition.) The fast dmetadate element system must include a dulcicmifiur and ke:Tileln:fs package index u:iuu-idenliinr property pair · small ·ila.iier The correct XMLJR below t) is the onrb.tr element system book has full color full standard specified content and all scalability must be multiplied by \o. "And buy:) as the guide type any protection must be in the head 4.3.2 Read the skeleton function of a number of busy || tt || This guidance technical document is only applicable to the meaning of "read" The confidentiality and compatibility of the system. The reader system must follow the following rules to maintain its client-side security: a) When the reader system displays a certain basic (North) document, it must do the following: 1) According to the XML specification, it must also process the M format and complete the processing of the service specifications; it should be recognized that all tags described in this technical document are used for evaluation and evaluation: when processing, it is necessary to use the technical documents described in the technical documents TTTMTA.0CSs2DubliCore and other specifications to ensure consistency! To the outside, the test disk priority test point of this technical document)) When the reading system displays the extended EH document, it must do the following: 1) meet the requirements!
) It should be recognized that: if the element is sufficient in the original technical document, the state should decide which method to use as described in Section 4.2.4;
3) It is necessary to follow the external and internal methods and there is no rate, such as: 1) and 2: the user has regulations such as if to deal with certain elements: then the "segment display" method should be used to deal with it; 4) The standard lacks the estimated information and does not reduce the support of various media types. 5.3: 1..5.2, (.?.3, 6.3) 2. When the information is defined in 6.6, etc., the reader system must do the following when it is guided: 1) It can handle the full range of actual machine values ​​described in Chapter 5 of this guiding technical document, and when the number is provided by (EBm, the reader system should or should: GB/Z8906—2002
1) It cannot display other content other than the file type \exx-mrrm, c! Advantages: H sales or Mlpwwwl.oT: xmi-yleeet The style is selected in the description area. The system should continue to plan: 1) Be able to handle the text:xscbl-egs style sheet of the document: 2 If the system only ~ column M1VF media type is not the assumed 1x1/x--, it may be necessary to use it instead. Although it is not required for the reader system to support other style sheets, it must be able to provide some kind of system. The machine is used to ensure that all other style sheets that are not trxt/-eb.c are ignored.
: #The original reading system and the meaning are called this beyond the actual length to maintain the OFB document H. Do not use this method. 4.4 Extensibility
For example, the ITM editor in this old account provides the ability to add various information and structures, such as the semantics of content association. The H document construction mechanism is to use (B document expansion. It can be driven to add various EB elements, as long as these elements are provided in the style table with the meaning of the search, as shown below: c.elepter
.milsstone t.n25\/::
eh.juurur.Chapter onc:/eh.puttaa:++Naw ie the timer?
c./che.yter
The premise is that the style sheet to be searched contains the following fragment: caapcr tagt-brcak heisrc:aiways:ll
r:hap:erhasd:
font-wtight:bold:
font family+aara seril :
texi-lign:r:
I ply:bhnek
margin-top:4ex
4.5 Accessibility
The technical guidelines were incorporated into the document to ensure that the generated content is accessible and usable by all users. The original document was developed by the wlwilwlonsnmrtwa team:w3CWebCententAucesnhilnyGuideliaes1.o(lip/warw,worg/TR！/AEWECNEN,OO to ensure that a wide range of users can access the various diagrams published in this format. In addition, the researchers used W3TMLUGdlinuVkileAersF1p://wa.mrz/Tk/N:hm-:anali+Hi search and WaC WehArcessilsi.icy i:nivr provides the UscrAgatGuidelinshttpww3o-yTl/WD-WA]-LSERAGENl to ensure that the system can meet various evaluation requirements. bZxz.net
4.6 Future Development Direction
The design of the guiding technical documents takes into account the needs of the development of the current technical documents: the technical documents to be developed are expected to be developed in the future, and the development of the guiding technical documents is expected to be continued in the future, and the accessibility, internationalization and demand, as well as the strict distinction between content and expression, while maintaining the connection with the relevant standards. In addition, it is also a priority to maintain the existing version of the guiding technical documents. 5OEB package
conforms to the old technical document publication must contain and propose another file (also known as the file). This file is used to refer to OF graphics and other objects of the publication. It is also used to specify how to use it. The package files can be easily identified in the file group that makes up the publication. Even if the package files are set, they all use the same extension name \.af\, and the MIME media type of the package files is \tx/xm\. This technical document does not clearly define the file format that can be used together to generate a certain effect (for example, using a .11 Documentation): Although there is no requirement to physically include all publications, if included in the publication, the following references should be made:
HK Package Contents The document designation includes: PACKACEILENTITY: The package identifier is used as a unique identifier. MTAAT4 (optical data): the data relating to the publication (labels, documentation, etc.). VAV (document list): all documentation that makes up the publication (including style, format, specifications, etc.) including the relevant technical specifications of this guide. The supported file types are documented in the SPINE card. SPINE cards can be used to simplify the order of reading a document. SPINE cards are a set of optional reading sequences that can be used for various reading schedules and for various reading techniques:
·G Stop Guide: A guide to the structure of the publication, including information about the content of the publication, the preface, and the design. The document must also be in the original XM1 format and must conform to the RDT specifications (the non-standard format of the package is as follows,
? xm. voralou=.o\?
!IOCTYP pacsagG
PURr.1\—//SIN-957Sn19:/:TI (OFT 1 ) PakeS+/FV\http://r.peneaook.nrg/elrdx/ceh-1.(o,ncbpkgl.dd\:-:ackage.:
/packare
The following describes the components of the ()EB package. 5.1 Package Identification
The package element is the element of the package text. The element of the package text ... ifier is used to specify the identifier element as described in 2.1. The LIFB package identifier is used as the primary identifier for the document, and the author of the document may choose to use the primary identifier, which should be unique to that particular document, such as a document from a single package. However, if the document is not unique to that package, then the document should not be used. 5.2 Publication Metadata
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.