anchor.diff:      "id": "service-guid-here",
       "name": "mysql",
       "description": "A MySQL-compatible relational database",
  +    "tags":[  
  +        "no-sql",
  +        "relational"
  +     ],
       "bindable": true,
  +    "metadata":{  
  +        "provider":{  
  +        "name":"The name"
  +        },
  +    "requires":[  
  +        "route_forwarding"
  +     ],
  +    "plan_updateable":true,
       "plans": [{
         "id": "plan1-guid-here",
         "name": "small",
         "description": "A small shared database with 100mb storage quota and 10 connections"
  +      "metadata":{  
  +        "cost":0,
  +        "bullets":[  
  +          {  
  +            "content":"40 concurrent connections"
  +          }
  +        ]
  +      }
       },{
         "id": "plan2-guid-here",
         "name": "large",
  
positive.code:   <td>&nbsp;&nbsp;&nbsp;requires</td>
    <td>array-of-strings</td>
    <td>A list of permissions that the user would have to give the service, if they provision it. The only permissions currently supported are <tt>syslog_drain</tt> and <tt>route_forwarding</tt>; for more info see <a href="app-log-streaming.html">Application Log Streaming</a> and <a href="route-services.html">Route Services</a>.</td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;plan_updateable</td>
    <td>boolean</td>
    <td>
  	  Whether the service supports upgrade/downgrade for some plans.
  	  <br/>
  	  Please note that the misspelling of the attribute <i>plan_updatable</i> to <i>plan_updateable</i> was done by mistake. We have opted to keep that misspelling instead of fixing it and thus breaking backward compatibility.
    </td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;plans*</td>
    <td>array-of-objects
  
negative.code:   <td>A short description of the service that will appear in the catalog.</td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;tags</td>
    <td>array-of-strings</td>
    <td>Tags provide a flexible mechanism to expose a classification, attribute, or base technology of a service, enabling equivalent services to be swapped out without changes to dependent logic in applications, buildpacks, or other services. E.g. mysql, relational, redis, key-value, caching, messaging, amqp.</td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;bindable*</td>
    <td>boolean</td>
    <td>Whether the service can be bound to applications.</td>
  </tr>
  <tr>
    <td>&nbsp;&nbsp;&nbsp;metadata</td>
    <td>object</td>
    <td>A list of metadata for a service offering. For more information, see <a href="catalog-metadata.html">Service Metadata</a>.</td>
  