Hello,

I'm working as a Technical Architecte on SOA Governance standards.
My current client designed an Enterprise Data model with XSD files, some of objects are referencing themselves (a company has contacts, and contacts are attached to a company).
Today, I'm working on JSon Technical Design rules, and I wanted to base my assessment on Json Enterprise Data model, but the cycles between XSD are not correctly understood by xsd2json.

I also had some issues when I am not using the option "-u", I'm quite sure that using this option by default could help many people who are trying to resolve the problem by installing Visual Studio or Microsoft Visual Express or SDK or many other frameworks ..... With -u option at the end it is not necessary and more simple.

Could you please provide a patch for these loops?
From my point of view, I analyzed the JSON files generated from an XSD without cycles, and I can see that references on complextypes are writen, as for XSD. So when the Complextype is detected the first time, it must be generated in the JSON file, but the second time, it is not necessary to go ahead on it.
I think that a simple hashtable in memory, reminding the complextype "already processed" in order to NOT analyze them twice could be a good entry point, but as I am not expert on Javascript and Swiple programs, I am not able to propose a solution.

You can contact me on this email: [email protected]

Thxs for your help,
Richard

Used xsd:

<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="dog" type="xs:string" />
</xs:schema>

code:

let xsd2json = require('xsd2json');
let filename = '${__dirname}/schema.xsd';

// use as function
xsd2json(filename, (err, schemaObject) => {
    console.log(err);
    console.log(JSON.stringify(schemaObject));
});

Error message:

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at /home/heucles/dev/c4-omnigateway/app/node_modules/xsd2json/index.js:55:25
    at ConcatStream.<anonymous> (/home/heucles/dev/c4-omnigateway/app/node_modules/concat-stream/index.js:36:43)
    at emitNone (events.js:110:20)
    at ConcatStream.emit (events.js:207:7)
    at finishMaybe (/home/heucles/dev/c4-omnigateway/app/node_modules/readable-stream/lib/_stream_writable.js:607:14)
    at endWritable (/home/heucles/dev/c4-omnigateway/app/node_modules/readable-stream/lib/_stream_writable.js:615:3)
    at ConcatStream.Writable.end (/home/heucles/dev/c4-omnigateway/app/node_modules/readable-stream/lib/_stream_writable.js:571:41)
    at Socket.onend (_stream_readable.js:598:10)
    at Object.onceWrapper (events.js:314:30)
undefined
<Buffer 5b 46 41 54 41 4c 20 45 52 52 4f 52 3a 0a 09 43 6f 75 6c 64 20 6e 6f 74 20 6f 70 65 6e 20 72 65 73 6f 75 72 63 65 20 64 61 74 61 62 61 73 65 20 22 2f ... >

Version 10.4.0 of tap just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tap is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The following example XSD does not create any JSON Schema:

<?xml version="1.0" ?>
<xs:schema>
  <xs:element name="pet">
    <xs:simpleType>
      <xs:restriction base="xs:string">
        <xs:enumeration value="dog" />
        <xs:enumeration value="cat" />
      </xs:restriction>
    </xs:simpleType>
  </xs:element>
</xs:schema>

The following schema element

<xs:complexType name="Resource">
  <xs:annotation><xs:documentation>
     Added in Version 1.2: INFO for diagnostics in several places
  </xs:documentation></xs:annotation>
  <xs:sequence>
    <xs:element name="DESCRIPTION" type="anyTEXT" minOccurs="0"/>
    <xs:element name="INFO" type="Info" minOccurs="0" maxOccurs="unbounded"/>
    <xs:choice minOccurs="0" maxOccurs="unbounded">
      <xs:element name="COOSYS" type="CoordinateSystem"/><!-- Deprecated in V1.2 -->
      <xs:element name="GROUP" type="Group" />
      <xs:element name="PARAM" type="Param" />
    </xs:choice>
</xs:complexType>

gives this JSON schema fragment:

   "Resource": {
      "properties": {
        "name": {
          "type": "string"
        },
        "DESCRIPTION": {
          "$ref": "#/definitions/anyTEXT"
        },
        "INFO": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/Info"
          },
          "minItems": 0
        }
}

