Import
Related Doc:
package dsom
The enclosing component, and follows back-references from types to their elements, from globalElementDef to elementRefs, from simpleType defs to derived simpletype defs, from global group defs to group refs
The enclosing component, and follows back-references from types to their elements, from globalElementDef to elementRefs, from simpleType defs to derived simpletype defs, from global group defs to group refs
Note: the enclosing component of a global element or global group referenced from a element ref or group ref, is NOT the ref object, but the component that contains the ref object
Define this for schema components that have back-references to ref objects.
Define this for schema components that have back-references to ref objects. So group def to group ref, globalelementdecl to element ref, type to element, base type to derived type.
Not for format annotations however. We don't backpoint those to other format annotations that ref them.
All schema components except the root have an enclosing element.
All schema components except the root have an enclosing element.
Unconditionally, get the schema file object.
Unconditionally, get the schema file object.
Get the schema file if it isn't one we have seen before.
Get the schema file if it isn't one we have seen before.
If it new to us, then get it. This can cause a failure if the file doesn't exist but we need it to determine the namespace. That is, the Option here does NOT return None for file-not-found. It's only about whether we've already got this file in the (ns, url) map we're maintaining.
This can succeed even if the file will not be found later when someone asks for the schema document, or if at that point its namespace is not acceptable given the import statement.
Whether the component is hidden.
Whether the component is hidden.
Override this in the components that can hide - SequenceGroupRef and ChoiceGroupRef
Annotations can contain expressions, so we need to be able to compile them.
Annotations can contain expressions, so we need to be able to compile them.
We need our own instance so that the expression compiler has this schema component as its context.
Namespace scope for resolving QNames.
Namespace scope for resolving QNames.
We insist that the prefix "xsi" is properly defined for use in xsi:nil attributes, which is how we represent nilled elements when we convert to XML.
Used as factory for the XML Node with the right namespace and prefix etc.
Used as factory for the XML Node with the right namespace and prefix etc.
Given "element" it creates <dfdl:element /> with the namespace definitions based on this schema component's corresponding XSD construct.
Makes sure to inherit the scope so we have all the namespace bindings.
The lexically enclosing schema component
The lexically enclosing schema component
path is used in diagnostic messages and code debug messages; hence, it is very important that it be very dependable.
path is used in diagnostic messages and code debug messages; hence, it is very important that it be very dependable.
XML Catalog is tried first, then classpath
Only import has a namespace URI.
Only import has a namespace URI.
This will be Some(URL) for reading an imported schema, if we resolved the namespace URI via the XML Catalog.
Both include and import have schemaLocation.
Both include and import have schemaLocation. For import it is optional. If supplied we resolve it via the classpath, relative to the location of the including/importing file, etc.
ALl non-terms get runtimeData from this definition.
ALl non-terms get runtimeData from this definition. All Terms which are elements and model-groups) override this.
The Term class has a generic termRuntimeData => TermRuntimeData function (useful since all Terms share things like having charset encoding) The Element classes all inherit an elementRuntimeData => ElementRuntimeData and the model groups all have modelGroupRuntimeData => ModelGroupRuntimeData.
There is also VariableRuntimeData and SchemaSetRuntimeData.
Includes instances.
Includes instances. Ie., a global element will appear inside an element ref. a global group inside a group ref, a global type inside an element or for derived simple types inside another simple type, etc.
Used in diagnostic messages and code debug messages
(ns, file) that we've seen before.
(ns, file) that we've seen before.
Includes this file we're currently on (if we haven't seen it) so that if our own includes/imports cycle back to us we will detect it.
Elements only e.g., /foo/ex:bar
Elements only e.g., /foo/ex:bar
This is the root, or basic target namespace.
This is the root, or basic target namespace. Every schema component gets its target namespace from its xmlSchemaDocument.
Used in diagnostic messages; hence, valueOrElse to avoid problems when this can't get a value due to an error.
Used in diagnostic messages; hence, valueOrElse to avoid problems when this can't get a value due to an error.
An import statement.
The enclosingGoalNamespace argument is Some(noNamespace) for a topLevel schema file that has no targetNamespace attribute.
Now consider that we could be an import which is inside an included schema which includes another included, etc. A nest of included schemas the innermost of which then contains an import. We have to verify that the ultimate goal namespace at the start of that chain of includes is different from this imported schema's goalNamespace.