HOME Cart(0) Quotation About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

CYT102.2-2020 English PDF

US$559.00 · In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email.
CYT102.2-2020: (Press and publishing digital content object storage, expansion and exchange specification - Part 2: Object encapsulation, storage and exchange)
Status: Valid

CYT102.2: Evolution and historical versions

Standard ID	Contents [version]	USD	STEP2	[PDF] delivered in	Standard Title (Description)	Status	PDF
CY/T 102.2-2020	English	559	Add to Cart	4 days [Need to translate]	(Press and publishing digital content object storage, expansion and exchange specification - Part 2: Object encapsulation, storage and exchange)	Valid	CY/T 102.2-2020
CY/T 102.2-2014	English	RFQ	ASK	3 days [Need to translate]	(Digital content storage object reuse and exchange specification Part 2: The object encapsulation, storage and exchange)	Obsolete	CY/T 102.2-2014

PDF similar to CYT102.2-2020

Standard similar to CYT102.2-2020

DL/T 679 GB/T 7706 CY/T 102.3 CY/T 102.4 CY/T 102.1

Basic data

Standard ID	CY/T 102.2-2020 (CY/T102.2-2020)
Description (Translated English)	(Press and publishing digital content object storage, expansion and exchange specification - Part 2: Object encapsulation, storage and exchange)
Sector / Industry	Press & Publication Industry Standard (Recommended)
Classification of Chinese Standard	A19
Classification of International Standard	01.140.40
Word Count Estimation	24,230
Date of Issue	2020-11-16
Date of Implementation	2021-02-01
Older Standard (superseded by this standard)	CY/T 102.2-2014
Regulation (derived from)	Guoxin Departure Letter (2020) No. 249
Issuing agency(ies)	State Press and Publication Administration

CYT102.2-2020: (Press and publishing digital content object storage, expansion and exchange specification - Part 2: Object encapsulation, storage and exchange)

---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
People's Republic of China Press and Publishing Industry Standards Replace CY/T 102.2-2014 Object storage and reuse of news and publication digital content with exchange specification Part 2.Object encapsulation, storage and exchange Released by the State Administration of Press and Publication

foreword

This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for Standardization Work Part 1.Structure and Drafting Rules for Standardization Documents" drafting. This document is part 2 of CY/T 102 "Standard for Object Storage, Reuse and Exchange of Press and Publishing Digital Content". CY/T 102 has The following sections were released. --Part 1.Object Model; --Part 2.Object encapsulation, storage and exchange; --Part 3.Object consistency check method. This document replaces CY/T 102.2-2014 "Digital Content Object Storage, Reuse and Exchange Specification Part 2.Object Encapsulation, Storage Compared with CY/T 102.2-2014, except for structural adjustment and editorial changes, the main technical changes are as follows. a) The scope of application of this document has been modified, from being applicable to a single publication type of books to being applicable to multiple types of publications; b) Modified the encapsulation method of digital content objects. In CY/T 102.2-2014, the OAI-ORE resource map file is adopted to comply with The digital content object of the PUBO ontology model is encapsulated. This revision adopts "PUBO RDF Instance Document (RDF/XML Document)" encapsulates the publication digital content object conforming to the revised PUBO ontology model; c) Modified the information package structure, its content includes. 1) Modify the resource map files and related folders at all levels under the CONTAINER folder in CY/T 102.2-2014 to Represented by "PUBO RDF Instance Document"; 2) Modified the content of the manifest file pubomanifest.xml, except for the clear In addition to the list (dataFileList), a new object list (objectList) is added to indicate that each resource instance is used as When it is a subject, it has related objects and semantic relations. Please note that some contents of this document may refer to patents. The issuing agency of this document assumes no responsibility for identifying patents. This document is proposed and managed by the National Press and Publication Information Standardization Technical Committee (SAC/TC 553). This document was drafted by. Peking University, Central Propaganda Department Agency Service Center (Central Propaganda Department Information Center), Beijing Tuobiao Excellent Information Technology Research Institute Academy, China Science and Technology Publishing and Media Co., Ltd. The main drafters of this document. Wang Wenqing, Chen Pengfei, Liu Chengyong, Liu Yong, Zhang Mo, Nan Zhihong, Lu Xinmin, Guan Tao, Zhang Zhi, Jiang Lei, Guo Yujin. The release status of previous versions of this document and the documents it replaces are as follows. --First published as CY/T 102.2-2014 in January.2014; -- This is the first revision.

Introduction

