xml - 如何轻松提取精心指定的 XML 数据？

Question

我需要从一些 XML 数据文件中提取数据，以及描述其结构的 XSD。它使用来自几个命名空间的大量复杂类型，这些命名空间本身使用来自更多命名空间的更复杂类型，依此类推。即使在扁平化之后，仍然使用 120 个 XSD。

这是 XSD:

Copyright (C) UN/CEFACT (2008). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to UN/CEFACT, except as needed for the purpose of developing UN/CEFACT specifications, in which case the procedures for copyrights defined in the UN/CEFACT Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by UN/CEFACT or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and UN/CEFACT DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-->
<!--
Schema agency:   Florecom / Floricode
Schema version:   0.10
Schema date:       27 september 2013

Copyright (C) Florecom / Floricode (2013). All Rights Reserved.

Sierteelt Invoice

20110510 HvR Upgrade to new Florecom Library RABIE4p0
20110831 HvR Upgrade to development library RABIE5p0 for Pilot FloraHolland Invoice, added PayerParty, InvoicerParty
20120507 HvR Library 2012 juli.
20120612 HvR Upgrade to new Florecom library RABIE6p0. 
20130927 HvR Upgrade to new Florecom / Floricode liberary RABIE7p0, added ClearingAgent.
-->
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:feccii="urn:fec:florecom:xml:data:draft:CrossIndustryInvoice:10" xmlns:ram="urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:3" xmlns:feram="urn:fec:florecom:xml:data:draft:ReusableAggregateBusinessInformationEntity:7" xmlns:udt="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:4" xmlns:qdt="urn:un:unece:uncefact:data:standard:QualifiedDataType:3" xmlns:ccts="urn:un:unece:uncefact:data:standard:CoreComponentsTechnicalSpecification:2" targetNamespace="urn:fec:florecom:xml:data:draft:CrossIndustryInvoice:10" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10">
    <!-- ======================================================================= -->
    <!-- =====  Imports                                                     ==== -->
    <!-- ======================================================================= -->
    <!-- =====  Import of Reusable Aggregate Business Information Entity Schema Module ===== -->
    <!-- ======================================================================= -->
    <xsd:import namespace="urn:un:unece:uncefact:data:standard:UnqualifiedDataType:4" schemaLocation="http://www.unece.org/uncefact/data/standard/UnqualifiedDataType_4p0.xsd"/>
    <!-- ======================================================================= -->
    <!-- ===== Import of Qualified DataType Schema Module                  ===== -->
    <!-- ======================================================================= -->
    <xsd:import namespace="urn:un:unece:uncefact:data:standard:QualifiedDataType:3" schemaLocation="http://www.unece.org/uncefact/data/standard/QualifiedDataType_3p0.xsd"/>
    <!-- ======================================================================= -->
    <!-- ===== Import of Reusable Aggregate Business Information Entity Schema Module ===== -->
    <!-- ======================================================================= -->
    <xsd:import namespace="urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:3" schemaLocation="http://www.unece.org/uncefact/data/standard/ReusableAggregateBusinessInformationEntity_3p0.xsd"/>
    <!-- ======================================================================= -->
    <!-- ===== Import of FEC Reusable Aggregate Business Information Entity Schema Module ===== -->
    <!-- ======================================================================= -->
    <xsd:import namespace="urn:fec:florecom:xml:data:draft:ReusableAggregateBusinessInformationEntity:7" schemaLocation="http://schemas.florecom.org/xml/data/draft/FEC_ReusableAggregateBusinessInformationEntity_7p0.xsd"/>
    <!-- ======================================================================= -->
    <!-- =====  Element Declarations                                       ===== -->
    <!-- ======================================================================= -->
    <!-- =====  Root Element Declarations                      ===== -->
    <!-- ======================================================================= -->
    <xsd:element name="CrossIndustryInvoice" type="feccii:CrossIndustryInvoiceType">
        <xsd:annotation>
            <xsd:documentation xml:lang="en">
                <ccts:UniqueID>UNMCII1</ccts:UniqueID>
                <ccts:Acronym>CII</ccts:Acronym>
                <ccts:Name>CrossIndustryInvoice</ccts:Name>
                <ccts:Version>1.0</ccts:Version>
                <ccts:Definition>The cross industry invoice is an electronic document exchanged between trading partners with a prime function as a request for payment.  It is an important accounting document and has potential legal implications for sender and receiver. It is also used in the European Union as the key document for VAT declaration and reclamation, for statistics declaration in respect of intra community trade, and to support export and import declaration in respect of trade with countries outside the European community.</ccts:Definition>
            </xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <!-- ================================================================== -->
    <!-- =====  Type Definitions                                      ===== -->
    <!-- ================================================================== -->
    <!-- =====  Type Definitions: CrossIndustryInvoiceType        ===== -->
    <!-- ================================================================== -->
    <xsd:complexType name="CrossIndustryInvoiceType">
        <xsd:sequence>
            <xsd:element name="SupplierParty" type="ram:SupplierPartyType" minOccurs="0"/>
            <xsd:element name="CustomerParty" type="ram:CustomerPartyType" minOccurs="0"/>
            <xsd:element name="BuyerParty" type="ram:BuyerPartyType" minOccurs="0"/>
            <xsd:element name="SellerParty" type="ram:SellerPartyType" minOccurs="0"/>
            <xsd:element name="ConsignorParty" type="ram:ConsignorPartyType" minOccurs="0"/>
            <xsd:element name="ConsigneeParty" type="ram:ConsigneePartyType" minOccurs="0"/>
            <xsd:element name="InvoiceeParty" type="ram:InvoiceePartyType" minOccurs="0"/>
            <xsd:element name="InvoicerParty" type="feram:InvoicerPartyType" minOccurs="0"/>
            <xsd:element name="ManufacturerParty" type="ram:ManufacturerPartyType" minOccurs="0"/>
            <xsd:element name="PayeeParty" type="ram:PayeePartyType" minOccurs="0"/>
            <xsd:element name="PayerParty" type="feram:PayerPartyType" minOccurs="0"/>
            <xsd:element name="InvoiceIssuerParty" type="ram:InvoiceIssuerPartyType" minOccurs="0"/>
            <xsd:element name="TaxRepresentativeParty" type="ram:TaxRepresentativePartyType" minOccurs="0"/>
            <xsd:element name="CustomerAccountantParty" type="ram:CustomerAccountantPartyType" minOccurs="0"/>
            <xsd:element name="SupplierAccountantParty" type="ram:SupplierAccountantPartyType" minOccurs="0"/>
            <xsd:element name="ClearingAgentParty" type="feram:ClearingAgentPartyType" minOccurs="0"/>
            <xsd:element name="InvoiceTradeLineItem" type="feram:InvoiceTradeLineItemType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="BillingPeriod" type="ram:BillingPeriodType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="TradeTransportMeans" type="ram:TradeTransportMeansType" minOccurs="0"/>
            <xsd:element name="TradeTransportMode" type="ram:TradeTransportModeType" minOccurs="0"/>
            <xsd:element name="PayableAccountingAccount" type="ram:PayableAccountingAccountType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="ReceivableAccountingAccount" type="ram:ReceivableAccountingAccountType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="BillingCurrencyExchange" type="ram:BillingCurrencyExchangeType" minOccurs="0"/>
            <xsd:element name="PaymentCurrencyExchange" type="ram:PaymentCurrencyExchangeType" minOccurs="0"/>
            <xsd:element name="AlternativePaymentCurrencyExchange" type="ram:AlternativePaymentCurrencyExchangeType" minOccurs="0"/>
            <xsd:element name="TaxCurrencyExchange" type="ram:TaxCurrencyExchangeType" minOccurs="0"/>
            <xsd:element name="PayeeFinancialAccount" type="ram:PayeeFinancialAccountType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="TradeAllowanceCharge" type="ram:TradeAllowanceChargeType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="BillingAdjustment" type="ram:BillingAdjustmentType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="TradeNote" type="ram:TradeNoteType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="TradeDeliveryTerms" type="ram:TradeDeliveryTermsType" minOccurs="0"/>
            <xsd:element name="BillingDocument" type="feram:BillingDocumentType"/>
            <xsd:element name="BillingPayment" type="ram:BillingPaymentType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="AdvancePayment" type="ram:AdvancePaymentType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="ReferencedDocument" type="ram:ReferencedDocumentType" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="BillingMonetarySummation" type="ram:BillingMonetarySummationType" minOccurs="0"/>
            <xsd:element name="CategorySubtotalTax" type="ram:CategorySubtotalTaxType" minOccurs="0" maxOccurs="unbounded"/>
        </xsd:sequence>
    </xsd:complexType>
