Identity (extensions schema for Windows 8.1)

Defines a globally unique identifier for a package. A package identity is represented as a tuple of attributes of the package.

Element hierarchy

<Package>

<Identity>

Syntax

<Identity Name                   = A string between 3 and 50 characters in length that consists of alpha-numeric, period, and dash characters.
          ProcessorArchitecture? = "x86" | "x64" | "arm" | "neutral"
          Publisher              = A string between 1 and 8192 characters in length that fits the regular expression  of a distinguished name : "(CN|L|O|OU|E|C|S|STREET|T|G|I|SN|DC|SERIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID\.(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))+))=(([^,+="<>#;])+|".*")(, ((CN|L|O|OU|E|C|S|STREET|T|G|I|SN|DC|SERIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID\.(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))+))=(([^,+="<>#;])+|".*")))*". Further, semantic validation ensures that the string is compliant with CertNameToStr Windows API implementation of X.500 rules.

          Version                = A version string in quad notation, "Major.Minor.Build.Revision".
          ResourceId?            = A string between 1 and 30 characters in length that consists of alpha-numeric, period, and dash characters. />

Key

?   optional (zero or one)

Attributes and Elements

Attributes

Child Elements

None.

Parent Elements

Remarks

The Name attribute is used by the operating system and developers to identify packages. The Name attribute is not intended to be displayed to end users.

When an app is based on different resource packages, the ResourceId attribute must be unique across the user account for a given package name. Main package variants based on resource IDs are not allowed to be installed simultaneously. However, multiple simultaneous variants of a resource-only package are allowed. Examples of possible ResoureId attributes include:

• North America
• Asia
• European Languages

The Publisher attribute is validated against the subject name of the signing certificate when signed packages are opened. If the Publisher attribute doesn't exactly match the subject name, the package is invalid. You can construct multiple semantically-equivalent string representations from the subject name that is stored in the certificate. Use these canonicalization rules to match the Publisher attribute value to that subject name:

• Unicode values can be UTF-8 encoded.

• If the name contains the legacy e-mail component, the Internationalized Domain Name (IDN) is represented in Unicode form.

• Object identifiers (OIDs) with X.500 key names must use the X.500 key name (for example, CN, not 2.5.4.3).

• OIDs without X.500 key names are identified with the "OID." prefix (for example, OID.2.5.4.34).

• OID key names are separated from their values by an equal sign without extra spaces (for example, CN=JohnSmith).

• Multiple relative distinguished name (RDN) entries are separated by a comma followed by a space (for example, CN=JohnSmith, O=Contoso).

• The RDN value has quotes around it only if it contains leading or trailing white space or one of the following characters (for example, CN=" JohnSmith", O="C++ Inc."):

  • Comma (,)
  • Plus sign (+)
  • Equal sign (=)
  • Inch mark (")
  • Backslash followed by the letter n (\n)
  • Less than sign (<)
  • Greater than sign (>)
  • Number sign (#)
  • Semicolon (;)

• The quotation character is an inch mark ("). If the RDN value contains an inch mark, the inch mark must have double quotes ("") in addition to being enclosed in quotes (for example, CN="William ""Bill"" Smith").

• Multivalued RDN are not allowed (for example, CN=JohnSmith + O=Contoso).

These rules follow the behavior of the CertNameToStr function, which can be used to determine the expected Publisher attribute value from a certificate.

Examples

The following example is taken from the package manifest of one of the SDK samples.

<Identity Name="Microsoft.SDKSamples.ApplicationDataSample" 
          Version="1.0.0.0" 
          Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />

Requirements