anchor.diff:  information, logical metadata, and physical files.  Those "artifacts" are almost never isolated in nature.  They're all
   connected and inter-dependent, but the relationships can be difficult to understand.
   
  -In the software development world, this is an especially important problem to solve.  Dictionary.com defines "artifact"
  -as "any object made by human beings, especially with a view to *subsequent use*".  That's key!  The development process
  +In the software development world, this is an especially important problem to solve.  The development process
   often spews out a huge amount of artifacts, needed for future analysis and actions.  Without the ability to
   analyze how the information, artifacts, and content within the artifacts are connected, development
  -processes become difficult, at best, or nearly impossible, at worst.  Both the publisher and the consumer need help!
  +processes become difficult, at best, or nearly impossible, at worst.  Further, it's not enough to simply know how the
  +bits are related.  How do you correlate the artifacts/metadata with, for example, service endpoints,
  +the responsible teams/individuals, and change histories?
  +
  +Both the publisher and the consumer need help!
   
   
   Overview
  
positive.code: Two of the developers on the project currently participate in the Technical Committee, one of which is the co-chair.
  
  It's important to note that Artificer is not simply an S-RAMP implementation!  The capabilities extend well beyond
  what's required by the spec.
  
  
  Core Properties
  
negative.code: ** Type declarations in XSDs
  ** Messages/ports/endpoints in WSDLs
  ** Many others
  * Automatically detects content type
  * Powerful query language
  * Many interfaces & integrations
  ** REST/Atom
  