</xsd:schema>

不幸的是，我无法共享实际的数据文件，但它是有效的。 (打乱它会破坏验证。)

我需要一种方便的方法来从 Delphi 代码中提取数据。

• 我尝试了使用 XSD 的 XML 数据绑定(bind)向导，但它无法输出编译代码；只是很多很多本质上是简单数据类型的接口(interface)。
• 从 XML 数据文件生成它确实会导致编译返回简单数据类型的代码，但数据为空。
• 发现命名空间的一些问题后，我调整了 RegisterChildNode 和 ChildNodes 调用，为命名空间传递一个空白字符串(这在手动解析时确实有帮助)。现在我遇到了接口(interface)转换错误。

有希望让这个生成器工作吗？也许结构太复杂了，我并不真正需要双向绑定(bind)。我正在寻找一种可读的(类似 map /字典？)的数据提取方式(不受 XML 特殊性的支配)。类型安全不是必须的。

这不一定是一个以 Delphi 为中心的问题。恐怕 XSD.exe 对于 .NET 来说也不会做得更好。也许任何人都可以分享经验，让我的工作更轻松

Answer 1

What I'm looking for is a readable (map/dictionary-like?) way of extracting the data (not dominated by the particularities of XML).

你那里有一点问题。寻求从丰富的 XSD 语义映射到简单的字典结构本质上是有问题的。

It's not necessarily a Delphi-centered question. I'm afraid XSD.exe wouldn't do a much better job for .NET. Perhaps anyone can share experience with that to make my job easier.

两个建议:

1. 要了解 XSD 中指定的关系，请汇总您的袖子并理解 XSD，而不是试图绘制出你的出路XSD。

2. 要根据 XSD 自动测试条件，请利用现有的工具。

   对您来说，好消息是 XSD 是 XML 文档，因此可以被许多可以解析 XML 的语言的工具进行解析。

   坏消息是，XSD 的语义非常复杂，除了在有限情况下进行简单的抽查之外，您将很难对所有情况进行一般分析。

为了处理 XML 和 XSD，我建议使用基于 XPath 的查询而不是其他技术，特别是如果您可以利用 Schema-aware processing with XSLT 2.0 .