Davide Brunato

I could add a logger for export method (*export_schema* function in fact), providing *loglevel* optional argument like it's now for schema initialization/building.

Maybe for solving this a fix in this helper can be sufficient: ```python def replace_location(text: str, location: str, repl_location: str) -> str: repl = 'schemaLocation="{}"'.format(repl_location) pattern = r'\bschemaLocation\s*=\s*[\'\"].*%s.*[\'"]' % re.escape(location)...

The new release v3.1.0 has a fix for schema exports . The replacement pattern has been changed with a safer one (considering that the source is a valid XML document...

The XML namespace is already loaded within the meta-schema, so an `xs:import` element has to be present in the schema if the namespace is used (e.g. *xml:base*) but the import...

To clarify: the schema _export_ doesn't download nothing, it only uses the already downloaded XSD sources contained in the schema instance and save them locally.

> (and in many cases i found that the location points to an HTML page instead of a regular XSD file). > I'm sorry, I didn't remember well, the referred...

FYI about the special status of the above four base namespaces: https://www.w3.org/TR/xmlschema11-1/#sec-nss-special

@AmeyaVS: I will not change schema export for downloading skipped schemas like the case of *xml.xsd*, but in the next minor release I will add a new API `download_schemas()` for...

Keep it open, the next minor release should be ready soon.

The `download_schemas()` API is available with release v3.2.0.