We can see that children elements COOSYS/GROUP/PARAM are ignored. Therefore they are not validated although their schema is well defined in the schema.

Operating System = Windows 10
Node 6.10

var path = require('path');
var xsd2json = require('xsd2json');

var filename = path.join(__dirname, 'node_modules/xsd2json/test/XMLSchema2.xsd');

// use as function
xsd2json(filename, function(err, schemaObject) {
	if (err) console.log(err);
	console.log(JSON.stringify(schemaObject, null, 2));
});

[1] SyntaxError: Unexpected end of JSON input
[1]     at Object.parse (native)
[1]     at C:\@repositories\pir-model-preparer\node_modules\xsd2json\index.js:55:25
[1]     at ConcatStream.<anonymous> (C:\@repositories\pir-model-preparer\node_modules\concat-stream\index.js:36:43)
[1]     at emitNone (events.js:91:20)
[1]     at ConcatStream.emit (events.js:185:7)
[1]     at finishMaybe (C:\@repositories\pir-model-preparer\node_modules\readable-stream\lib\_stream_writable.js:504:14)
[1]     at endWritable (C:\@repositories\pir-model-preparer\node_modules\readable-stream\lib\_stream_writable.js:514:3)
[1]     at ConcatStream.Writable.end (C:\@repositories\pir-model-preparer\node_modules\readable-stream\lib\_stream_writable.js:484:41)
[1]     at Socket.onend (_stream_readable.js:511:10)
[1]     at Socket.g (events.js:291:16)

Hey guy,

at first thanks for working on my issue. Nevertheless I have the question, if you could add support for xs:unsignedInt.

Would it be possible, to add the entry type to every json-object, nevertheless if you can resolve the type?
Example:
If the type is xs:unsignedInt and you are not able to resolve it, you can just add
"element" : {
"type" :"unsignedInt",
"description" :"whatever"
}

Maybe you already added this support, but atm I am at version 1.0.1 because with version 1.2.1 the generation of json-schema-files is not working anymore. Is there a way for me, to debug the process or to help finding the error on my xsd-files or your process?

Atm you dont create an entry for the type-field instead, right?

Thanks in advance,
PiQ99

Hey guy,

is there any hint, why the order gets changed for xsd-elements, that are getting transformed into a json-schema file?

I came across this problem, when the order was checked of the elements that are included in a sequence-tag. There, the order is not allowed to be changed related to the xsd-schema. In contrast to this, I know, json is not able / or dont has to maintain the same order.

Here is an example, which was converted with version 1.0.1 of xsd2json: http://jsfiddle.net/PiQ99/vz3mcm7g/

Is there anything that can be changed to have the same order? :-)

Thanks for your answer.

Hi,

I need to do xml validation against xsd. i thought of using libxmljs module. i couldn't move forward with it as it has some building/installation issues. Moreover, i haven't found any other module to accomplish the task.

Now, i would like to use xsd2json converter to convert XSD to JSON and XML to JSON and validate it.

Please let me know if there is already a validator for this. or how do you suggest me to go about this.

Thanks,
Raja

swipl --quiet --nodebug --g 'main,halt' -s cli.pl -- < /path/to/your.xsd

--g 'main,halt' should be -g 'main,halt'

@fnogatz just updated to version 7.6.3, but also rebuilded the package, but I am still facing the same issues as in #76 .Any Ideas?

Ubuntu 16.04
swi-prolog-nox 6.6.4-2ubuntu1
xsd2json 1.7.7

$ xsd2json schema.xsd > schema.json
ERROR: Prolog initialisation failed:
ERROR: Domain error: `sgml_option' expected, found `help(false)'

I have no knowledge of prolog whatsoever, but I am a developer. I can hack and slash my way through code if need be. What other information do you need?

According to http://www.w3schools.com/xml/schema_example.asp it is possible to specify multiple top-level xs:element nodes. Use anyOf to handle them. See http://stackoverflow.com/questions/8854144/xml-schema-root-element.

