--- CBOR-XS/XS.pm	2013/10/29 00:20:26	1.11
+++ CBOR-XS/XS.pm	2013/10/30 10:11:04	1.17
@@ -48,6 +48,14 @@
 often compresses better than CBOR though, so if you plan to compress the
 data later you might want to compare both formats first).
 
+To give you a general idea about speed, with texts in the megabyte range,
+C<CBOR::XS> usually encodes roughly twice as fast as L<Storable> or
+L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the
+data, the worse L<Storable> performs in comparison.
+
+As for compactness, C<CBOR::XS> encoded data structures are usually about
+20% smaller than the same data encoded as (compact) JSON or L<Storable>.
+
 The primary goal of this module is to be I<correct> and the secondary goal
 is to be I<fast>. To reach the latter goal it was written in C.
 
@@ -60,7 +68,7 @@
 
 use common::sense;
 
-our $VERSION = 0.05;
+our $VERSION = 0.08;
 our @ISA = qw(Exporter);
 
 our @EXPORT = qw(encode_cbor decode_cbor);
@@ -285,8 +293,9 @@
 =item CBOR::XS::Tagged objects
 
 Objects of this type must be arrays consisting of a single C<[tag, value]>
-pair. The (numerical) tag will be encoded as a CBOR tag, the value will be
-encoded as appropriate for the value.
+pair. The (numerical) tag will be encoded as a CBOR tag, the value will
+be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to
+create such objects.
 
 =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error
 
@@ -456,6 +465,95 @@
 required.
 
 
+=head1 THE CBOR::XS::Tagged CLASS
+
+CBOR has the concept of tagged values - any CBOR value can be tagged with
+a numeric 64 bit number, which are centrally administered.
+
+C<CBOR::XS> handles a few tags internally when en- or decoding. You can
+also create tags yourself by encoding C<CBOR::XS::Tagged> objects, and the
+decoder will create C<CBOR::XS::Tagged> objects itself when it hits an
+unknown tag.
+
+These objects are simply blessed array references - the first member of
+the array being the numerical tag, the second being the value.
+
+You can interact with C<CBOR::XS::Tagged> objects in the following ways:
+
+=over 4
+
+=item $tagged = CBOR::XS::tag $tag, $value
+
+This function(!) creates a new C<CBOR::XS::Tagged> object using the given
+C<$tag> (0..2**64-1) to tag the given C<$value> (which can be any Perl
+value that can be encoded in CBOR, including serialisable Perl objects and
+C<CBOR::XS::Tagged> objects).
+
+=item $tagged->[0]
+
+=item $tagged->[0] = $new_tag
+
+=item $tag = $tagged->tag
+
+=item $new_tag = $tagged->tag ($new_tag)
+
+Access/mutate the tag.
+
+=item $tagged->[1]
+
+=item $tagged->[1] = $new_value
+
+=item $value = $tagged->value
+
+=item $new_value = $tagged->value ($new_value)
+
+Access/mutate the tagged value.
+
+=back
+
+=cut
+
+sub tag($$) {
+   bless [@_], CBOR::XS::Tagged::;
+}
+
+sub CBOR::XS::Tagged::tag {
+   $_[0][0] = $_[1] if $#_;
+   $_[0][0]
+}
+
+sub CBOR::XS::Tagged::value {
+   $_[0][1] = $_[1] if $#_;
+   $_[0][1]
+}
+
+=head2 EXAMPLES
+
+Here are some examples of C<CBOR::XS::Tagged> uses to tag objects.
+
+You can look up CBOR tag value and emanings in the IANA registry at
+L<http://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml>.
+
+Prepend a magic header (C<$CBOR::XS::MAGIC>):
+
+   my $cbor = encode_cbor CBOR::XS::tag 55799, $value;
+   # same as:
+   my $cbor = $CBOR::XS::MAGIC . encode_cbor $value;
+
+Serialise some URIs and a regex in an array:
+
+   my $cbor = encode_cbor [
+      (CBOR::XS::tag 32, "http://www.nethype.de/"),
+      (CBOR::XS::tag 32, "http://software.schmorp.de/"),
+      (CBOR::XS::tag 35, "^[Pp][Ee][Rr][lL]\$"),
+   ];
+
+Wrap CBOR data in CBOR:
+
+   my $cbor_cbor = encode_cbor
+      CBOR::XS::tag 24,
+         encode_cbor [1, 2, 3];
+
 =head1 CBOR and JSON
 
 CBOR is supposed to implement a superset of the JSON data model, and is,