Description of problem:

Say we have Template-A and we create another Template as a sub-template of Template-A. the new template inherits the name of the base template and can be given a sub-template name.
The new sub-template has a <version> attribute which holds <version_number>, <version_name> and a link to the base template.
On the other hand the Base template doesn't have a <version> attribute, whereas in DB it does have a template_version_number = 1 (the 1st subversion is 2 and so on..).
I think we should have a unity in the way we represent templates and therefore I think every template should have a <version> tag with <version_number>1</version_number> under it.

This isn't a crucial problem but it did in fact raise a problem in automation e.g. where a find request tried to check if a template is of version x , and got a NoneType when tried to derive the version attribute of the Base template.
while this is a small bug that can be handled inside our automation code,  I still expect a unity between the templates entities to prevent other small bugs like this.

Version-Release number of selected component (if applicable):
rhevm-3.6.0.3-0.1.el6.noarch

How reproducible:
always.

Steps to Reproduce:
1. Create template.
2. Create a template as sub template of the previous template.
3. call GET to look at both template's attributes.

Actual results:

Base template has no <version> attribute

Expected results:

Base template has <version> attribute
Additional info: