Best Practices – Digital Asset Guidelines – Rev 4 www.autocare.org | www.autocarevip.com | technology@autocare.org 7 3. Digital Asset Data Delivery Best Practices 3.1 Digital Asset Data Delivery Overview The Digital Asset Data Delivery Guidelines are designed to provide the suppliers and receivers of the digital assets all the information they need to categorize and catalog the digital assets appropriately in their systems. 3.2 Digital Asset Naming Convention Defining a specification for the naming convention of digital assets that satisfies both the digital asset creator and the digital asset receiver across the entire Aftermarket industry was not plausible. However, the following guidelines should be considered when creating the digital asset file names: • The ‘Digital Asset File Name’ should only consist of alphanumeric characters o Spaces and any other special characters other than a dash or underscore should not be used o This would include special characters, codes, symbols or signs found on a standard U.S. QWERTY keyboard or those included in the ASCII or UTF-8 code references • File names should include a unique identifier for the digital asset o Minimum values might include the part name, part number and/or orientation view • File names must include the file extension e.g., .jpg, .tif, pdf, eps, aif, wav, mp3, wma, ogg, aac, pcm, ac3, midi • File naming may be case sensitive for some trading partners o Trading partners should discuss and agree on the file naming structure / format The best approach to the file naming issue was to allow digital asset creators to name the file anyway they want as long as the file name was associated to the other relevant digital asset data. This association is accomplished by entering the digital asset data in the appropriate fields of the PIES file and sending that to the receiver along with the digital assets.