anchor.diff:  #### Data Import  
   
   When the <code>CrossOrigen</code> module is included in a class it gets access
  -to an <code>cr_import</code> method.
  +to a <code>cr_import</code> method.
   This will automatically detect the type of the given file and select the appropriate
   import rules.
   
   The file to be imported must exist locally or it can be pulled automatically from
  -a 3rd party respository in which case the file will be fetched the first time Origen
  +a 3rd party repository in which case the file will be fetched the first time Origen
   is invoked and then cached locally for future invocations.
   Supported repositories are shown in the example below.
   
   ~~~ruby
  -class D_IP_ANA_TEST_ANNEX_SYN
  +class MyDevice
   
     include CrossOrigen
   
  
positive.code:     # Import from Design Sync
      cr_import(vault: "sync://sync-15040:15040/Projects/nvm_c90tfsn2w/ftf2/rtl_v/kx2_4m/.regs", version: "ftf2_kx2_4096k2_256_128k_64_4k.00.00.01.00") 
    end
  
  end
  ~~~
  
  The plugin will add attribute getter and setter methods to the top-level object and to registers and bits
  to contain any metadata information which does not have a direct equivalent within Origen. Generally
  the name given to such data will be the lower cased and underscored (following std Ruby
  conventions) version of the attribute name.
  
  #### Data Export
  
  
negative.code: Currently the following formats are supported:
  
  * IP-XACT - Import and Export registers and hierarchy
  * CMSIS-SVD - Import registers and hierarchy
  * RALF (Synopsys format) - Export registers
  
  See the [examples](<%= path "examples" %>) for format specific documentation, but
  most formats should follow this basic structure...
  