Does this tool convert losslessly from XSD to JSON-schema?

xsd2json
/usr/local/bin/xsd2json: 3: exec: /home/fnogatz/.swivm/versions/7.2.3/lib/swipl-7.2.3/bin/x86_64-linux/swipl: not found

What is "/home/fnogatz/.swivm/versions/7.2.3/lib/swipl-7.2.3/bin/x86_64-linux/swipl" ?

Version 2.12.1 of commander was just published.

This version is covered by your current version range and after updating it in your project the build failed.

commander is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The XMLSchema.xsd authorizes any element (with relaxed validation) in documentation content :

<xs:element name="documentation" id="documentation">
...
  <xs:complexType mixed="true">
    <xs:sequence minOccurs="0" maxOccurs="unbounded">
      <xs:any processContents="lax"/>
    </xs:sequence>
    ...
  </xs:complexType>
</xs:element>

so this xsd

<?xml version="1.0" encoding="UTF-8"?>
<s:schema targetNamespace="http://www.mgdis.fr/public/demande-paiement/v1" 
    xmlns:s="http://www.w3.org/2001/XMLSchema" 
    xmlns:tns="http://www.mgdis.fr/public/demande-paiement/v1" 
    elementFormDefault="qualified">
  <s:element name="acomplexobject">
    <s:complexType>
      <s:sequence>
        <s:element name="aproperty" type="s:string" minOccurs="0">
          <s:annotation>
            <s:documentation xml:lang="EN"><p>A description</p></s:documentation>
          </s:annotation>
        </s:element>
      </s:sequence>
    </s:complexType>
  </s:element>
</s:schema> 

should generate this jsonschema

{
  "type":"object", 
  "properties": {
    "aproperty": {
      "description":"<p>A description</p>",
      "type":"string"
    }
  }
}

but it fails with :

ERROR: Prolog initialisation failed:
ERROR: term_to_atom/2: Type error: `text' expected, found `http://www.w3.org/2001/XMLSchema:documentation'

The question is open :
Does it parse the xhtml tag (especially <br/> with \n) or does it restitute the description unchanged ?

P.S. : Thanks for your projet :)

Hi

I do not manage to install xsd2json with .
swipl has ben installed from sources and sems to to work.
I got the following errors which are opaque to me.
That look like a broken dependency.
Have you an idea?

Laurent

michel@obs-he-lm:~/gitRepositories/xsd2json$ sudo npm install -g xsd2json
/usr/bin/xsd2json -> /usr/lib/node_modules/xsd2json/lib-pl/cli

> [email protected] postinstall /usr/lib/node_modules/xsd2json
> npm run create-qlf


> [email protected] create-qlf /usr/lib/node_modules/xsd2json
> swipl -O --goal=main -o lib-pl/cli -c lib-pl/cli.pl

ERROR: /usr/lib/node_modules/xsd2json/lib-pl/helpers.pl:8:
	source_sink `library(sgml_write)' does not exist
Warning: /usr/lib/node_modules/xsd2json/lib-pl/helpers.pl:8:
	Goal (directive) failed: helpers:use_module(library(sgml_write))
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:9:
	source_sink `library(chr)' does not exist
Warning: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:9:
	Goal (directive) failed: xsd2json:use_module(library(chr))
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:10:
	source_sink `library(http/http_open)' does not exist
Warning: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:10:
	Goal (directive) failed: xsd2json:use_module(library(http/http_open))
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:13:
	source_sink `library(sgml)' does not exist
Warning: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:13:
	Goal (directive) failed: xsd2json:use_module(library(sgml))
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:30:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:40:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:42:1: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:56:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:63:1: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:78:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:85:1: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:90:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:99:1: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:111:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:115:1: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:130:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:147:18: Syntax error: Operator expected
ERROR: /usr/lib/node_modules/xsd2json/lib-pl/xsd2json.pl:152:1: Syntax error: Operator expected
....

Why there is an extra |: string in the most begining of json schema output, my xml schema is:

<!-- filename: models.xsd-->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:element name="models">
        <xs:complexType>
            <xs:all>
                <xs:element name="User" type="User" minOccurs="0"/>
                <xs:element name="Device" type="Device" minOccurs="0"/>
                <xs:element name="Ad" type="Ad" minOccurs="0"/>
            </xs:all>
        </xs:complexType>
    </xs:element>
    <xs:complexType name="User">
        <xs:sequence>
            <xs:element name="id" type="xs:nonNegativeInteger"/>
            <xs:element name="name" type="xs:string"/>
        </xs:sequence>
    </xs:complexType>
    <xs:complexType name="Device">
        <xs:sequence>
            <xs:element name="id" type="xs:nonNegativeInteger"/>
            <xs:element name="name" type="xs:string"/>
        </xs:sequence>
    </xs:complexType>
    <xs:complexType name="Ad">
        <xs:sequence>
            <xs:element name="id" type="xs:nonNegativeInteger"/>
            <xs:element name="name" type="xs:string"/>
            <xs:element name="user_id" type="xs:nonNegativeInteger"/>
        </xs:sequence>
    </xs:complexType>
</xs:schema>

and with the following command line:

swipl --quiet --nodebug -g 'main,halt' -s lib/cli.pl -- < test/xsd/models.xsd

The output is:

|:  {
  "definitions": {
    "User": {
      "required": ["id", "name" ],
      "type":"object",
      "properties": {
    "id": {"type":"integer", "minimum":0, "exclusiveMinimum":false},
    "name": {"type":"string"}
      }
    },
    "Device": {
      "required": ["id", "name" ],
      "type":"object",
      "properties": {
    "id": {"type":"integer", "minimum":0, "exclusiveMinimum":false},
    "name": {"type":"string"}
      }
    },
    "Ad": {
      "required": ["id", "name", "user_id" ],
      "type":"object",
      "properties": {
    "id": {"type":"integer", "minimum":0, "exclusiveMinimum":false},
    "name": {"type":"string"},
    "user_id": {"type":"integer", "minimum":0, "exclusiveMinimum":false}
      }
    }
  }
}

The complextType someType will not be added to the JSON definition output.
Looks like the simpleContent element is not recorginzed by the translator.

input

<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns="http://example.local"
           xmlns:xs="http://www.w3.org/2001/XMLSchema"
           targetNamespace="http://example.local"
           elementFormDefault="qualified">
    <xs:element name="test" type="someType" />

    <xs:complexType name="someType">
        <xs:simpleContent>
            <xs:extension base="someRestrictionType">
                <xs:attribute name="id" type="xs:ID" />
            </xs:extension>
        </xs:simpleContent>
    </xs:complexType>

    <xs:simpleType name="someRestrictionType">
        <xs:restriction base="xs:double">
            <xs:minInclusive value="0" />
        </xs:restriction>
    </xs:simpleType>
</xs:schema>

output

{
  "definitions": {
    "someRestrictionType": {
      "type":"number",
      "minimum":0,
      "exclusiveMinimum":false
    }
  },
  "allOf": [
    {
      "$ref":"#/definitions/someType"
    }
  ]
}

the xsd2jon command fails with this xsd :

<?xml version="1.0" encoding="UTF-8"?>
<s:schema targetNamespace="http://www.mgdis.fr/public/demande-paiement/v1" 
    xmlns:s="http://www.w3.org/2001/XMLSchema" 
    xmlns:tns="http://www.mgdis.fr/public/demande-paiement/v1" 
    elementFormDefault="qualified">
  <s:element name="acomplexobject">
    <s:complexType>
      <s:sequence>
        <s:element name="aproperty" type="s:string" minOccurs="0"/>
        <s:element name="description" type="s:string" minOccurs="0">
          <s:annotation>
            <s:documentation xml:lang="EN">A description for the description field</s:documentation>
          </s:annotation>
        </s:element>
      </s:sequence>
    </s:complexType>
   </s:sequence>
</s:schema> 

This should generate a json like :

{
  "type":"object",
  "properties": {
    "description": {
      "description":"A description for the description field",
      "type":"string"
    },
    "aproperty": {"type":"string"}
  }
}

