Support url-based namespaces

[supertom01]

This feature might contribute to issue #84.

At least the files provided by the dutch government reference to their XBRL tags with URL based name spaces.

If a namespace is not special and it is an url, then it would be better to fetch it from the cache.

[supertom01]

@manusimidt

[manusimidt]

Hey @supertom01,
thanks for proposing the change. Do you have an example of a namespace that is equal to the schema URL?
Because to be honest I have never seen it until now, not in US submissions nor in UK submissions.

Usually, the namespace is always shorter like "http://fasb.org/us-gaap/2024" for the schema defined here: "https://xbrl.fasb.org/us-gaap/2024/elts/us-gaap-2024.xsd".

If something like this is to be implemented there needs to be a check for the HTTP status code and also for the file content. For example, if you go to https://fasb.org/us-gaap/2024.xml you get a HTML page telling you that the page does not exist. This must be somehow catched.

[supertom01]

Hi @manusimidt,

An example is illustrated below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><!--accept-sbr-converter
version: 5.1.1-->
<xbrli:xbrl xmlns:xbrli="http://www.xbrl.org/2003/instance"
    xmlns:link="http://www.xbrl.org/2003/linkbase" xmlns:xlink="http://www.w3.org/1999/xlink"
    xml:lang="nl"
    xmlns:jenv-bw2-i="http://www.nltaxonomie.nl/nt18/jenv/20231213/dictionary/jenv-bw2-data"
    xmlns:kvk-i="http://www.nltaxonomie.nl/nt18/kvk/20231213/dictionary/kvk-data"
    xmlns:nl-cd="http://www.nltaxonomie.nl/nt18/sbr/20230301/dictionary/nl-common-data"
    xmlns:rj-i="http://www.nltaxonomie.nl/nt18/rj/20231213/dictionary/rj-data"
    xmlns:jenv-bw2-dm="http://www.nltaxonomie.nl/nt18/jenv/20231213/dictionary/jenv-bw2-domains"
    xmlns:jenv-bw2-dim="http://www.nltaxonomie.nl/nt18/jenv/20231213/dictionary/jenv-bw2-axes"
    xmlns:iso4217="http://www.xbrl.org/2003/iso4217" xmlns:xbrldi="http://xbrl.org/2006/xbrldi">
    <link:schemaRef xlink:type="simple"
        xlink:href="http://www.nltaxonomie.nl/nt18/kvk/20231213/entrypoints/kvk-rpt-jaarverantwoording-2023-nlgaap-micro-publicatiestukken.xsd" />
    <xbrli:context id="c0d_0">
        <xbrli:entity>
            <xbrli:identifier scheme="http://www.kvk.nl/kvk-id">30267975</xbrli:identifier>
        </xbrli:entity>
        <xbrli:period>
            <xbrli:startDate>2023-01-01</xbrli:startDate>
            <xbrli:endDate>2023-09-30</xbrli:endDate>
        </xbrli:period>
    </xbrli:context>
    <jenv-bw2-i:BasisOfPreparation contextRef="c0d_0">Commercieel</jenv-bw2-i:BasisOfPreparation>
    <jenv-bw2-i:DocumentAdoptionDate contextRef="c0d_0">2023-10-01</jenv-bw2-i:DocumentAdoptionDate>
    <jenv-bw2-i:DocumentAdoptionStatus contextRef="c0d_0">Ja</jenv-bw2-i:DocumentAdoptionStatus>

The actual definitions of these tags can then for example the jenv-bw2-i are found at http://www.nltaxonomie.nl/nt18/jenv/20231213/dictionary/jenv-bw2-data.xsd

This example and others can be found on the website from SBR at their download page.

With regards to the file contents and the status code. I agree that one might want to verify the file contents. However, the status code should already be checked by the cache_file function. At this moment it throws an Exception, which seems fine in my opinion