Change Details

In T1962, the possibility of storing the component syntax version within the XML file was introduced. It has remained underadvertised and underused due to a question of convenience: the mapping component <~~> interface definition file is not 1-to-1, nor should it be (for example system <~> system-*.xml.in; interface <~> interface-*.xml.in). This raises the question of in which file to include the XML syntax version element, so as to be least burdensome on the developer. In this task, we will revisit the matter, so as to finally move the component syntax version out of vyatta-cfg-system.

In T1962, the possibility of storing the component syntax version within the XML file was introduced. It has remained underadvertised and underused due to a question of convenience: the mapping component <~~> interface definition file is not 1-to-1, nor should it be (for example system <~> system-*.xml.in; interfaces <~> interface-*.xml.in). This raises the question of in which file to include the XML syntax version element, so as to be least burdensome on the developer. In this task, we will revisit the matter, so as to finally move the component syntax version out of vyatta-cfg-system.

In T1962, the possibility of storing the component syntax version within the XML file was introduced. It has remained underadvertised and underused due to a question of convenience: the mapping component <~~> interface definition file is not 1-to-1, nor should it be (for example system <~> system-*.xml.in; interfaces <~> interface-*.xml.in). This raises the question of in which file to include the XML syntax version element, so as to be least burdensome on the developer. In this task, we will revisit the matter, so as to finally move the component syntax version out of vyatta-cfg-system.