SupportedOperation fields - Example App vs Spec

Hi list,

I'm working on a hydra generator tool in Ruby, and as part of my tests, 
I wanted to make sure it generated a comparable vocab as the one in the 
example app at http://www.markus-lanthaler.com/hydra/api-demo/.

Upon investigating the "supportedOperation" section, the example app's 
vocab looks like this:

     {
       "@id": "vocab:User",
       "@type": "hydra:Class",
       "subClassOf": null,
       "label": "User",
       "description": "A User represents a person registered in the 
system.",
       "supportedOperation": [
         {
           "@id": "_:user_replace",
           "@type": "hydra:Operation",
           "method": "PUT",
           "label": "Replaces an existing User entity",
           "description": null,
           "expects": "vocab:User",
           "returns": "vocab:User",
           "statusCodes": [
             {
               "code": 404,
               "description": "If the User entity wasn't found."
             }
           ]
         },

The part I had a question about is the "label" and "description" fields 
in the SupportedOperation. Comparing them to the "label" and 
"description" fields of the User resource itself, they seem to be 
switched. And when comparing it to the example given in the Hydra Spec 
(EXAMPLE 10 in http://www.hydra-cg.com/spec/latest/core/), I see that it 
uses "title", and no "label" or "description" at all.

Is the example app simply out-of-date with the spec? Forgive my 
ignorance, as I'm still new to Hydra, JSONLD and RDF, but which of those 
is responsible for the "label" field? Perhaps my confusion is related to 
"ISSUE 8" in the spec, "Describe the various properties of an 
operation.", and once that happens, things will be clearer. Is this 
section still subject to much change, and I shouldn't worry about 
getting it to match either the spec or the example app exactly for now?

Thanks
Paul