#55: XML Schema Definition for LNST Recipe Syntax ----------------------+------------------ Reporter: rpazdera | Owner: Type: task | Status: new Priority: major | Milestone: Component: lnst-ctl | Version: Keywords: | Blocked By: Blocking: | ----------------------+------------------ It would be great if we had a scheme definition for recipes and machine configs. It could be used for preliminary validation. Also VIM >= 7 should support syntax checking and even completion based on this definitions!
#55: XML Schema Definition for LNST Recipe Syntax -----------------------+---------------------- Reporter: rpazdera | Owner: olichtne Type: task | Status: new Priority: major | Milestone: Component: lnst-ctl | Version: Resolution: | Keywords: Blocked By: | Blocking: -----------------------+---------------------- Changes (by rpazdera):
* owner: => olichtne
#55: XML Schema Definition for LNST Recipe Syntax -----------------------+---------------------- Reporter: rpazdera | Owner: olichtne Type: task | Status: new Priority: major | Milestone: Component: lnst-ctl | Version: Resolution: | Keywords: Blocked By: | Blocking: -----------------------+----------------------
Comment (by olichtne):
Schema and DTD draft, along with a description of potential problems is available here:
https://lists.fedorahosted.org/pipermail/lnst- developers/2013-April/001164.html
#55: XML Schema Definition for LNST Recipe Syntax -----------------------+---------------------- Reporter: rpazdera | Owner: olichtne Type: task | Status: assigned Priority: major | Milestone: Component: lnst-ctl | Version: Resolution: | Keywords: Blocked By: | Blocking: -----------------------+---------------------- Changes (by olichtne):
* status: new => assigned
Comment:
The problems with the XML Schema resulted in us creating the RelaxNG schema instead. The new rng schema is available here:
https://lists.fedorahosted.org/pipermail/lnst- developers/2013-May/001216.html
You can try to validate your recipe with this schema by using the script from Jan that's available here:
https://lists.fedorahosted.org/pipermail/lnst- developers/2013-May/001198.html
The only limitation that this now has is the usage of the source attribute which it can detect and accept but it will not recursively validate the referenced files.
My suggestion would be to use XInclude instead which can be easily parsed by for example the lxml parser, and validated afterwards. This will however require a rewrite of our current parser so it's a potential future feature.
#55: XML Schema Definition for LNST Recipe Syntax -----------------------+---------------------- Reporter: rpazdera | Owner: olichtne Type: task | Status: closed Priority: major | Milestone: Component: lnst-ctl | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: -----------------------+---------------------- Changes (by rpazdera):
* resolution: => fixed * status: assigned => closed
lnst-developers@lists.fedorahosted.org