Separate instructions for testing well formed XML files and validation against DTD

[ejgutierrez74]

Related to #943 , #945

Would it possible to make two different instructions: one to test if a xml file is well formed and other to validate it against DTD file. Thats the way XML copy editor works, and many online validators.

Or at least in problems output, make a clear difference ( ideally separated by horizontal line or something like that ) between the xml file ( errors of not well formed file) and errors that came from DTD ( from validation of the xml file against DTD). Because mixing the two diferent source of errors, would be some kind of mess....specially to my students.

As @angelozerr asked me, i open a issue to separate, the bug from this feature request or enchancement.

The validation check is performed against any XML schema or DTD declared inside the XML document.
If neither an XML schema nor a DTD is declared, only a syntax check is performed.

Another example:
https://www.liquid-technologies.com/online-xml-validator

But in this case it misses the XML vs DTD validator...

My students and me were very grateful.... ;)

[angelozerr]

Would it possible to make two different instructions: one to test if a xml file is well formed and other to validate it against DTD file.

If I understand your need you would like to validate:

• only XML syntax
• XML syntax + errors coming from DTD rules
• XML syntax + errors coming from XSD rules

with separate commands?

To learn XML I can understand the need but it requires some work.

I think the thing that you want is to distinguish the erros (Syntax, errors coming from DTD rules, etc). A thing that we can try is to use the source information of the reported diagnostic. Today source is xml:

which is not relevant. We could have:

• XML.Syntax: XML errors syntax
• XML.DTD : XML errors coming from DTD rules
• DTD.Syntax: DTD errors syntax (when you open the DTD)
• ...

After that you could use filter from the Problems vscode view

You can click on view as table

you could see better the code:

What do you think about this idea?

[angelozerr]

My students and me were very grateful.... ;)

Glad vscode-xml please you :)

[ejgutierrez74]

F

Would it possible to make two different instructions: one to test if a xml file is well formed and other to validate it against DTD file.

If I understand your need you would like to validate:

* only XML syntax

* XML syntax + errors coming from DTD rules

* XML syntax + errors coming from XSD rules

with separate commands?

To learn XML I can understand the need but it requires some work.

For example XML Copy Editor has two instructions/commands : one to test if an xml file is well formed and other to test if is valid against a DTD.

This is an example:

As you can see, is in spanish but dont difficult to understand:
F2 Check xml file is well formed
F5 Check if is valid against DTD

Also there is the online resource i told you https://www.xmlvalidation.com/ that does the work this way...separating things.

About checking if a DTD file is correct, i havent seen any place to test it. I found the DTD language grammar, but dont know any online or software resource that checks it ( i havent tested any payment software have to say). So If its included ok, but for me/students not strictly necessary.

[ejgutierrez74]

I think the thing that you want is to distinguish the erros (Syntax, errors coming from DTD rules, etc). A thing that we can try is to use the source information of the reported diagnostic. Today source is xml:

which is not relevant. We could have:

* XML.Syntax: XML errors syntax

* XML.DTD : XML errors coming from DTD rules

* DTD.Syntax: DTD errors syntax (when you open the DTD)

* ...

After that you could use filter from the Problems vscode view

You can click on view as table

you could see better the code:

What do you think about this idea?

Id have to try when new pre-release is out with my students..but as said in previous post, not the best solution for me, but better than the one we have now.

Dont know the work it requires, but many resources do this way, so i suppose is not a very complicated solution.

[angelozerr]

F5 Check if is valid against DTD

This command exists with Revalidate current XML file command.

F2 Check xml file is well formed

We should provides a new command Revalidate only XML syntax from the current XML file

About checking if a DTD file is correct, i havent seen any place to test it.

vscode-xml provides a DTD validator, no?

Id have to try when new pre-release is out with my students..but as said in previous post, not the best solution for me, but better than the one we have now

For the moment there are nothing about that, the screenshot is the current version. My idea is to replace xml with XML.Syntax, XML.DTD and after that you could use filter. This problem view comes from vscode and there are no way to customize it.

[ejgutierrez74]

F5 Check if is valid against DTD

This command exists with Revalidate current XML file command.

Then id suggest to change the name of the command because its a little confusing. Term revalidate is confusing and "xml file" suggests that you are validating again a file against whatever ( dont know) but xml file suggests some xml file validation...
So id feel more comfortable with something like Check valid against DTD and other order or command Check valid against XSD.

F2 Check xml file is well formed

We should provides a new command Revalidate only XML syntax from the current XML file

Then id suggest to change the name of the command because its a little confusing....i suppose for people with other mother language different than english. In my opinion should be Check xml file is well-formed ( as XML Copy Editor and other validators has). It confuses with validation against a DTD or XSD file. Id put Check well formed or Check XML file is well formed.

About checking if a DTD file is correct, i havent seen any place to test it.

vscode-xml provides a DTD validator, no?

If it has i dont know...how can you test if a DTD file syntax is correct or not ?
As said i dont know any software or online application that does that.

Id have to try when new pre-release is out with my students..but as said in previous post, not the best solution for me, but better than the one we have now

For the moment there are nothing about that, the screenshot is the current version. My idea is to replace xml with XML.Syntax, XML.DTD and after that you could use filter. This problem view comes from vscode and there are no way to customize it.

Perhaps if we divide into different commands as mentioned would be easier for me/my students and general people. And dont get a mixed problems console.

If I understand your need you would like to validate:

only XML syntax
XML syntax + errors coming from DTD rules
XML syntax + errors coming from XSD rules

with separate commands?

Yes if not would be confusing specially with noobs or people beginning to learn xml, dtd, xsd...
Then in the future would come to check against XSLT ;)

[angelozerr]

Then id suggest to change the name of the command because its a little confusing. Term revalidate is confusing and "xml file" suggests that you are validating again a file against whatever ( dont know) but xml file suggests some xml file validation...
So id feel more comfortable with something like Check valid against DTD and other order or command Check valid against XSD.

Having several command will be hard (or require some more work) because vscode doesn't know that XML is bound to an XSD, DTD, etc, so we should keep one command like Check valid against DTD/XSD/RelaxNG.

@fbricon @datho7561 what do you think about this suggestion?

Then id suggest to change the name of the command because its a little confusing....i suppose for people with other mother language different than english. In my opinion should be Check xml file is well-formed ( as XML Copy Editor and other validators has). It confuses with validation against a DTD or XSD file. Id put Check well formed or Check XML file is well formed.

@fbricon @datho7561 what do you think about this suggestion?

If it has i dont know...how can you test if a DTD file syntax is correct or not ?

Open DTD file and you will see errors (or the first error).

Perhaps if we divide into different commands as mentioned would be easier for me/my students and general people. And dont get a mixed problems console.

Ok