X.694指南：W3C XML Schema到ASN.1的映射

X.694

ASN.1

需积分: 9 185 浏览量更新于2024-08-02 收藏 663KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"X.694-Mapping W3C XML Schema Definitions into ASN.1" 是一个ITU-T（国际电信联盟电信标准化部门）推荐的标准，它详细描述了如何将W3C XML Schema定义映射到ASN.1（抽象语法标记一）中。这个标准是由ITU-T与ISO（国际标准化组织）/ IEC（国际电工委员会）共同发布的，主要用于数据网络和开放系统通信中的信息表示。 ASN.1是一种强大的数据表示语言，用于定义复杂的数据结构，常用于电信、网络协议和分布式系统等领域。它的设计目标是提供一种独立于任何特定机器或编程语言的语法，以便不同系统之间能够交换数据。ASN.1定义了一种抽象的数据结构，而X.694则提供了将这些抽象结构转换为XML Schema的规则。 XML Schema是W3C（万维网联盟）制定的一种XML文档的结构化描述语言，它用于定义XML文档的结构、数据类型以及元素和属性的约束。XML Schema的出现，使得XML文档的验证和处理变得更加规范和精确。 X.694标准的重要性在于，它允许在XML和ASN.1之间进行无缝转换，这对于那些已经使用ASN.1作为其数据表示标准但又需要与XML生态系统交互的系统来说至关重要。这种映射机制使得XML Schema定义的数据可以被解析、编码和解码为ASN.1格式，反之亦然。这在多种应用场景中都有用，比如网络协议、数据库交换、软件配置文件等。映射过程通常包括以下几个步骤： 1. **识别XML Schema组件**：首先，需要识别XML Schema文档中的各种组件，如元素、属性、数据类型等。 2. **映射数据类型**：XML Schema的数据类型需要映射到ASN.1的相应类型，例如基本数据类型（字符串、整数、浮点数）和更复杂的类型（枚举、数组、结构体）。 3. **处理XML Schema的约束**：XML Schema中关于元素和属性的约束，如最大长度、最小值等，需要在ASN.1中得到相应的表示。 4. **构建ASN.1模块**：根据映射规则，构建ASN.1模块，这通常包括ASN.1的定义、类型和结构。 5. **编码和解码**：利用映射后的ASN.1模块，可以实现XML数据到ASN.1的编码，以及ASN.1数据到XML的解码。通过X.694标准，开发者和系统设计者可以充分利用XML的灵活性和广泛支持，同时保持ASN.1在数据交换和处理方面的高效性和标准化。这在跨平台和跨系统的通信中起到桥梁作用，确保了数据的一致性和兼容性。

资源详情

资源推荐

ISO/IEC 8825-5:2004 (E)

4 ITU-T Rec. X.694 (01/2004)

standardized, and conforming implementations of the mapping may choose any syntactic form (or a mixture of syntactic

forms) for the assignment of final XER encoding instructions.

NOTE – The choice among these options does not affect the final binary or XML encodings.

6.5 A formal specification of the required mapping is not provided.

6.6 This Recommendation | International Standard is concerned only with the mapping of XSD Schemas that

conform to W3C XML Schema.

NOTE – Such conformance can be either by the provision of one or more W3C XSD schema documents or by other means as

specified in W3C XML Schema.

7 Mapping XSD Schemas

7.1 A mapping is based on a source XSD Schema, which is a set of schema components (see W3C XML Schema

Part 1, 2.2). No particular representation of schema components or sets of schema components is required or assumed

for the mapping, although it is expected that the source XSD Schema will usually be provided as one or more XML

schema documents (see W3C XML Schema Part 1, 3.15.2).

NOTE 1 – Since the mapping is defined in terms of schema components (and not in terms of their XML representation), it is not

affected by details of the XML representation, such as the use of multiple schema documents linked by

xsd:include and

xsd:redefine element information items, the placement of element information items in one or another schema documents, the

order of

xsd:attribute element information items within a xsd:complexType element information item, and so on.

NOTE 2 – Two sets of schema documents that differ in many aspects but represent the same set of schema components generate

the same set of ASN.1 type assignments, with the same final encoding instructions assigned to them and to their components to

any depth.

7.2 The source XSD Schema shall meet all the constraints imposed by the XSD specification. If the source XSD

Schema is represented (in part or all) as a set of XML schema documents, each schema document shall be valid

according to the XSD Schema for Schemas (see W3C XML Schema Part 1, Appendix A).

7.3 At least one ASN.1 module (see 7.4) shall be generated for each different

target namespace (whether a

namespace name or the keyword absent) that is the target namespace of one or more schema components in the source

XSD Schema. Each ASN.1 module shall contain one or more type assignments corresponding to top-level schema

components (see 7.9) that have the same

target namespace. Each ASN.1 module can also contain one or more special

ASN.1 type assignments whose associated ASN.1 type assignments are in the same ASN.1 module (see 7.6).

NOTE –The schema components represented in the multiple schema documents become part of the same XSD Schema through

