About Software Tagging RegIDs
AdminStudio 2024 | 27.0 | Application Manager
A software ID tag file can contain up to three different RegIDs: Tag Creator RegID, Software Creator RegID, and Software Licensor RegID. A RegID has the following format:
regid.YYYY-MM.ReversedDomainName,optional_division
For example:
regid.2009-06.com.yourcompany,GlobalProductDivision
regid.2001-09.com.ABCDcompany,AccountingSystems
regid.2005-11.com.WZYZcompany
regid.2010-02.net.1234company,WordProcessing
The following table describes the components of a RegID in more detail:
Component |
Description |
|||||||||
Type |
A software tag ID begins with the string regid. This qualifies the element as a registration ID for software identification tags. The regid string is followed by a period. |
|||||||||
Date |
Enter a date code in YYYY-MM format which is the date during which the naming entity owned the domain, such as 2009-11.
The date string is followed by a period. |
|||||||||
Naming Authority |
Enter the reversed domain name of the naming entity (person or organization) that is creating this software identification tag. For example, if your company’s domain is mycompany.com, you would enter com.mycompany after the date code. Note the following regarding the naming authority domain name:
|
|||||||||
Additional Subentity |
(Optional) Enter a string that specifies any subentity that may have its own unique naming authority, such as AccountingSystems or MarketingDepartment. For example, AdminStudio’s default RegID includes AdminStudio as a subentity of Flexera, which is the naming authority: regid.2009-06.com.flexera,AdminStudio Using this optional component enables individual business units of large software publishers to manage their own software identification tags independently. This string must be preceded by a comma. Note:With the exception of the comma prefix, the owner of the domain name can assign text following the reversed domain name as desired as long as all characters are valid for use in file names on any platform that the tag will be installed on. It is the responsibility of the naming entity to ensure that each subentity reference is unique within their organization. |