Issue 31

[Randy George <randyg@us.ibm.com>]

I have an action item to propose a resolution
to Issue 31.  Issue 31 is stated as follows: "Is the correspondence
between deploymentDescriptor and the file element defining the deployment
descriptor simply the fact that the pathname matches?" 

The current schema based on the ACS
convergence had the DeploymentDescriptor element be a URI.  In addition,
there is a File element that provides the additional attributes about the
deploymentDescriptor...including the URI.   The convention to associating
a File element to the deployment descriptor was that the URIs had to be
the same.  This convention can not be enforced by the XSD.  
Example 1 below shows this approach.

Example 1
This example has the DeploymentDescriptor
element (which is optional based on the ACS convergence).  To make
this work, the value in <DeploymentDescriptor> MUST be equal to the
value in the pathname of one of the File elements.  

<?xml version="1.0" encoding="UTF-8"?>
<spd:PackageDescriptor
        xmlns:spd="urn:oasis:names:tc:SDD:1:0:packageDescriptor"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:oasis:names:tc:SDD:1:0:packageDescriptor
spd.xsd"
        schemaVersion="1.0"
        size="12345"
        descriptorID="31111111111111111111111111111111"
        buildID="PTP-Build-241"
        buildDate="2006-06-10T12:00:00">
    <PackageIdentity
softwareID="123456789">
        <Name>PersonalTaxProgram</Name>
        <Version>1.0</Version>
        <DisplayName
default="My Personal Tax program" key="PI_1" />
        <Description
default="This software enables one to better manage their 2006 federal
income taxes.  It includes support for electronic filing." key="PI_2"
/>
        <Manufacturer>
         
      <DisplayName default="Tax Company"
key="MFG_1"/>
         
      <Location>
         
              <Address>
         
               
      <DisplayName default="Washington,
DC" key="MFG_2"/>
         
              </Address>
         
      </Location>
        </Manufacturer>
    </PackageIdentity>
    <Files>
        <File
pathname="/files/DeploymentData.xml" purpose="DeploymentDescriptor"
/>
        <File
pathname="setup.exe" length="1234567890" />
    </Files>
    <DeploymentDescriptor>/files/DeploymentData.xml</DeploymentDescriptor>
</spd:PackageDescriptor> 



The proposal is to remove the DeploymentDescriptor
element from the PackageDescriptor and just rely on requiring a File element
with a purpose of "deploymentDescriptor".  In this case,
the file purpose attribute is used to determine if there is a deployment
descriptor.   BTW, this same pattern can actually be used with the
above XSD files since the <DeploymentDescriptor> element is optional.
 Rather than "supporting 2 patterns" with the XSD, I recommend
that we remove the extraneous DeploymentDescriptor element and rely on
the File purpose attribute.   This approach is more consistent with
ACS.

Example 2
<?xml version="1.0" encoding="UTF-8"?>
<spd:PackageDescriptor
        xmlns:spd="urn:oasis:names:tc:SDD:1:0:packageDescriptor"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:oasis:names:tc:SDD:1:0:packageDescriptor
spd.xsd"
        schemaVersion="1.0"
        size="12345"
        descriptorID="31111111111111111111111111111111"
        buildID="PTP-Build-241"
        buildDate="2006-06-10T12:00:00">
    <PackageIdentity
softwareID="123456789">
        <Name>PersonalTaxProgram</Name>
        <Version>1.0</Version>
        <DisplayName
default="My Personal Tax program" key="PI_1" />
        <Description
default="This software enables one to better manage their 2006 federal
income taxes.  It includes support for electronic filing." key="PI_2"
/>
        <Manufacturer>
         
      <DisplayName default="Tax Company"
key="MFG_1"/>
         
      <Location>
         
              <Address>
         
               
      <DisplayName default="Washington,
DC" key="MFG_2"/>
         
              </Address>
         
      </Location>
        </Manufacturer>
    </PackageIdentity>
    <Files>
        <File
pathname="DeploymentData.xml" purpose="DeploymentDescriptor"
/>
        <File
pathname="setup.exe" length="1234567890" />
    </Files>
</spd:PackageDescriptor> 

Regards,
Randy George

Senior Technical Staff Member
Provisioning Architecture
Tivoli Software, IBM Software Group
Austin, TX  
(512) 838-0752     T/L 678-0752