[SCM] librdf-ns-perl Debian packaging branch, master, updated. debian/20130208-1-22-g47de138

[Jakob Voss]

The following commit has been merged in the master branch:
commit 58b7d8e9dc8a88206efb9fe321fdd653f0df9ad6
Author: Jakob Voss <voss at gbv.de>
Date:   Tue Nov 1 18:47:02 2011 +0100

    typos

diff --git a/README b/README
index 1a7ac1a..a0ada59 100644
--- a/README
+++ b/README
@@ -3,11 +3,11 @@ for abbreviation. Defining namespaces, however, is also cumbersome because you
 need to repeat this step in every environment. This is silly because in most
 cases we use the same URI namespaces anyway. Some popular examples:
 
-    @prefix owl: <http://www.w3.org/2002/07/owl#> .            Turtle/N3 syntax
+    @prefix owl: <http://www.w3.org/2002/07/owl#> .   (Turtle/N3)
 
-    PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>     SPARQL syntax
+    PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>   (SPARQL)
 
-    xlmns:rdf="http://xmlns.com/foaf/0.1/"                       RDF/XML syntax
+    xmlns:foaf="http://xmlns.com/foaf/0.1/"   (RDF/XML)
 
 Fortunately there is http://prefix.cc, a registry where people can vote the most
 popular URI namespaces. It is best practice to use the same prefixes as defined
@@ -23,8 +23,6 @@ to the date of a particular snapshot. The changelog in the file Changes lists
 all snapshots with their modifications. RDF::NS provides some handy methods,
 for instance you can use method-calls to create full URIs:
 
-    $ns = RDF::NS->new('20111031');
-
     $ns->rdf_type; # returns "http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
 
 The subclass RDF::NS::Trine, shipped with RDF::NS returns blessed URI objects

-- 
librdf-ns-perl Debian packaging