anchor.diff:  ==== 3.1.2 Distinguish ASL During Import
   
   The output of `masl2xtuml` is a legal `.xtuml` file that can be imported
  -into BridgePoint.  Converted MASL models have labels imbedded inside that
  +into BridgePoint.  Converted MASL models have labels embedded inside that
   provide hints to the BridgePoint import process to set MASL-specific
   parameters for the model.  A similar approach will be taken for
   ASL-dialect converted models.
  
positive.code: 
  MASL models are imported with special tags 'masl_project' and 'masl_domain'
  in particular model element locations.  This is done to provide a key to
  the BridgePoint model import funcitionality.  During import, BridgePoint
  detects these keys and performs dialect-specific operations for MASL.
  
  ASL dialect models will need to use a similar approach with different keys.
  
  ==== 3.5.1 Add 'asl_project' and 'asl_domain' to `m2x`
  
  Based upon command line input, the `m2x` conversion utility will imbed
  the label 'asl_project' and 'asl_domain' in the same locations where it
  currently imbeds 'masl_project' and 'masl_domain' for MASL models.
  
  ==== 3.5.2 Detect 'asl_project' and 'asl_domain' in Import
  
  
negative.code: lines of an activity.  This is superfluous and incorrect syntax for ASL
  activities.  The MASL dumper also emits a "begin, null, end" sequence
  for empty activities which is not useful for ASL.
  
  Notem however, that the signature actually serves as the key for the
  activity.  It cannot be completely omitted from processing.
  
  ==== 3.2.1 'Grep out' the MASL Function Signature
  
  