RELAX NG schema of PVC aspect

This aspect allows declaring content processing method for applications utilizing Parallels Virtual Containers technology. This aspect uses the http://apstandard.com/ns/1/pvc XML namespace.

<content xmlns:pvc="http://apstandard.com/ns/1/pvc">
  <pvc:templates class="std-win">
    <pvc:template path="pvc/application-template-0.1.12.efd">
      <pvc:checksum algorithm="MD5">
        8f199aebac0036c0c1fa2304eecc3d54
      </pvc:checksum>
    </pvc:template>
    <pvc:template path="pvc/webserver-template-2.3.efd">
      <pvc:checksum algorithm="MD5">
        c82ba28cb60b69c6a9c12334fd147c55
      </pvc:checksum>
    </pvc:template>
  </pvc:templates>
</content>

The example above describes that the application files are resided in PVC templates application-template-0.1.12.efd and webserver-template-2.3.efd placed in the pvc/ directory within package archive.

This processing method instructs Controller to install the specified templates into available environment, following the usual templates installation procedure. Upgrade and removal of template also conform to usual PVC template update procedure.

If the targeted environment already contains specified templates, installation MUST be aborted. Upon removal of application, all the application templates MUST be uninstalled.

PVC templates may be embedded directly into APS package, or referenced as external source. When embedded into APS package, they must be specified with the path attribute pointing to the exact location of template file in application archive. It is possible to reference template available externally. For this, either an exact downloadable URL of the template must be specified with the url attribute, or a full filename with extension of the template file must be stated by the filename attribute. In the latter case, Controller should search available template repositories in order to find template with the given name. If such template cannot be found, installation must be aborted.

In order to help Controller to recognize exact format of PVC template type, it may be specified with the class attribute. The following types of PVC templates are predefined:

Controller must treat unknown template type as unspecified.

A PVC template may contain application files and directories, as well as APS metadata elements. In this case it is allowed to declare location of application files on filesystem after template installation with help of archive-root element. When specified, this element defines path to the directory which contains the application files after templates installation. This directory MUST be used by Controller if the specified files are not found in application archive. A Controller MUST prefer files existing in application archive to files from exported root. The value of the path attribute of this element MUST be an absolute path which is owned by one of the specified PVC templates.

A Package SHOULD have metadata elements necessary for displaying information about the Package in archive. Therefore a Package MUST have APP-META.xml in the root of archive.

<content xmlns:pvc="http://apstandard.com/ns/1/pvc">
  <pvc:templates class="std-win">
    <pvc:archive-root path="C:\Program Files\Broobmla\Broombla-13"/>
    <pvc:template path="broombla-template-13.0.efd">
      <pvc:checksum algorithm="MD5">
        7bbf7634cea0cafa80c9255ab87d9ee6
      </pvc:checksum>
    </pvc:template>
  </pvc:templates>
</content>
...
<service id="vhost">
  <provision>
    <url-mapping>
      <mapping url="/" path="htdocs"/>
    </url-mappling>
  </provision>
</service>

When processing URL Mapping of the example above, Controller MUST firstly lookup mapping/@path content in the htdocs directory of application archive, and if it is not presented there - read it from C:\Program Files\Broobmla\Broombla-13\htdocs\ directory of the filesystem.