the use of the

xsd:include, xsd:redefine, and xsd:import element information items.

7.4 The number of ASN.1 modules generated for each target namespace (including the keyword absent) may be

more than one, but each ASN.1 module shall not contain type assignments corresponding to top-level schema

components with different

target namespaces (including the keyword absent).

7.5 When multiple ASN.1 modules are generated for a given

target namespace (including the keyword absent), all

the type assignments present in them shall be generated as if they were being added to a single ASN.1 module for the

purpose of generating distinct type reference names (see 10.3). The type reference names generated from the

names of

the top-level schema components with a given

target namespace shall be the same type reference names regardless of the

number of ASN.1 modules generated for that

target namespace and regardless of the way type assignments are divided

among the various ASN.1 modules.

NOTE – This is designed to provide flexibility without compromising interoperability.

7.6 Each special ASN.1 type assignment (see clauses 29, 30, and 31) shall be inserted in the same ASN.1 module

as its associated ASN.1 type assignment (see 29.4, 31.4, and 30.4, respectively).

7.7 All ASN.1 modules generated by the mapping shall contain (in the XER encoding control section) a

GLOBAL-

DEFAULTS MODIFIED-ENCODINGS encoding instruction and a GLOBAL-DEFAULTS CONTROL-NAMESPACE encoding

instruction specifying the XSI namespace.

7.8 A source XSD Schema shall be processed as follows:

a) for each top-level

element declaration, an ASN.1 type assignment shall be generated by applying

clause 14 to the

element declaration;

b) for each top-level

attribute declaration, an ASN.1 type assignment shall be generated by applying

clause 15 to the

attribute declaration;

c) for each user-defined top-level

simple type definition, an ASN.1 type assignment shall be generated by

applying clause 13 to the

simple type definition;

d) for each top-level

complex type definition, an ASN.1 type assignment shall be generated by applying

clause 20 to the

complex type definition;

ISO/IEC 8825-5:2004 (E)

ITU-T Rec. X.694 (01/2004) 5

e) for each model group definition whose model group has a compositor of sequence or choice, an ASN.1 type

assignment shall be generated by applying clause 17 to the model group definition.

NOTE 1 – The remaining schema components of the source XSD schema will be processed as a result of mapping these schema

components.

NOTE 2 – The order in which schema components are to be mapped is specified in 10.4. The order of the items of the list above

has no significance for the mapping.

7.9 Column 1 of Table 1 lists schema components. Column 2 gives the reference to the clause in W3C XML

Schema that defines the schema component. Column 3 lists the clause that defines the mapping of those schema

components into ASN.1.

Table 1 – Mapping of XSD schema components

XSD schema component W3C XML Schema reference Mapping defined by

attribute declaration Part 1, 3.2 Clause 15

element declaration Part 1, 3.3 Clause 14

complex type definition Part 1, 3.4 Clause 20

attribute use Part 1, 3.5 Clause 22

attribute group definition Part 1, 3.6 not mapped as such

model group definition Part 1, 3.7 Clause 17

model group Part 1, 3.8 Clause 18

particle Part 1, 3.9 Clause 19

wildcard Part 1, 3.10 Clause 21

identity-constraint definition Part 1, 3.11 ignored by the mapping

notation declaration Part 1, 3.12 ignored by the mapping

annotation Part 1, 3.13 ignored by the mapping

simple type definition Part 1, 3.14 Clauses 11, 13

schema Part 1, 3.15 Clause 9

ordered Part 2, 4.2.2.1 ignored by the mapping

bounded Part 2, 4.2.3.1 ignored by the mapping

cardinality Part 2, 4.2.4.1 ignored by the mapping

numeric Part 2, 4.2.5.1 ignored by the mapping

length Part 2, 4.3.1.1 Clause 12

minLength Part 2, 4.3.2.1 Clause 12

maxLength Part 2, 4.3.3.1 Clause 12

pattern Part 2, 4.3.4.1 Clause 12

enumeration Part 2, 4.3.5.1 Clause 12

whiteSpace Part 2, 4.3.6.1 Clause 12

maxInclusive Part 2, 4.3.7.1 Clause 12

maxExclusive Part 2, 4.3.8.1 Clause 12

minExclusive Part 2, 4.3.9.1 Clause 12

minInclusive Part 2, 4.3.10.1 Clause 12

totalDigits Part 2, 4.3.11.1 Clause 12

fractionDigits Part 2, 4.3.12.1 Clause 12

8 Ignored schema components and properties

8.1 The mapping shall ignore the schema components and properties that are listed in this clause.

8.2 All

annotations (see W3C XML Schema Part 1, 3.13) shall be ignored.

NOTE – All attribute information items in a schema document with names qualified with namespaces other than the XSD

namespace (see W3C XML Schema Part 1, 3.13.1) are a property of

annotations, and are ignored.

8.3 All identity-constraint definitions (see W3C XML Schema Part 1, 3.11) shall be ignored.

ISO/IEC 8825-5:2004 (E)

6 ITU-T Rec. X.694 (01/2004)

NOTE – The identity-constraint definition provides mechanisms for specifying referential constraints that can be required in a

valid instance. ASN.1 currently has no concept of such constraints, and such constraints cannot be mapped into a formal ASN.1

specification, but they may be included as normative comments that are binding on an application implementation.

8.4 All notation declarations (see W3C XML Schema Part 1, 3.12) shall be ignored.

8.5 All schema components that are the

fundamental facets (ordered, bounded, cardinality, numeric) of simple type

definition

s (see W3C XML Schema Part 2, 4.2) shall be ignored.

8.6 The properties

identity-constraint definitions, substitution group exclusions and disallowed substitutions of element

declaration

s shall be ignored.

8.7 The properties

final, abstract, and prohibited substitutions of complex type definitions shall be ignored.

8.8 The property

process contents of wildcards shall be ignored.

NOTE – There is no support in ASN.1 for any action other than skip.

8.9 The properties fundamental facets and final of simple type definitions shall be ignored.

8.10 All

value constraints that are present on any element declarations or attribute declarations whose type definition is

either xsd:QName or a simple type definition derived from xsd:QName or xsd:NOTATION shall be ignored.

8.11 All

attribute group definitions shall be ignored.

NOTE – The attribute uses in an attribute group definition become part of the attribute uses of the complex type definitions whose XML

representation contains a reference to the

attribute group definition.

9 The ASN.1 module and namespaces

NOTE – A full description of the relationship between the namespace concept of W3C XML Namespaces and naming in ASN.1

is provided in ITU-T Rec. X.693 | ISO/IEC 8825-4, clause 16. Type reference names and identifiers defined in an ASN.1 module

are assigned a namespace by means of a

NAMESPACE encoding instruction, and otherwise do not have a namespace. The mapping

generates

NAMESPACE encoding instructions as appropriate.

9.1 The mapping generates one or more ASN.1 modules corresponding to all schema components in the Schema

that have the same target namespace.

9.2 The ASN.1 "ModuleIdentifier" (see ITU-T Rec. X.680 | ISO/IEC 8824-1, clause 12) to be generated by the

mapping is not standardized. Where

IMPORTS statements are used, the ASN.1 module names and module identifiers in

the

IMPORTS statements shall be those generated for the ASN.1 modules generated by the mapping.

NOTE – The choice of "ModuleIdentifier" does not affect the encodings in any of the standard encoding rules.

9.3 The ASN.1 modules shall have a "TagDefault" of AUTOMATIC TAGS.

9.4 In each ASN.1 module, there shall be an ASN.1

IMPORTS statement importing the ASN.1 type reference

names in the module named

XSD specified in Annex A that are referenced in the ASN.1 module.

9.5 The

IMPORTS statement shall also import the ASN.1 type reference names of type assignments that have been

placed (as a result of the mapping) in other ASN.1 modules but are referenced in this ASN.1 module.

9.6 There shall be no

EXPORTS statement.

NOTE – This means that all ASN.1 type reference names in the ASN.1 module can be imported into other modules.

10 Name conversion

10.1 General

10.1.1 This Recommendation | International Standard specifies the generation of:

a) ASN.1 type reference names corresponding to the

names of model group definitions, top-level element

declarations, top-level attribute declarations, top-level complex type definitions, and user-defined top-level

simple type definitions;

b) ASN.1 identifiers corresponding to the

names of top-level element declarations, top-level attribute

declarations, local element declarations, and local attribute declarations;

c) ASN.1 identifiers for the mapping of certain

simple type definitions with an enumeration facet (see 12.4.1

and 12.4.2);

剩余69页未读，继续阅读

好汉钱

粉丝: 0
资源: 9

X.694指南：W3C XML Schema到ASN.1的映射

SANGFOR_NGAF_6.8_DNS-Mapping配置指导.pdf

hib-mapping-3.0.dtd

java.lang.IllegalStateException: Service id not legal hostname (${idms.service-mapping.cms-stsc})这是什么原因导致的

<mime-mapping> <extension>apk</extension> <mime-type>application/vnd.android.package-archive</mime-type> </mime-mapping>

services.nginx.networks.mall-network must be a mapping

AUTOSAR里的SENDER-REC-RECORD-TYPE-MAPPING or SENDER-REC-ARRAY-TYPE-MAPPING

Web.xml ，Springmvc-config.xml ，Spring-mybatis.xml ，Applicationcontext.xml 四个配置文件主要代码功能描述及代码

web.xml ejb-jar.xml 示例

WebServlet对应web.xml文档参数

<servlet-mapping> <servlet-name>default</servlet-name> <url-pattern>*.css</url-pattern> </servlet-mapping>的其他表示方法

ERROR org.springframework.boot.SpringApplication - Application run failed org.yaml.snakeyaml.scanner.ScannerException:

mybatis-plus. mapper-locations

web.xml配置详解

web.xml配置文件内容

最新资源