Update bibref/biblio.js

Added information about the Role Attribute Candidate Recommendation as ROLE-ATTRIBUTE.
Update js/w3c/legacy.js

Configuration was never processed correctly for legacy code.
Added refs for GSM-SMS, OMA-PUSH, and RFC3428
Merge pull request #86 from fhirsch/develop

Update bibref/biblio.js
Merge pull request #85 from blsaws/develop

Added refs for GSM-SMS, OMA-PUSH, and RFC3428
Merge pull request #84 from halindrome/patch-1

Update bibref/biblio.js
v3.1.28
Merge branch 'release/v3.1.28' into develop
Add a core/requirements module.

This module does two things:

1.  It finds and marks all requirements. These are elements with class "req".
    When a requirement is found, it is reported using the "req" event. This
    can be used by a containing shell to extract them.
    Requirements are automatically numbered.

2.  It allows referencing requirements by their ID simply using an empty <a>
    element with its href pointing to the requirement it should be referencing
    and a class of "reqRef".

                           * * *

    <p>This use cases implies the following requirements:
    <a href="#foo" class=reqRef></a>, <a href="#bar" class=reqRef></a>.</p>
    
    […]
    
    <p id="foo" class=req>It MUST be possible to do foo.</p>

    <p id="bar" class=req>It MUST be possible to do bar.</p>

Will yeld:

    This use cases implies the following requirements:
    <a href="#foo" class=req>Req. 1</a>, <a href="#bar" class=req>Req. 2</a>.</p>
    
    […]
    
    <p id="foo" class=req><a href="#foo" class=req>Req. 1</a>: It MUST be possible to do foo.</p>

    <p id="bar" class=req><a href="#bar" class=req>Req. 2</a>: It MUST be possible to do bar.</p>
Merge pull request #88 from tobie/req

Add a core/requirements module.
Add Markdown support.

Markdown support is optional. It is enabled by setting the `format`
property of the configuration object to "markdown."

ReSpec uses marked for parsing Markkdown.

Note that the content of SECTION elements, and P elements with a
class name of "note" or "issue" is also parsed.

The HTML created by the Markdown parser is turned into a nested
structure of SECTION elements, following the strucutre given by
the headings. For example, the following markup:

    Title
    -----

    ### Subtitle ###

    Here's some text.

    ### Another subtitle ###

    More text.

will be transformed into:

    <section>
      <h2>Title</h2>
      <section>
        <h3>Subtitle</h3>
        <p>Here's some text.</p>
      </section>
      <section>
        <h3>Another subtitle</h3>
        <p>More text.</p>
      </section>
    </section>
Unescape > to fix broken support for block quotes.
Handles markdown content being nested inside elements with soft tabs.

E.g.:

'''
<div>
    This is a title
    ---------------
    
    And this more text.
</div
'''

Gets turned into:

'''
<div>
    <h2>This is a title</h2>
    <p>And this more text.</p>
</div
'''

Rather than:

'''
<div>
    <pre><code>This is a title
---------------

And this more text.</code></pre>
</div
'''
Notes and issues need not be paragraphs.
Also process markdown within requirements.
Add specs for core/requirements.
Fix leaked global variables.
Add specs for markdown implementation.
Comment-out the code dealing with markdown parsing of content nested in markup and explain why.
Merge pull request #90 from tobie/md

Add Markdown support (with bugfixes and specs).