Do XML Schema imports in .xsd files have significance to Nuxeo?
I have a doctype in a Nuxeo extension like this:
<doctype name="CreativeWork" extends="File">
<schema name="common" />
<schema name="dublincore"/>
<schema name="CreativeWork"/>
</doctype>
And an XML schema like this:
<?xml version="1.0" ?>
<xs:schema targetNamespace="http://schema.org/CreativeWork"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://schema.org/Thing" schemaLocation="Thing.xsd"/>
...
where the xs:import refers to another schema in the package.
My schemas and doctypes are available in Nuxeo—I checked by using nuxeo-doctypes-io—but I do not see any indication that the fields in Thing.xsd are available to documents with the CreativeWork doctype.
My guess is that Nuxeo does nothing with xs:import, and that if I wish to structure my custom document types like this, it should be done by adding the parent schemas to the doctype declaration. Is this guess correct?
 |
Steven Huwig
Member (2.3K) 3 5 6 |
02/18/2014 ( History) |
Hi,
Yes you can proceed like this, support of xs:import was added quite recently, it may not be supported depending on your version (added in 5.7.1, see NXP-10984).
If you're using Nuxeo 5.8, maybe it's configuration problem and the tests at the end of this commit could help? https://github.com/nuxeo/nuxeo-core/commit/c0687f3f0f94bae834eaa5e199ec9c495ab299fc
 |
Anahide Tchertchian
Member (15.4K) 3 6 6 |
02/21/2014 ( History) |
You can actually see this work at <https://github.com/courseload/nuxeo-schema-dot-org>, but it is not yet ready for general consumption.
<doctype extends="File" name="CreativeWork">
<schema name="common"/>
<schema name="dublincore"/>
<schema name="Thing"/>
<schema name="CreativeWork"/>
</doctype>
Elements from the Thing schema are available, but with
<doctype extends="File" name="CreativeWork">
<schema name="common"/>
<schema name="dublincore"/>
<schema name="CreativeWork"/>
</doctype>
I receive errors like [org.nuxeo.ecm.platform.el.DocumentModelResolver] Property not found: thing:url even though the XSD files have the imports defined and the contributions to org.nuxeo.ecm.core.schema.TypeService have the prefixes defined.
It seems the xs:import only allows you to declare types, not to declare fields (xs:element) that will be present in the schema… I'm not sure about the spec about this (and i haven't tested on my side)