Hi John, A quick 'find . -name *.xsd*' reveals:
./base/xsd/base_types.xsd ./libports/src/app/sntp_client/config.xsd ./os/src/init/config.xsd ./os/src/server/nic_dump/config.xsd ./os/src/server/nic_router/config.xsd ./os/src/server/nic_bridge/config.xsd ./os/src/app/trace_logger/config.xsd ./os/src/app/ping/config.xsd ./os/src/test/nic_stress/config.xsd ./os/src/test/net_flood/config.xsd ./os/xsd/net_types.xsd ./os/xsd/timeout_types.xsd ./gems/src/app/depot_autopilot/config.xsd We implemented support for automatic XSD checking in the run tool some time ago [1] but only a handful of components have an XSD by now. Cheers, Martin [1] https://genode.org/documentation/release-notes/18.02#Offline_validation_of_XML_configurations El 22/1/20 a las 19:37, John J. Karcher escribió > I had a small thought related to this: Are there any XSD (XML schema) > files for the configuration files? > > This would make it easier to use a generic XML editor, not to mention > custom tools or IDE plug-ins, to write these files. Considering how > regular the formats are, the resulting XSD could be very clean. > > Thanks! > > John J. Karcher > [email protected] > > _______________________________________________ > Genode users mailing list > [email protected] > https://lists.genode.org/listinfo/users _______________________________________________ Genode users mailing list [email protected] https://lists.genode.org/listinfo/users
