encoding: Fix bug in TlvEncoder.writeNonNegativeInteger: value <= 0xff should be encoded using 1 byte. Refs #1926.
 CHANGELOG: Added bug 1926: Should encode non-negative integers 253 through 255 as one byte. Refs #1926.
Merge branch 'issue/1926-nonNegativeIntegers-253-through-255'. Refs #1926.
http://redmine.named-data.net/issues/1926
 Name: In Name::Component::fromNumberWithMarker, encode using TlvEncoder.writeNonNegativeInteger. This affects appendSegment and appendVersion. Refs #1833.
 CHANGELOG: Name.appendSegment, etc. now use nonNegativeInteger. Refs #1833.
 Name: In the doc for appendSegment, etc, link to the NDN naming conventions Tech Memo.
Merge pull request #41 from rynomad/ferossmerge

Ferossmerge
transport: In WebSocketTransport.onmessage, the Buffer constructor expects an instantiated array.
Merge branch 'master' into feross to pull in bug fix #1925 and make appendSegment, etc. encode as nonNegativeInteger.
Merge branch 'feross' after Ryan Bennett's pull request to use the feross Buffer wrapper and to "bring ndn-js gracefully to the npm ecosystem".
https://github.com/named-data/ndn-js/pull/41
CHANGELOG: Note the pull request from the feross branch.
browserify: Added the copyright header to shim files.
package.json: Changed the license to LGPL-3.0+.
ndn.js: Rebuild after merging the feross branch.
ndn-protocol.xpi: Rebuild to use the new feross Buffer.
 Name: Added appendTimestamp, appendSequenceNumber, appendSegmentOffset, toTimestamp, toSequenceNumber and toSegmentOffset. Refs #1833.
Name.Component: In the constructor, turn an ArrayBuffer into a Uint8Array to support the feross Buffer.
Name.Component: Added fromNumber.
CHANGELOG: Tag release v0.5.
package.json: Change to version 0.5.0.