Generating a C# class from an S1000D schema ,called descript.xsd, fails

[RJerrell]

Forgive my ignorance please. I'm trying to make sense of the failures I'm getting when trying to generate C# classes from the 27 xsd schemas that define each of the document types in S1000D.
More information about the specification can be found at https://s1000d.org

Preliminary:

This is a partial list, for simplicity of this discussion, for the S1000D 4.0.1 schema file names in a workspace on my local machine. The workspace actually covering all 27 schemas for the 4.0.1 release of S1000D documents.

descript.xsd : http://www.s1000d.org/S1000D_4-0-1/xml_schema_flat/descript.xsd
dc.xsd
rdf.xsd
xcf.xsd
xlink.xsd

Requirement : Generate a C# class compliant with descript.xsd

My Attempt to generate C# classes failed

<xs:schema attributeFormDefault="qualified"
    elementFormDefault="qualified"
    **xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"**
    xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    **<xs:import namespace="http://www.w3.org/1999/xlink" schemaLocation="xlink.xsd"/>**
    **<xs:import namespace="http://www.w3.org/1999/02/22-rdf-syntax-ns#" schemaLocation="rdf.xsd"/>**
    <xs:annotation>
        <xs:documentation>Issue number: 4.0</xs:documentation>
        <xs:documentation>Issue date: 2008-08-01</xs:documentation>
        <xs:documentation>Release number: 4.0</xs:documentation>
        <xs:documentation>Release date: 2008-08-01</xs:documentation>
        <xs:documentation>URL: http://www.s1000d.org/S1000D_4-0/xml_schema_flat/descript.xsd</xs:documentation>
        <xs:documentation>Root element: dmodule</xs:documentation>
        <xs:documentation>Copyright:
			Copyright (C) 2008 by each of the following organizations:
			1.  AeroSpace and Defence Industries Associations of Europe - ASD.
			2.  Ministries of Defence of the member countries of ASD.
		
			Limitations of Liability:
	
			1.  This material is provided "As Is" and neither ASD nor any person who has contributed to the creation, revision or maintenance of the material makes any representations or warranties, express or implied, including but not limited to, warranties of merchantability or fitness for any particular purpose.
			2.  Neither ASD nor any person who has contributed to the creation, revision or maintenance of this material shall be liable for any direct, indirect, special or consequential damages or any other liability arising from any use of this material.
			3.  Revisions to this document may occur after its issuance.  The user is responsible for determining if revisions to the material contained in this document have occurred and are applicable. 
		</xs:documentation>
        <xs:documentation>Remarks: none</xs:documentation>
    </xs:annotation>
    <xs:element name="dmodule" type="dmoduleElemType"/>

Given this excerpt from the descript.xsd schema I included the
When using xscgen.exe from the CLI in the folder where all the schemas are located, I get the following error message:

Using 3 schemas as arguments, I run the following command (from the CLI in the folder where all the schemas are located) attempting to insure that the descript.xsd has the import dependencies included; descript.xsd , rdf.xsd , lastly the xlink.xsd , all pipe separated, yields the following:

xscgen descript.xsd|rdf.xsd|xlink.xsd

Unhandled exception. System.ArgumentException: Namespace http://www.w3.org/1999/02/22-rdf-syntax-ns# not provided through map or generator.

Question:

I can generate classes for the rdf.xsd and xlink.xsd individually but not for the descript.xsd. The same problem occurs on all the other major document types: proced.xsd, ipd.xsd etc.

What am I missing?

Oh, and Happy New Year 2025 to all!

• Roger

[mganss]

You need to provide a mapping from the XML namespace http://www.w3.org/1999/02/22-rdf-syntax-ns# to a C# namespace. If it's just this one or a small number of XML namespaces you can do it on the commandline using e.g. -n "http://www.w3.org/1999/02/22-rdf-syntax-ns#=RdfSyntax. If there are many namespaces you can also provide the mapping through a configuration file. See
https://github.com/mganss/XmlSchemaClassGenerator?tab=readme-ov-file#using-mapping-files

[RJerrell]

This CLI command worked but the map file didn't. xscgen -n "|xlink.xsd=S1000D.401" -n "|rdf.xsd=S1000D.401" -n "|descript.xsd=S1000D.401" xlink.xsd rdf.xsd descript.xsd The use of the map file failed due to the '#' symbol in the namespace. From the command line it works fine. I'll process the 27 classes for this version, S1000D 4.0.1 and see if it works for my application. There are 6 modern version of that specification with major/minor variances and patches over the 30 years. We have about 35 million files on 1 commercial aircraft program alone that uses this technology and this will help standardize the way we process them. When I complete a generic prototype of the finished product, I'll provide a repo address for you and send it to you. Many thanks for the many years you've put into this project. Thanks, Roger Jerrell, ☸

…

On Thu, Jan 2, 2025 at 9:19 AM Michael Ganss ***@***.***> wrote: You need to provide a mapping from the XML namespace http://www.w3.org/1999/02/22-rdf-syntax-ns# to a C# namespace. If it's just this one or a small number of XML namespaces you can do it on the commandline using e.g. -n " http://www.w3.org/1999/02/22-rdf-syntax-ns#=RdfSyntax. If there are many namespaces you can also provide the mapping through a configuration file. See https://github.com/mganss/XmlSchemaClassGenerator?tab=readme-ov-file#using-mapping-files — Reply to this email directly, view it on GitHub <#541 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPRHAJHTBS5AOHPV7ACQML2IVYKXAVCNFSM6AAAAABUO7TAEOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZRHEYDCOA> . You are receiving this because you authored the thread.Message ID: <mganss/XmlSchemaClassGenerator/repo-discussions/541/comments/11719018@ github.com>

[mganss]

Thanks for the kind words Roger ❤️

I'm surprised the mapping file approach didn't work. The # character should introduce a comment only if it's the first non-whitespace character on a line. Can you share the mapping file you created?

If you have any suggestions on how to streamline the namespace mapping process, let me know.

[RJerrell]

At my first opportunity, I'll definitely share the map. If not the '#' sign it may be the fact the namespace has an = # it. I haven't debugger it yet. I look forward to working with this library in the near future. Thanks, Roger

…

On Fri, Jan 3, 2025, 10:09 AM Michael Ganss ***@***.***> wrote: Thanks for the kind words Roger ❤️ I'm surprised the mapping file approach didn't work. The # character should introduce a comment only if it's the first non-whitespace character on a line. Can you share the mapping file you created? If you have any suggestions on how to streamline the namespace mapping process, let me know. — Reply to this email directly, view it on GitHub <#541 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPRHAJN6CRUQN4VVXGJZUT2I3G5DAVCNFSM6AAAAABUO7TAEOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZSHAYDIMQ> . You are receiving this because you authored the thread.Message ID: <mganss/XmlSchemaClassGenerator/repo-discussions/541/comments/11728042@ github.com>