but the process returns this error :

ERROR: Prolog initialisation failed:
ERROR: string_concat/3: Type error: `atomic' expected, found `json([description=A description for the description field,type=string])'

Hello again :)

When running cli.pl I encounter the following errors:

ERROR: c:/users/mouton-a/sandbox/git/xsd2json/prolog-xsd2json/merge_json.pl:60:14: Syntax error: Operator expected
ERROR: c:/users/mouton-a/sandbox/git/xsd2json/prolog-xsd2json/xsd2json.pl:380:12: Syntax error: Operator expected
ERROR: c:/users/mouton-a/sandbox/git/xsd2json/prolog-xsd2json/xsd2json.pl:381:11: Syntax error: Operator expected

Most of the times this is non-blocking. But on some XSDs it is followed by the blocking error:

ERROR: c:/users/mouton-a/sandbox/git/xsd2json/prolog-xsd2json/cli.pl:5: Initialization goal raised exception:
ERROR: xsd2json:convert_xsd_restriction/3: Undefined procedure: xsd2json:json_false/1

The 3 lines contain arobases. Coincidence ? I think not !

Wondering if this could be an encoding problem I tried adding ':- encoding(utf8).' to the source files. But it didn't fix anything and being totally ignorant of prolog I am already out of ideas.

Environment:

$ swipl -v
SWI-Prolog version 6.6.6 for i386-win32

Attempting to convert 5 XSDs linked by import using this tool and unfortunately it gets so far then stops with the following error: (I have installed swipl)

debug: Spawn prolog xsd2json program
events.js:182
throw er; // Unhandled 'error' event
^

Error: spawn swipl ENOENT
at _errnoException (util.js:1019:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:192:19)
at onErrorNT (internal/child_process.js:374:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)

unfortunately, i'm unable to provide the XSDs. Is there any other information I can provide to assist?

When I tried to run on Ubuntu 14.04 this happen:

/usr/local/bin/xsd2json -> /usr/local/lib/node_modules/xsd2json/lib-pl/cli

[email protected] postinstall /usr/local/lib/node_modules/xsd2json
npm run create-qlf

/usr/local/lib/node_modules/.bin/npm: 2: exec: /usr/local/lib/node_modules/.bin/node: not found
npm ERR! Linux 3.13.0-92-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "xsd2json"
npm ERR! node v4.2.2
npm ERR! npm v2.14.7
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! [email protected] postinstall: npm run create-qlf
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] postinstall script 'npm run create-qlf'.
npm ERR! This is most likely a problem with the xsd2json package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run create-qlf
npm ERR! You can get their info via:
npm ERR! npm owner ls xsd2json
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/sciensa/npm-debug.log

I installed the swipl on my mac osx 10.10 (Yosemite). I had to manually add a /usr/local/bin/swipl link. When I run swipl I get the prompt, so I exit out. I then installed xsd2json and that was fine. Now when I run xsd2json, I just see a spinning | character and it sits there forever. I've let it go for 2 hours, still nothing. I thought maybe it was just extremely slow, but obviously it's more than that.

Are there some updated Mac OS instructions/steps on how to install and get it to work? I can't seem to find the man documentation for it either.

Thanks.

I get this error:

stack": [
"Error: spawn swipl ENOENT",
" at exports._errnoException (util.js:746:11)",
" at Process.ChildProcess._handle.onexit (child_process.js:1053:32)",
" at child_process.js:1144:20",
" at process._tickDomainCallback (node.js:381:11)",
" at process. (/home/syedn/proj/ori/propfi/node_modules/loopback/node_modules/continuation-local-storage/node_modules/async-listener/index.js:18:15)"
],
"level": "error",
"message": "uncaughtException: spawn swipl ENOENT"

Hi,

This is a great tool.
I'm facing issue in the following scenario.
XSD1.....>XSD2------>XSD3.
It's throwing out error (going to infinite loop)while trying to reference xsd3.
Is there a setting that restricting to do get 3rd level reference?
Thanks,
Purush

The devDependency commander was updated from 2.19.0 to 2.20.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

