File naming convention for documentation & driver_software subfolder of each product folder: ============================================================================================ fields: ------- __rev____. All fields existance is mandatory. example: -------- DFL-700_fw_revAB1C_1-33B67_all_en_20051223.zip DES-3526_fw_revA_5-01B01_all_en_20090101.zip DES-3200_fw_revA_1-50B10_all_en_20090602.zip DES-3526DC_dview_revA_5-00R11_all_en_20071024.zip DCS-3411&3430_fw_revA_1-00_all_eu5_20100101.zip DFL-800_mib_revA_2-20-03-08_all_en_20090102.zip DGS-3100-24TG_dview_revA_1-00R10_all_en_20091230.zip DCS-3110_ce_revA2_1-00_all_en_20100304.pdf DCS-3110_rohs_revB1_1-00_all_enfr_20050101.pdf DNS-323_qig_revABC_1-00_eu_eu18_20100203.pdf DWS-4000_man_revA_1-00_all_en_20090202.pdf definition: ----------- field name example description product-name DFL-700 name of the product in uppercase type type of the file in lowercase fw firmware addon-BitTorrent addon-NFS additional firmware package (for example for DNS-3x3) drv driver apmanager AP Manager modules/application dview D-View module gpl GPL source code sw other software mib Management Information Base ce CE declaration rohs RoHS declaration ds datasheet qig quick installation guide man manual cli CLI manual spec specification [...] additional types possible in regards to new file types introduced in the future revision all(!!!) product hardware revisions for which the file is valid; string "rev" in lowercase and revisions in uppercase revA if applicable to all rev. A (like for most firmwares and manuals) revA1 if applicable only to a specific rev. - like A1 (for CE, RoHS and some firmwares) revA2A3 if applicable only to A2 and A3 hardware revision revABC if applicable for all A, B and C hardware revisions revAB1C if applicable for all A revisions, B1 revision and all C revisions revNA if Not Applicable (mostly for software) please note: DO NOT use revALL - this is dangerous, as at the beginning there is only a single HW version. Later on, when new HW versions appear, all revALL need to be renamed to a proper HW version - which is mostly omitted and therefore introduces inconsistency to the file naming version software version 1-33B67 assuming that the package is for all supported operating systems 1-20B10-Vista 1-20B06-MacOS version for single operating system 1-00 for other versioned files (like CE, RoHS declarations) 00 as last resort placeholder (if really no version is available) validarea area where the file is valid all the whole world eu Europe us United States ru Russia cn China tw Taiwan de Germany pl Poland cz Czech Republic [...] for not covered areas, please use http://www.iana.org/domains/root/db/ language language version en de pl cz eu5 5-multilanguage for EU, assuming: en+de+fr+it+es eu18 18-multilanguage for EU enfr en+fr language [...] for not covered languages, please use http://www.iana.org/domains/root/db/ releasedate 20051223 date of release in: yyyymmdd extension zip - all drivers, firmwares, documentation grouped into packages pdf - documentation File naming convention for other documentation and how-to files: ================================================================ fields: ------- _howto____.pdf _doc____.pdf All fields existance is mandatory. example: -------- DFL-210_howto_en_How-to-capture-packets-on-DFL_1-00_20100201.pdf DFL-210_doc_pl_Rozdzial10-Zarzadzanie-ruchem_2-12_20090605.pdf definition: ----------- field name example description product-name DFL-700 name of the product in uppercase language en english pl polish de german file-description How-to-run-the-service name of the file - use "-" (dash) instead of space and do not use national chars version 1-00 file version - use "-" (dash) instead of "." (dot) releasedate 20051223 date of release in: yyyymmdd