With the development of Internet technology and the gradual maturity of digital processing and publishing related technologies, traditional news and publishing organizations have successively applied information technology for digital publishing. In the process of digital processing and publishing, published content resources such as books and periodicals not only include printable or electronic Various media objects for publication and service (such as PDF files of entire books or chapters, and PDF files of a periodical issue and a paper, etc.), typesetting or The media objects generated during the processing (such as typesetting design source files, etc.), also include cover, table of contents, metadata, various content bodies, various Subsidiary text (such as references, abstracts, glossary, etc.) digital content entity components. For these published content resources, a new A unified digital content object model in the field of news and publishing, to systematically represent and record the content structure, characteristics, expression forms, and carrier methods of resources. formats and the relationship between resources, and can encapsulate, store, reuse and exchange related data at different granularities. In recent years, in the field of knowledge representation and modeling of published content resources, driven by application requirements, relevant industry and enterprise standards at home and abroad Came into being. In November.2017, the drafting of a series of national standards "Specifications for Digital Content Object Storage, Reuse and Exchange" was officially launched; In March 2020, this series of national standards was officially released, laying a model foundation for the establishment of publishing content resource ontology. Three recommendations including GB/T 38371.1-2020 "Digital Content Object Storage, Reuse and Exchange Specification Part 1.Object Model" Based on national standards, combined with the processing and application requirements of publishing content resources in the press and publishing industry, the formulation of this standard is on the agenda. exist During the drafting process of this standard, the drafting group conducted research on a number of current national standards, industry standards and engineering standards, and referred to a large number of Data standards and models at home and abroad provide a set of data from multiple aspects such as object model, object encapsulation, storage and exchange, and object consistency check Unified industry standards to achieve standardized representation of published content resources in the field of news and publication, eliminate data reuse and exchange barriers, and reduce Resource management and utilization costs promote the integration and in-depth utilization of published content resources. Specification for storage, reuse and exchange of digital content objects for press and publication Part 2.Object encapsulation, storage and exchange

1 Scope

This document specifies the encapsulation, storage and exchange methods of published content resource objects, and provides the object exchange service interface. This document is applicable to the unified digital management and sharing of digital content resources in the press and publishing industry.

2 Normative references

The contents of the following documents constitute the essential provisions of this document through normative references in the text. of which, dated references, Only the version corresponding to the date applies to this document; for undated reference documents, the latest version (including all amendments) applies to this document document. GB/T 7408-2005 Data elements and exchange formats Information exchange date and time representation (ISO 8601.2000, IDT) GB/T 38371.2-2020 Digital Content Object Storage, Reuse and Exchange Specification Part 2.Object Encapsulation, Storage and Exchange CY/T 102.1-2020 Press and Publication Digital Content Object Storage, Reuse and Exchange Specification Part 1.Object Model CY/T 102.3-2020 Press and Publication Digital Content Object Storage, Reuse and Exchange Specification Part 3.Object Consistency Check Method

3 Terms and Definitions

The following terms and definitions defined in GB/T.20000.1 apply to this document.

5 Digital Content Object Encapsulation

5.1 Object encapsulation method 5.1.1 Container Level Packaging Container-level encapsulation is used to encapsulate publication digital content objects and all related object information. 5.1.2 Object-level encapsulation Object-level encapsulation is used to encapsulate the publication digital content object and the single media object information it contains. 5.2 Exchange Packet File Structure 5.2.1 Exchange packet types According to the resource granularity encapsulated by the exchange information packet, it can be divided into container-level exchange information packet and object-level exchange information packet. 5.2.2 Container-level exchange packet structure The container-level exchange packet encapsulates all the information contained in a complete container-level package, and its structure is as follows. 5.3 Verification method See 5.2 of CY/T 102.3-2020 for the verification method of publication digital content object encapsulation.

6 Digital Content Object Storage

6.1 Packet Storage The storage of information packages includes the storage of instance files and data files of publication digital content objects (and related resource objects). accomplish The logical storage structure of these two types of files is the publication digital content object archive information package structure. 6.2 Instance file storage 6.2.1 File system storage The complete PUBO RDF instance file can be stored separately in the file system. If the file involves specific data files related to media objects When storing the location, the storage location may be a relative path to the storage location of the current PUBO RDF instance file, or other paths. 6.2.2 Relational database storage A relational database organizes and stores instance data in a two-dimensional table structure. When storing PUBO RDF instance files in a relational database, each instance is stored in a database table as an independent text unit. The table structure is shown in Table 1. 6.2.3 Graph database storage The PUBO object model has graph characteristics. When the instance file data of publication digital content objects and related resource objects is large, Traditional management methods using structured data models are difficult to meet the requirements of low data redundancy and high query performance. Manage RDF instances graphically The data can not only avoid the conversion between RDF logical data model and physical model, but also use mature graph algorithm to optimize RDF data query. Graph databases are based on directed graphs, whose theoretical basis is graph theory. Subject (and object) instance objects in PUBO RDF instance files are regarded as sections Point, the relationship (that is, attributes) between the subject and the object is regarded as an edge, and the RDF instance of the publication digital content object and its related resource object can be regarded as Data is stored in a graph database. Common graph database storage systems include. Neo4j, OrientDB, JanusGraph, Amazon Neptune, InfiniteGraph, 6.3 Data file storage Data files related to PUBO RDF instance files are stored in the dataFile file directory, classified according to different media types, and stored The structure is shown in Table 3. 6.4 Verification method See 7.1 and 7.2 of CY/T 102.3-2020 for the verification method of the storage of publication digital content objects.