commander is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency tap was updated from 12.5.1 to 12.5.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 11.1.1 of tap was just published.

This version is covered by your current version range and after updating it in your project the build failed.

tap is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hello,
Having issues with increasing the stack limit on my mac.

:/~/Downloads/xsd2json-master $ swipl --stack_limit=4g
Welcome to SWI-Prolog (threaded, 64 bits, version 8.0.2)
SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software.
Please run ?- license. for legal details.

For online help and background, visit http://www.swi-prolog.org
For built-in help, use ?- help(Topic). or ?- apropos(Word).

?- halt.

Post this setting of stack_limit to 4 GB I run the conversion program but fails with below error:

ERROR: -g user:main: Stack limit (1.0Gb) exceeded
ERROR: Stack sizes: local: 3.4Mb, global: 0.6Gb, trail: 0.4Mb
ERROR: Stack depth: 77,673,357, last-call: 100%, Choice points: 8,947
ERROR: In:
ERROR: [77,673,357] assoc:adjust(yes, '<garbage_collected>', left, _27862, yes)
ERROR: [77,673,354] assoc:insert(<, '<garbage_collected>', '<garbage_collected>', x, _27890, _27892)
ERROR: [77,673,352] assoc:insert(<, '<garbage_collected>', '<garbage_collected>', x, _27918, _27920)
ERROR: [77,673,350] assoc:insert(<, '<garbage_collected>', '<garbage_collected>', x, _27946, _27948)
ERROR: [77,673,348] assoc:insert(<, '<garbage_collected>', '<garbage_collected>', x, _27974, _27976)
ERROR:
ERROR: Use the --stack_limit=size[KMG] command line option or
ERROR: ?- set_prolog_flag(stack_limit, 2_147_483_648). to double the limit.

It's clearly seen that the 4GB value is not applied.

Can you please help?

Thanks for the impressive piece of work.

In your thesis you specifically mention that xsd2json doesn't support the extension of complex types. Do you have any project to fill this gap ? If not, do you have a solution in mind to implement this functionality that maybe another developer could contribute ?

I have no deep understanding of the problem or of your program, but I wonder if the simplest solution could be to do some merging of the complex types definitions before applying CHR rules ?

I also wonder about include and import that you say are not supported. Do you think a simple merge of included schemas in the root schema will do the trick ?

Basically: do you think a not too complex tranformation (xslt or other) applied on the schemas before processing by xsd2json could help overcome its limitations ?

Alban

Hey,

at first I have to say, I like your work. It is a great tool that helps me a lot at the moment. In addition I wanted to ask, if you plan further development? There are several things to do I guess.
Of course I saw, you did not commit anything about two months now, but maybe you continued developing at home?

e.g. what about:

• ref-attributes in element-tags
• the documentation-attibute in a complexType (it gets ignored I guess atm?)
• complexTypes in element-tags?

These are several things that do not work atm, afaik, and I wanted to ask, if you are going to fix these things, maybe?

Thanks for your answer and have a nice week!

Version 2.13.0 of commander was just published.

This version is covered by your current version range and after updating it in your project the build failed.

commander is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The xsd2json command is not installed correctly on Windows. It assumes the presence of /bin/sh.exe or /bin/sh, which (ha ha) does not exist on Windows unless you have Cygwin or similar.

At the very least, the documentation should be updated to reflect that. Ideally, unless a UNIX shell is required, the install should only reference Windows standard executable.

Thanks for this great tool.

Given a root xsd, is it possible to create separate corresponding jsonschema files for each xsds referenced along the way?

I have a large tree of xsds and swipl bails out with following error:
ERROR: -g main: Out of global stack

Any ideas welcome.

The read_string/3 predicate used in markup_to_string/4 of helpers.pl is defined only since SWI-Prolog of version 6 (corresponding commit). That's why xsd2json fails for XSDs which include xs:documentation tags:

> ./lib-pl/cli test/xsd/annotation.xsd 
ERROR: Prolog initialisation failed:
ERROR: helpers:markup_to_string/4: Undefined procedure: helpers:read_string/3

E.g.

