Hi all, After reading the text about p:schema-import (btw, there is a typo in the first sentence: "...that will to be available to the pipeline"), I am not sure what should happen in this case: <p:pipeline> ... <p:import-schema .../> <!-- import schema A --> ... <p:declare-step> // a sub-pipeline ... <p:import-schema .../> <!-- import schema B --> ... </p:declare-step> ... </p:pipeline> If I read the spec correctly, schema definitions from schema A are available in the nested pipeline. But what about the other way around? I would say that in the scope of the nested pipeline, the schema definitions from schema B will be "merged" with A, but they will not be visible in the top-level pipeline. Is this correct? -- Also, what happens with schema definitions if I import a library that contains a schema-import? <p:library> <!-- "library.xpl" --> ... <p:import-schema .../> ... </p:library> <p:pipeline> ... <p:import href="library.xpl"/> ... </p:pipeline> -- Is p:import-schema still considered a feature at risk? If so, the spec does not mention this. Regards, VojtechReceived on Thursday, 24 July 2008 06:53:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 24 July 2008 06:53:07 GMT