A computer apparatus receives seed characters relating to an object and accesses rules to generate an identifier. The identifier includes a human-readable component that conveys understanding to a non-skilled user. The identifier complies with limitations dictated by the rules and is not based on random generation. |
Citations|
| US5535375 | Oct 11, 1994 | Jul 9, 1996 | International Business Machines Corporation | File manager for files shared by heterogeneous clients | | US5864862 | Sep 30, 1996 | Jan 26, 1999 | Telefonaktiebolaget LM Ericsson (publ) | System and method for creating reusable components in an object-oriented programming environment | | US5963646 | Dec 28, 1998 | Oct 5, 1999 | The PACid Group | Secure deterministic encryption key generator system and method | | US6249782 | Dec 17, 1998 | Jun 19, 2001 | Apple Computer, Inc. | System and method for reducing file name length and for retrieving the reduced file name entitled files | | US6532481 | Mar 31, 2000 | Mar 11, 2003 | | Product identifier, catalog and locator system and method | | US6539396 | Aug 31, 1999 | Mar 25, 2003 | Accenture LLP | Multi-object identifier system and method for information service pattern environment | | US6591415 | Apr 25, 2000 | Jul 8, 2003 | Trymedia Systems | Polymorphic code generation method and system therefor | | US6675382 | Jun 14, 1999 | Jan 6, 2004 | Sun Microsystems, Inc. | Software packaging and distribution system | | US6804700 | Oct 4, 2000 | Oct 12, 2004 | Microsoft Corporation | Methods and systems for assigning human-readable and unique uniform resource locators to objects | | US6857053 | Apr 10, 2002 | Feb 15, 2005 | International Business Machines Corporation | Method, system, and program for backing up objects by creating groups of objects | | US6970892 | Feb 16, 2001 | Nov 29, 2005 | Stratus Technologies Bermuda LTD | Implementing standards-based file operations in proprietary operating systems | | US7080371 | Sep 1, 2000 | Jul 18, 2006 | Siebel Systems, Inc. | Method, system, apparatus and program product for distribution and instantiation of software upgrades | | US7086052 | Jan 3, 2003 | Aug 1, 2006 | Hewlett-Packard Development Company, L.P. | Software installation and operation with random selection | | US7315854 | Oct 25, 2004 | Jan 1, 2008 | International Business Machines Corporation | Distributed directory replication | | US7352867 | Jul 10, 2002 | Apr 1, 2008 | General Instrument Corporation | Method of preventing unauthorized distribution and use of electronic keys using a key seed | | US7783677 | Sep 10, 2007 | Aug 24, 2010 | Microsoft Corporation | Tracking file system namespace changes during transactions | | US20020156767 | Apr 12, 2002 | | | Method and service for storing records containing executable objects | | US20040002991 | Jun 28, 2002 | | Microsoft Corporation | System and method for associating properties with objects | | US20040008846 | Jul 10, 2002 | | | Method of preventing unauthorized distribution and use of electronic keys using a key seed | | US20040252198 | Jun 21, 2004 | | Canon Kabushiki Kaisha | File management system of image data | | US20050010794 | Jul 19, 2004 | | | Content addressable information encapsulation, representation, and transfer | | US20050267982 | Aug 9, 2005 | | Hitachi, Ltd. | Method for accessing distributed file system | | US20060020578 | Jul 21, 2004 | | Rockwell Software, Inc. | Time stamp methods for unified plant model | | US20060085402 | Oct 20, 2004 | | Microsoft Corporation | Using permanent identifiers in documents for change management |
Claims1. A method for generating identifiers for installation package files, the method being performed by a computing system comprising at least one processor, the method comprising: - during a first build of an installation package:
- receiving first seed characters associated with a first file to be included in the first build of the installation package;
- applying rules to the first seed characters to create a unique, reproducible first file code for the first file, wherein:
- the rules, when applied to subsequent seed characters identical to the first seed characters, are configured to reproduce a subsequent file code identical to the first file code
- the rules are configured to create a different file code for each different set of seed characters;
- receiving second seed characters associated with a first set of files to be included in the first build of the installation package, the first set of files comprising the first file;
- applying the rules to the second seed characters to create a unique, reproducible first component code for the first set of files;
- during a second build of the installation package:
- receiving the subsequent seed characters associated with the first file;
- applying the rules to the subsequent seed characters associated with the first file to create the subsequent file code that is identical to the first file code:
- wherein:
- the first component code is related to the first file code;
- the relationship between the first component code and the first file code enables a product included in the first build of the installation package to be accessible by a product included in the second build of the installation package.
2. The method of claim 1, wherein: - the rules, when applied to subsequent seed characters identical to the second seed characters, are configured to reproduce a subsequent component code identical to the first component code;
- the rules are configured to create a different component code for each different set of seed characters;
the method further comprising: - during the second build of the installation package:
- receiving the subsequent seed characters associated with the first set of files;
- applying the rules to the subsequent seed characters associated with the first set of files to create the subsequent component code that is identical to the first component code.
3. The method of claim 1, further comprising: - during the first build of the installation package:
- receiving third seed characters associated with a second file to be included in the first build of the installation package;
- applying the rules to the third seed characters to create a unique, reproducible second file code for the second file, wherein:
- the rules, when applied to subsequent seed characters identical to the third seed characters, are configured to reproduce a subsequent file code identical to the second file code;
- the second file code is different than the first file code;
- during the second build of the installation package:
- receiving the subsequent seed characters associated with the second file;
- applying the rules to the subsequent seed characters associated with the second file to create the subsequent file code that is identical to the second file code.
4. The method of claim 1, further comprising: - during the first build of the installation package:
- receiving third seed characters associated with a second file to be included in the first build of the installation package;
- applying the rules to the third seed characters to create a unique, reproducible second file code for the second file, wherein:
- the rules, when applied to subsequent seed characters identical to the third seed characters, are configured to reproduce a subsequent file code identical to the second file code;
- the second file code is different than the first file code;
- the first set of files comprises the first and second files;
- during the second build of the installation package:
- receiving the subsequent seed characters associated with the second file;
- applying the rules to the subsequent seed characters associated with the second file to create the subsequent file code that is identical to the second file code.
5. The method of claim 1, further comprising: - processing the first seed characters to generate a human-readable component;
- inserting the human-readable component into the first file code.
6. The method of claim 1, further comprising: - processing the first seed characters to generate a human-readable component and a non-readable component based on the rules;
- applying the rules to determine placement of the human-readable component relative to the non-readable component; and
- inserting the human-readable and non-readable components into the first file code.
7. The method of claim 1, further comprising: - identifying contextual constraints of the first file code, wherein applying the rules comprises applying the contextual constraints.
8. The method of claim 7, wherein the contextual constrains comprise at least one of: - a minimum length limitation;
- a maximum length limitation.
9. The method of claim 1, wherein the second build of the installation package comprises an upgrade of the first build of the installation package. 10. The method of claim 1, wherein the installation package comprises an electronically-packaged computer-program product. 11. A system comprising: - an identifier module programmed to:
- during a first build of an installation package:
- receive first seed characters associated with a first file to be included in the first build of the installation package;
- apply rules to the first seed characters to create a unique, reproducible first file code for the first file, wherein:
- the rules, when applied to subsequent seed characters identical to the first seed characters, are configured to reproduce a subsequent file code identical to the first file code;
- the rules are configured to create a different file code for each different set of seed characters;
- receive second seed characters associated with a first set of files to be included in the first build of the installation package, the first set of files comprising the first file;
- apply the rules to the second seed characters to create a unique, reproducible first component code for the first set of files;
- during a second build of the installation package:
- receive the subsequent seed characters associated with the first file;
- apply the rules to the subsequent seed characters associated with the first file to create the subsequent file code that is identical to the first file code;
- memory configured to store instructions of the identifier module;
- a processor in communication with the memory and configured to:
- receiving the instructions from the memory as an instruction stream;
- execute the instructions;
- wherein:
- the first component code is related to the first file code;
- the relationship between the first component code and the first file code enables a product included in the first build of the installation package to be accessible by a product included in the second build of the installation package.
12. The system of claim 11, wherein: - the rules, when applied to subsequent seed characters identical to the second seed characters, are configured to reproduce a subsequent component code identical to the first component code;
- the rules are configured to create a different component code for each different set of seed characters;
- the identifier module is further programmed to:
- during the second build of the installation package:
- receive the subsequent seed characters associated with the first set of files;
- apply the rules to the subsequent seed characters associated with the first set of files to create the subsequent component code that is identical to the first component code.
13. The system of claim 11, wherein the identifier module is further programmed to: - during the first build of the installation package:
- receive third seed characters associated with a second file to be included in the first build of the installation package;
- apply the rules to the third seed characters to create a unique, reproducible second file code for the second file, wherein:
- the rules, when applied to subsequent seed characters identical to the third seed characters, are configured to reproduce a subsequent file code identical to the second file code;
- the second file code is different than the first file code;
- during the second build of the installation package:
- receive the subsequent seed characters associated with the second file;
- apply the rules to the subsequent seed characters associated with the second file to create the subsequent file code that is identical to the second file code.
14. The system of claim 11, wherein the identifier module is further programmed to: - during the first build of the installation package:
- receive third seed characters associated with a second file to be included in the first build of the installation package;
- apply the rules to the third seed characters to create a unique, reproducible second file code for the second file, wherein:
- the rules, when applied to subsequent seed characters identical to the third seed characters, are configured to reproduce a subsequent file code identical to the second file code;
- the second file code is different than the first file code;
- the first set of files comprises the first and second files;
- during the second build of the installation package:
- receiving the subsequent seed characters associated with the second file;
- applying the rules to the subsequent seed characters associated with the second file to create the subsequent file code that is identical to the second file code.
15. A computer-readable-storage medium comprising instructions thereon that program a computer to perform the following: - during a first build of an installation package:
- receive first seed characters associated with a first file to be included in the first build of the installation package;
- apply rules to the first seed characters to create a unique, reproducible first file code for the first file, wherein:
- the rules, when applied to subsequent seed characters identical to the first seed characters, are configured to reproduce a subsequent file code identical to the first file code;
- the rules are configured to create a different file code for each different set of seed characters;
- receive second seed characters associated with a first set of files to be included in the first build of the installation package, the first set of files comprising the first file;
- apply the rules to the second seed characters to create a unique, reproducible first component code for the first set of files;
- during a second build of the installation package:
- receive the subsequent seed characters associated with the first file;
- apply the rules to the subsequent seed characters associated with the first file to create the subsequent file code that is identical to the first file code;
- wherein:
- the first component code is related to the first file code;
- the relationship between the first component code and the first file code enables a product included in the first build of the installation package to be accessible by a product included in the second build of the installation package.
16. The computer-readable-storage medium of claim 15, wherein: - the rules, when applied to subsequent seed characters identical to the second seed characters, are configured to reproduce a subsequent component code identical to the first component code;
- the rules are configured to create a different component code for each different set of seed characters;
- during the second build of the installation package:
- receive the subsequent seed characters associated with the first set of files;
- apply the rules to the subsequent seed characters associated with the first set of files to create the subsequent component code that is identical to the first component code.
17. The computer-readable-storage medium of claim 15, further comprising instructions that program the computer to perform the following: - during the first build of the installation package:
- receive third seed characters associated with a second file to be included in the first build of the installation package;
- apply the rules to the third seed characters to create a unique, reproducible second file code for the second file, wherein:
- the rules, when applied to subsequent seed characters identical to the third seed characters, are configured to reproduce a subsequent file code identical to the second file code;
- the second file code is different than the first file code;
- during the second build of the installation package:
- receive the subsequent seed characters associated with the second file;
- apply the rules to the subsequent seed characters associated with the second file to create the subsequent file code that is identical to the second file code.
|
