Closed Guerout-Arnaud closed 1 year ago
Microsoft tool is using XML schema 1.0 while ONVIF uses 1.1. Unfortunately we are not aware of any switch to tell it to use XML schema version 1.1
Luckily you can safely ignore this kind of errors since the tool still creates correct code.
Hi Hans. Thanks for your informations. I'll try it and close this issue if i don't have anything else related.
Hi @HansBusch.
I still have some issue with the wsdl beiing written in xml 1.1.
The first thing is that the file is tagged as xml 1.0 and not 1.1.
Even if the file was correctly tagged, i haven't been able to find any XML 1.1 compliant library.
Would it be possible to have xml 1.0 compliant wsdl ? Or is there any way to modify the current wsld to make them 1.0 compllant (without breaking the license) ?
Thanks by advance
Please refer to https://www.w3.org/TR/xmlschema11-1/ for the rationale why both 1.1 and 1.0 use the same schema url.
XML 1.0 has a serious extensibility issue that has been fixed with 1.1. For that reason ONVIF has switched to XML 1.1 many years ago.
Hi, sorry to bother. I'm facing some issues importing devicemgmt.wsdl into a project into Visual Studio.
I've just created a new ConsoleApp (C#) to experiment a bit with the protocol and see what's possible to do with it yet the import of the wsdl fails. To import the file I follow these few steps :
Go
In the
Status
output i get the following :Warning: One or more errors occurred. (details)
Theses error mostly occurs in onvif.xsd and common,xsd and are due to
##any
being used concurrently with optional parameters.Is there anything I can do on my side to fix these errors ? If I can't do anything, would it be possible to fix these errors please ? Thanks by advance