• Some element may appear twice on the same page.
• The parents of attributes that are defined as an attribute group are not listed.
• An extra comma appears at the end of lists.
• Schema diagrams are generic.
• At present, there is a bug in the Firefox rendition which causes a ‘null’ error to appear on the screen. The workaround is to click ‘history back’ and reselect the element to display.

These will be rectified in a future release.

• Approved browsers:
• • Firefox
  • Microsoft Edge
  • Google Chrome
• Browsers with issues:
• • n/a
• Non-functional browsers:
• • Microsoft Internet Explorer

Local files from the same directory and subdirectories were historically treated as being from the same origin. This meant that a file and all its resources could be loaded from a local directory or subdirectory during testing, without triggering a CORS error.

Unfortunately this had security implication. Many browsers, including Firefox and Chrome, now treat all local files as having opaque origins (by default). As a result, loading a local file with included local resources will now result in CORS errors.

Users who want to use the Data Dictionary locally now need to set up a local server. As all files are served from the same scheme and domain (localhost) they all have the same origin, and do not trigger cross-origin errors.

You can find a a simple guide for getting a local web server set up on GitHub or by asking your preferred Web Search Engine.

On Windows systems you may enable Internet Information Services