<xs:attribute name="countryCode" type="xs:string"/>

becomes

"@countryCode": {
    "type": "string"
}

Is there the possibility, to add option-parameters to xsd2json :-)? E.g. it would be nice, if the user could handle, if the result file should contain "$ref"s or not?!

Thanks again!

I try to convert with this code:

var xsd2json = require('xsd2json');
var filename = '../examples/release-notification.xsd';

// use as function
xsd2json(filename, {'debug-info':true},function(err, schemaObject) {
  if(err) throw err;
  console.log(JSON.stringify(schemaObject, null, 2));
});

the xml schema from here http://service.ddex.net/xml/ern/37/release-notification.xsd
but in the console just have this error
ERROR: -g user:main: false

what it means?

if I remove this , {'debug-info':true} from the function, the execution hangs

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

I'm sorry to reopen an issue which is rather likely a user support request (I'm an absolute beginner with Prolog). I guess that some other users can have to face the same problem.

I properly setup my swipl with Aptitude and swivm as suggested in thread #53

michel@obs-he-lm:~$ swipl --version
SWI-Prolog  version 7.2.3 for x86_64-linux
michel@obs-he-lm:~$ swipl
Welcome to SWI-Prolog (Multi-threaded, 64 bits, Version 7.2.3)
Copyright (c) 1990-2015 ....
?- use_module(library(sgml)).
true.
?- use_module(library(chr)).
true.

When I try to process a schema, I get nothing on stdout; then I switch to the trace mode and I get the following output (truncated).

michel@obs-he-lm:~$ xsd2json -t purchaseorder.xsd
CHR:   (0) Insert: node_attribute(/home/michel/purchaseorder.xsd,[0],xmlns:xsd,http://www.w3.org/2001/XMLSchema,source) # <0>
....
....
CHR:   (1) Redo: node_attribute(/home/michel/purchaseorder.xsd,[0],xmlns:xsd,http://www.w3.org/2001/XMLSchema,source) # <0>
CHR:   (0) Fail: node_attribute(/home/michel/purchaseorder.xsd,[0],xmlns:xsd,http://www.w3.org/2001/XMLSchema,source) # <0>
ERROR: Prolog initialisation failed:
ERROR: Domain error: `chr_port' expected, found `none'

I've no idea at all (and Google either) about that chr_port.
Is there some missing parameter or resource?

LM

Hi there,
Thanks for this great library. I'm still cannot use this library properly.
I'm using windows 10, node v8.11.1, SWI-Prolog v7.6.4, and xsd2json v1.11.6 and I installed it globally.

Here is the simple xsd I've used

<?xml version="1.0" encoding="UTF-8"?>

<shiporder orderid="889923" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="shiporder.xsd">
  <orderperson>John Smith</orderperson>
  <shipto>
    <name>Ola Nordmann</name>
    <address>Langgt 23</address>
    <city>4000 Stavanger</city>
    <country>Norway</country>
  </shipto>
  <item>
    <title>Empire Burlesque</title>
    <note>Special Edition</note>
    <quantity>1</quantity>
    <price>10.90</price>
  </item>
  <item>
    <title>Hide your heart</title>
    <quantity>1</quantity>
    <price>9.90</price>
  </item>
</shiporder>

and then I've tried to run this on cmd xsd2json shiporder.xsd > schema.json and the result is schema.json file only contain

{
}

is there anything I've missed?
Thanks.

I get the following error when I try to use xsd2json:

Could not open resource database "/usr/local/bin/xsd2json": Inappropriate ioctl for device]

I noticed that the /usr/local/bin/xsd2json is a symlink to .../lib-pl/cli.exe and also saw the commit that talked about windows compatibility. Could this be the issue?

Version 10.7.0 of tap just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tap is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The devDependency ajv was updated from 6.8.1 to 6.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ajv is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The following XSD is perfectly valid:

<schema xmlns="http://www.w3.org/2001/XMLSchema">
  <element name="dog" type="string" />
</schema>

Unlike using the same with explicit xs: prefix namespace, it returns:

{
  "$ref":"#/definitions/string"
}