1. Overview of Mini-Edit and other Tools Access DB Oracle DB You Need to Send Entries From Your Std To the Registry You Need to Get Back Updated Entries From the Registry To use in Your Std This Presentation shows how the various tools are used to help you do this and keep your records in order.

2. Making a standard, the old way, the new way Access DB The Old Way: 4 different set of final data The New Way: Common Data = Common Outputs Flat File To Registry ASN.1 Output Formatted Standard in Word Consensus Process Access DB Flat File To Registry ASN.1 Output Formatted Standard in Word Consensus Process XML Output

3. Mini Edit is a tool make this easier Access DB Oracle DB IEEE Registry Mini Edit As a steward you edit and manage records as well as produce standards and other products with the same information You also load your work to the registry, sync with others, and use the results in your own work The Registry World The SDO World

4. How are the two approaches different? The Mini Edit tool  One user / One Record per entry  Each data concept (DE,MSG) has only one entry which is always the most current one and all edits go to this record. (prior versions lost)  Typically a single standard per file  At any given time you can get the most current data (and only the current data).  When a standard is adopted, the then current DB is kept static to preserve it.  Updates take place on a new database, eventually being balloted and adopted The Registry tool  Multiple Users / Multiple Records per entry  Many entries for each data concept, each reflecting a point in time and keeping all prior data in a revision history  All standards in ITS are a kept in one file  At any given moment in time you can get the most current or a past set of data entries  AND: The ability to extract prior sets of data is how a configuration baseline between standards is maintained.  New updates cause a new record, which must be sent to the SDO to adopt.

5. Interaction with The Registry is fairly simple A simple file type is used to upload things Some people prefer interactive data loading A simple file can be exported [I am ignoring the many minor errors still present in this] Flat File Oracle DB Multiple Past Records Flat File Reports Web Editing Batch Editing IEEE Registry

6. A number of File Formats Can be produced by this, all with the same base data Access DB Flat File XML Output ASN.1 Output Oracle DB Multiple Past Records Flat File Reports Web Editing Batch Editing IEEE Registry Parser Mini Edit Export Routines

7. With the publishing side added, it all looks like: Access DB Flat File XML Output ASN.1 Output Oracle DB Multiple Past Records SDO Style Template Recipe For each Standard Flat File Formatted Standard in Word Reports Web Editing Batch Editing IEEE Registry Other Data used in the standard Registry Parser Word Builder Mini Edit Export Routines Word Files

8. What is on the install CD disk: The Mini Edit tool  Normal Installer script, will place things on your machine.  A demo trash database to play with  Current release is 0.3.77 and has decent editing abilities  Auto converting to XML not fully in place but enough works to show it  Still needs find utilities or the ability to import from the IEEE side  Exporting as been fully added Registry Parser  A standalone tool still, it take the batch download” of the IEEE registry export and converts it to various forms. [Will be merged with Mini Edit in time]  In this release it produces an aceess db you can use with MiniEdit  ASN and XML tag formas are still there  With this release you can now take a bunch of data elements from the registry (from another SDO) and use them along with your own access database of entries to link and compare and publish them

9. Demos of the tools in use The Mini Edit tool  Basics of operations and how to play with it  Editing a data concept  Auto converting to XML from other SDO entries  Next steps of thing to add….  A demo of how the final database is used to produce a mature standard using First word to make a richly formatted word document Registry Parser  Overview of this tool  Importing to produce ANS.1 and XML  Importing to produce an Access file  A few hundred data elements from the registry will be processed  Using the resulting file in Mini Edit  The resulting file will be opened in Mini Edit than viewed, correcting entries, and adding XML content, then exported for re-loading to the registry.

10. Short Term Road Map Features Wanted  Fill in some of the fields based on user ID and role  Allow capturing comments of others for promotion review of draft entries  Add Web message sending for comment collections and for auto-updating  Start creating information reports on contents  Provide document publishing side tools to other SDOs (needs discussion with FHWA on support to occur first)  Add 14817 support for Descriptive Names and other items  Create “automatic” 14817 conversion tools  Add “rule checking” to reflect checking the CCC decisions of formatting.  Provide reports on bulk XML results  Add XML builder “blank stub” code creation functions See various word documents for other needs Features Now Done  More Auto-fixing of many simple content problems from the IEEE tool  Importing now produces both an ANS.1 an an Access file, allowing a complete loop of entries between IEEE and the tool.  The XML parse now work, implementing the translation rules on any valid ASN.  This is the big new item in this release and should allow every ASDO to produce its own XML listings for its own standards.  Export produces stripped listings of ASN, XML and other format to support 3 rd party tools and producing complete listings in standards.

11. Tools Used and File Flows Access DB Flat File XML Output ASN.1 Output Oracle DB Multiple Past Records SDO Style Template Recipe For each Standard Flat File Formatted Standard in Word Reports Web Editing Batch Editing IEEE Registry Other Data used in the standard Registry Parser Word Builder Mini Edit Export Routines Word Files