7 Digital Content Object Exchange

7.1 Exchange method In order to support the exchange and multiplexing of publication digital content objects, digital content object application systems can communicate via FTP/SFTP, interfaces, etc. exchange of digital content objects. For the FTP/SFTP method, the "exchange information package" file can be directly transmitted between application systems. For the interface exchange method, the resource storage system can provide the following 8 aspects of the interface for the third party (or external system) from the current Obtain publication digital content object information (including metadata, data files, etc.) in the resource storage system. The corresponding exchange interfaces are shown below. a) Resource identifier acquisition interface (listIdentifiers). Obtain a list of resource identifiers that meet the query conditions; b) Specify the resource IRI acquisition interface (listIris). to obtain all relevant resources contained in the resource container level packaging that meet the query conditions. source IRI list; c) Metadata acquisition interface (getMetadata). Get the metadata of the resource of the specified IRI. Supports multiple metadata formats (such as MARC, DC, etc.); d) Data file URL acquisition interface (listContentURL). Get the URL list of data files associated with the specified resource; e) Data stream acquisition interface (getDataStream). to obtain the byte stream of the digital content corresponding to the data file; f) Exchange information packet acquisition interface (getEIP). obtain the exchange information packet of the specified resource IRI; g) Exchange information packet upload interface (uploadEIP). upload the exchange information packet to the resource storage system; h) Resource retrieval interface (resRetrieve). retrieve resource information in the resource storage system. 7.2 Resource identifier acquisition interface 7.2.1 Resource identifier acquisition interface definition The resource identifier acquisition interface (listIdentifiers) is defined in Table 4. 7.2.2 Resource identifier acquisition interface call 7.2.2.1 Correct Request Response An example of a correct request response for the resource identifier acquisition interface is as follows. Request. Return the ISBN list of books whose resource update time is between "2017-12-01" and "2017-12-31" 7.2.2.2 Error Request Response An example of a resource identifier get interface error request response is as follows. 7.3 Specify resource IRI acquisition interface 7.3.1 Specify resource IRI to get interface definition See Table 5 for the definition of the specified resource IRI acquisition interface (listIris). 7.3.2 Specify the resource IRI to get the interface call An example of specifying a resource IRI to obtain an interface request response is as follows. 7.4 Metadata acquisition interface 7.4.1 Metadata acquisition interface definition See Table 6 for the definition of the metadata acquisition interface (getMetadata). 7.4.2 Metadata acquisition interface call An example of the metadata acquisition interface request response is as follows. 7.5 Data file URL acquisition interface 7.5.1 Data file URL acquisition interface definition See Table 7 for the definition of the data file URL acquisition interface (listContentURL). 7.5.2 Data file URL acquisition interface call An example of the response to the interface request for the data file URL is as follows. 7.6 Data stream acquisition interface 7.6.1 Data stream acquisition interface definition See Table 8 for the definition of the data stream acquisition interface (getDataStream). 7.6.2 Data stream acquisition interface call An example of a request response to a data flow acquisition interface is as follows. 7.7 Exchange information packet acquisition interface 7.7.1 Interface definition for exchanging information packets See Table 9 for the definition of exchange information packet acquisition interface (getEIP). 7.8 Exchange information packet upload interface 7.8.1 Definition of exchange information packet upload interface See Table 10 for the definition of the exchanged information packet upload interface (uploadEIP). 7.8.2 Calling the exchange information package upload interface An example of an exchange packet upload interface request response is as follows. 7.9 Resource retrieval interface 7.9.1 Resource retrieval interface definition The resource retrieval interface follows the SRU/SRW protocol to obtain metadata information from the resource storage system. resource retrieval interface See Table 11 for the definition of (resRetrieve).

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of CYT102.2-2020_English be delivered?

Answer: Upon your order, we will start to translate CYT102.2-2020_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of CYT102.2-2020_English with my colleagues?

Answer: Yes. The purchased PDF of CYT102.2-2020_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.

Question 5: Should I purchase the latest version CYT102.2-2020?

Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version CYT102.2-2020 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.