using XSD with import statements

[dellard]

I have an XSD schema file that imports types from a different namespace. It seems like Ontmalizer ignores import statements: if I save the model as TTL, there's no mention of the elements with the imported types, and when I try to load a document, it fails.

Are imports supposed to work, or is this a known limitation?

[juandm]

Ontmalizer ignores import tag as stated in the last part of this blog post (http://www.srdc.com.tr/projects/salus/blog/?p=189)..

Some Notes about Ontmalizer

The current implementation does not take into account xsd:import; yet only xsd:include is supported.

@dellard could you find a solution/workaround to this problem?

[dellard]

Our workaround was to copy the files we wanted to import into our schema and rename a lot of things. It was fairly awkward, but since our schema was mostly static, it was only awkward once.

I don't recall why we didn't use try to use xs:include instead. (There may have been problems with other tools as well.)

It would be a nice feature to have, because we anticipate that the schema will become significantly more complex in the next phase of development. (we don't need it, but it would be elegant)

[juandm]

Put all in one XSD schema is not an option in my case, because is a standard XSD and there are chains of imports (so rename all namespaces could be a nigthmare). If i cant find another tool to do that i would try to create this feature here.

Thanks for the reply!

[crockct]

My pull request that handles xsd:import was merged into master!

[dellard]

FANTASTIC! Daniel Ellard Senior Scientist, Network & Cyber Technology Raytheon BBN Technologies [email protected] 617-873-8004 (office)

…

________________________________ From: Colleen Rock <[email protected]> Sent: Sunday, November 4, 2018 3:25:42 PM To: srdc/ontmalizer Cc: Dan ELLARD; Mention Subject: [External] Re: [srdc/ontmalizer] using XSD with import statements (#16) My pull request that handles xsd:import was merged into master! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMONyhOcBScxZEuqaiotwZnobUZlkO4Yks5ur01GgaJpZM4OCfy5>.