The root element is not declared

Hello everybody,
I introduced xmlNotepad and the resulting file contains this:

<?xml version="1.0"?>
<root>
  <Prepare time="15d" />
  <Develop time="1y" />
  <Promote />
</root>

Everything works OK, but the status bar tells me that the root element is not declared.

So I created a file FirstTry.xsd, with this contents:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <xs:element name="root"/>
</xs:schema>

As soon as this file was selected in View / Schema, the mention disappeared, so problem solved, but is it admitted to put the schema in the xml file, as done for instance in the basket.xml sample?

<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
 <xs:element name="root"/>
</xs:schema>
<root>
  <Prepare time="15j" />
  <Develop time="1y" />
  <Promote />
</root>

Anyway xmlNotepad stops to claim for undeclared element only once the xsd file is selected in View / Schema.

Well, once done, with this sample we learn that the basket element cannot contain text, perhaps that is another topic.

By the way, I notice that by default this error span in the status bar is the only element in the user interface that appears in French. Perhaps because .Net is installed in French?

Perhaps I should open another thread for this: it would be very handy that the tool be able to generate an xsd file.

Did I make a mistake? The code is much easier to read if the line-feeds are executed. By default the "Code" button of the forum generates a tick before and one after, I then tripled the ticks manually to respect the line-feeds. Oh, and I notice the triple tick at the end has to be on a separate line, otherwise the following paragraphs appear on one line each, which is not necessarily the most readable. And same for the triple tick at the beginning, otherwise the first line of code is lost.

Reproduce the report in XML Notepad using the inline XML/XSD sample and the separate FirstTry.xsd selected through View / Schema. The issue does not name an implementation file, test, or single expected change; clarify whether the target is schema association, inline-schema handling, localization, or XSD generation before defining done criteria.