The xsi:schemaLocation and xsi:noNamespaceSchemaLocation attributes can be used in a document to provide hints as to the physical location of schema documents which may be used for ·assessment·. See How schema definitions are located on the Web (§4.3.2) for details on the use of these attributes.
Maybe this will help you. I add xdto package with Namespace Uri "http://www.w3.org/2001/XMLSchema-instance" and then create type in DataProcessor1 at Server Procedure. see my example.
Thanks for the tip, but there are two problems: 1) schemaLocation this is attribute. The suggested option - complex Type in XML. 2) But even if the schemaLocation a simple type, then this Namespace ("http://www.w3.org/2001/XMLSchema-instance") import in other XDTO package and 1С platform output does so:
Sets an attribute value. If the attribute with the specified name does not exist in the element, it is created and set to the specified value. Otherwise, the attribute value is changed. The attribute value is not parsed while it is set
If the attribute name contains characters incompatible with XML standard of this document, or the node is read-only, an exception is triggered.
Alexey, unfortunately it is not possible to set schemaLocation using XDTO package. I can suggest you to use the solution provided by Xin Wang or process the resulting file, generated with usage of XDTOPackage and containing no schemaLocation, using XMLReader and XMLWriter to add schemaLocation where it is needed.
If you can give reasons that support of schemaLocation is critical for you and other users, I will send your request to our developers.
Timofey Bugaevsky wrote: If you can give reasons that support of schemaLocation is critical for you and other users, I will send your request to our developers.
1.2.28. Instance document must use the same namespace prefixes as used in the XBRL schemas or conformance suite instances together with the recommended default namespace prefix for all namespaces.
Below is a list of XBRL schemas for the core document files that are supported by disclosure systems following Global Filing Manual (e.g. instance, linkbase, XLink documents). The namespace that represents each document must be used in the form as shown. A recommended prefix that represents each namespace is provided. The location of the actual schema file is also identified.
Really we also feel lack of functionality (flexibility) of XDTO. We had to stop using it because we have not find a solution to implement what we needed. Please listen to us and add flexibility to prefixes.