rdf-vocab 3.1.9 → 3.1.10

data/lib/rdf/vocab/cert.rb

@@ -9,8 +9,8 @@ module RDF::Vocab
   #   # Ontology for Certificates and crypto stuff.
   #   #
   #   #     Ontology for Certificates and crypto stuff.    This is in development.     Some other ontologies to look at:      * http://www.w3.org/2000/10/swap/crypto         + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust         - a bit old perhaps. It imports daml+oil         - would help to be more completely specified         - uses literals as subjects a little liberally, which makes this a          bit difficult to work with frameworks that don't permit this      * http://xmlns.com/wot/0.1/         - limited very much to PGP (though on can map PGP to X509)         - a little coarse grained, mixes up the PGP certificate with the PGP           public key      *    Todo:       - add some classes and relations for DSA      - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter?      - expand more on the certification side of things      - verify this by security experts      - owl2 has some constructs for combined inverse functional properties.         This may be useful to use in defining an RSA key which is identified        by two numbers.      - also create html version of the spec by using this as a template.      - should comments such as this be in html?    
-  #   # @see http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
   #   # @see http://www.w3.org/ns/auth/X509Uml.svg
+  #   # @see http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
   #   # @see http://www.w3.org/ns/auth/rsa
   #   class CERT < RDF::StrictVocabulary
   #     # A certificate is a Document that is signed.     As explained here http://www.pgpi.org/doc/pgpintro/#p16     'A digital certificate consists of three things:         * A public key.         * Certificate information. ('Identity' information about the             user, such as name, user ID, and so on.)         * One or more digital signatures.'     
@@ -78,32 +78,7 @@ module RDF::Vocab
 
     # Ontology definition
     ontology :"http://www.w3.org/ns/auth/cert#",
-      comment: %(
-   Ontology for Certificates and crypto stuff.
-   This is in development. 
-   Some other ontologies to look at:
-     * http://www.w3.org/2000/10/swap/crypto
-        + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust
-        - a bit old perhaps. It imports daml+oil
-        - would help to be more completely specified
-        - uses literals as subjects a little liberally, which makes this a 
-        bit difficult to work with frameworks that don't permit this
-     * http://xmlns.com/wot/0.1/
-        - limited very much to PGP \(though on can map PGP to X509\)
-        - a little coarse grained, mixes up the PGP certificate with the PGP
-          public key
-     *
-   Todo: 
-     - add some classes and relations for DSA
-     - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter?
-     - expand more on the certification side of things
-     - verify this by security experts
-     - owl2 has some constructs for combined inverse functional properties. 
-       This may be useful to use in defining an RSA key which is identified
-       by two numbers.
-     - also create html version of the spec by using this as a template.
-     - should comments such as this be in html?
-   ).freeze,
+      comment: "\n   Ontology for Certificates and crypto stuff.\n   This is in development. \n   Some other ontologies to look at:\n     * http://www.w3.org/2000/10/swap/crypto\n        + has cwm builtins: http://www.w3.org/2000/10/swap/doc/Trust\n        - a bit old perhaps. It imports daml+oil\n        - would help to be more completely specified\n        - uses literals as subjects a little liberally, which makes this a \n        bit difficult to work with frameworks that don't permit this\n     * http://xmlns.com/wot/0.1/\n        - limited very much to PGP (though on can map PGP to X509)\n        - a little coarse grained, mixes up the PGP certificate with the PGP\n          public key\n     *\n   Todo: \n     - add some classes and relations for DSA\n     - should this all be in one file? Or should this be cut up a little? Say one file for the general CERT ontology, and then files for RSA, DSA, PGP, etc... Or perhaps it does not really matter?\n     - expand more on the certification side of things\n     - verify this by security experts\n     - owl2 has some constructs for combined inverse functional properties. \n       This may be useful to use in defining an RSA key which is identified\n       by two numbers.\n     - also create html version of the spec by using this as a template.\n     - should comments such as this be in html?\n   ".freeze,
       "dc:created": "2008-11-13".freeze,
       "foaf:maker": "http://bblfish.net/people/henry/card#me".freeze,
       label: "Ontology for Certificates and crypto stuff.".freeze,
@@ -113,26 +88,19 @@ module RDF::Vocab
 
     # Class definitions
     term :Certificate,
-      comment: %(A certificate is a Document that is signed.
-    As explained here http://www.pgpi.org/doc/pgpintro/#p16
-    'A digital certificate consists of three things:
-        * A public key.
-        * Certificate information. \('Identity' information about the  
-          user, such as name, user ID, and so on.\)
-        * One or more digital signatures.'
-    ).freeze,
+      comment: "A certificate is a Document that is signed.\n    As explained here http://www.pgpi.org/doc/pgpintro/#p16\n    'A digital certificate consists of three things:\n        * A public key.\n        * Certificate information. ('Identity' information about the  \n          user, such as name, user ID, and so on.)\n        * One or more digital signatures.'\n    ".freeze,
       isDefinedBy: "cert:".freeze,
       label: "Certificate".freeze,
       subClassOf: "foaf:Document".freeze,
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :Key,
-      comment: %(the class of keys).freeze,
+      comment: "the class of keys".freeze,
       isDefinedBy: "cert:".freeze,
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :PGPCertificate,
-      comment: %(the class of PGP Certificates).freeze,
+      comment: "the class of PGP Certificates".freeze,
       equivalentClass: "wot:PubKey".freeze,
       isDefinedBy: "cert:".freeze,
       label: "PGPCertificate".freeze,
@@ -140,33 +108,27 @@ module RDF::Vocab
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :PrivateKey,
-      comment: %(Private Key).freeze,
+      comment: "Private Key".freeze,
       isDefinedBy: "cert:".freeze,
       label: "PrivateKey".freeze,
       subClassOf: "cert:Key".freeze,
       type: "owl:Class".freeze
     term :PublicKey,
-      comment: %(Public Key).freeze,
+      comment: "Public Key".freeze,
       isDefinedBy: "cert:".freeze,
       label: "PublicKey".freeze,
       subClassOf: "cert:Key".freeze,
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :RSAKey,
-      comment: %(
-    The union of the public and private components of an RSAKey.
-    Usually those pieces are not kept together
-    ).freeze,
+      comment: "\n    The union of the public and private components of an RSAKey.\n    Usually those pieces are not kept together\n    ".freeze,
       isDefinedBy: "cert:".freeze,
       label: "RSA Key".freeze,
       subClassOf: "cert:Key".freeze,
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :RSAPublicKey,
-      comment: %(
-    The RSA public key.  Padded message m are encrypted by applying the function
-      modulus\(power\(m,exponent\),modulus\)
-    ).freeze,
+      comment: "\n    The RSA public key.  Padded message m are encrypted by applying the function\n      modulus(power(m,exponent),modulus)\n    ".freeze,
       isDefinedBy: "cert:".freeze,
       label: "RSA Public Key".freeze,
       "rdfs:seeAlso": "http://en.wikipedia.org/wiki/RSA".freeze,
@@ -174,13 +136,13 @@ module RDF::Vocab
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :Signature,
-      comment: %(the class of signtatures).freeze,
+      comment: "the class of signtatures".freeze,
       isDefinedBy: "cert:".freeze,
       label: "Signature".freeze,
       type: "owl:Class".freeze,
       "vs:term_status": "unstable".freeze
     term :X509Certificate,
-      comment: %(the class of X509 Certificates).freeze,
+      comment: "the class of X509 Certificates".freeze,
       isDefinedBy: "cert:".freeze,
       label: "X509Certificate".freeze,
       "rdfs:seeAlso": "http://en.wikipedia.org/wiki/X509".freeze,
@@ -190,10 +152,7 @@ module RDF::Vocab
 
     # Property definitions
     property :exponent,
-      comment: %(
-       The exponent used to encrypt the message. Number chosen between
-       1 and the totient\(p*q\). Often named 'e' .
-    ).freeze,
+      comment: "\n       The exponent used to encrypt the message. Number chosen between\n       1 and the totient(p*q). Often named 'e' .\n    ".freeze,
       domain: "cert:RSAPublicKey".freeze,
       isDefinedBy: "cert:".freeze,
       label: "exponent".freeze,
@@ -201,23 +160,16 @@ module RDF::Vocab
       type: "owl:DatatypeProperty".freeze,
       "vs:term_status": "unstable".freeze
     property :identity,
-      comment: %(
-    the identity of the public key. This is the entity that knows the private key and 
-    so can decrypt messages encrypted with the public key, or encrypt messages that can 
-    be decrypted with the public key. 
-    ).freeze,
+      comment: "\n    the identity of the public key. This is the entity that knows the private key and \n    so can decrypt messages encrypted with the public key, or encrypt messages that can \n    be decrypted with the public key. \n    ".freeze,
       domain: "cert:PublicKey".freeze,
-      editorialNote: %(
-         It turns out that this relation is unintuitive to write out and to name.
-         One should instead use cert:key
-    ).freeze,
+      editorialNote: "\n         It turns out that this relation is unintuitive to write out and to name.\n         One should instead use cert:key\n    ".freeze,
       inverseOf: "cert:key".freeze,
       isDefinedBy: "cert:".freeze,
       label: "identity".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze],
       "vs:term_status": "archaic".freeze
     property :key,
-      comment: %(relates an agent to a key - most often the public key.).freeze,
+      comment: "relates an agent to a key - most often the public key.".freeze,
       domain: "foaf:Agent".freeze,
       inverseOf: "cert:identity".freeze,
       isDefinedBy: "cert:".freeze,
@@ -226,18 +178,7 @@ module RDF::Vocab
       type: ["owl:InverseFunctionalProperty".freeze, "owl:ObjectProperty".freeze, "rdf:Property".freeze],
       "vs:term_status": "unstable".freeze
     property :modulus,
-      comment: %(    
-   <p>The modulus of an RSA public and private key. 
-   Or the modulus of a DSA Key.
-   The modulus is encoded as a hex binary. The binary is the same as the one encoded in the 
-  <a href="http://www.w3.org/TR/xmldsig-core/#sec-CryptoBinary">XML DSIG CryptoBinary</a>
-  </p>
-  <blockquote>
-   This specification defines the ds:CryptoBinary simple type for representing arbitrary-length integers \(e.g. "bignums"\) in XML as octet strings. The integer value is first converted to a "big endian" bitstring. The bitstring is then padded with leading zero bits so that the total number of bits == 0 mod 8 \(so that there are an integral number of octets\). If the bitstring contains entire leading octets that are zero, these are removed \(so the high-order octet is always non-zero\).
-  </blockquote>
- <p>The only difference is that the octet string is then encoded using either xsd:base64Binary or xsd:hexBinary. Currently for all usages of this relation, the xsd:hexBinary datatype should be used until the SPARQL working group specifies specifies in its <a href="http://www.w3.org/TR/sparql11-entailment/#DEntRegime">D-Entailment</a> that those two types are equivalent.</p>
- <p>It would have been better had there been a hexInteger datatype that was standard and supported by all tools.</p>
-   ).freeze,
+      comment: "    \n   <p>The modulus of an RSA public and private key. \n   Or the modulus of a DSA Key.\n   The modulus is encoded as a hex binary. The binary is the same as the one encoded in the \n  <a href=\"http://www.w3.org/TR/xmldsig-core/#sec-CryptoBinary\">XML DSIG CryptoBinary</a>\n  </p>\n  <blockquote>\n   This specification defines the ds:CryptoBinary simple type for representing arbitrary-length integers (e.g. \"bignums\") in XML as octet strings. The integer value is first converted to a \"big endian\" bitstring. The bitstring is then padded with leading zero bits so that the total number of bits == 0 mod 8 (so that there are an integral number of octets). If the bitstring contains entire leading octets that are zero, these are removed (so the high-order octet is always non-zero).\n  </blockquote>\n <p>The only difference is that the octet string is then encoded using either xsd:base64Binary or xsd:hexBinary. Currently for all usages of this relation, the xsd:hexBinary datatype should be used until the SPARQL working group specifies specifies in its <a href=\"http://www.w3.org/TR/sparql11-entailment/#DEntRegime\">D-Entailment</a> that those two types are equivalent.</p>\n <p>It would have been better had there been a hexInteger datatype that was standard and supported by all tools.</p>\n   ".freeze,
       domain: "cert:RSAKey".freeze,
       isDefinedBy: "cert:".freeze,
       label: "modulus".freeze,
@@ -245,12 +186,7 @@ module RDF::Vocab
       type: "owl:DatatypeProperty".freeze,
       "vs:term_status": "unstable".freeze
     property :privateExponent,
-      comment: %(
-       The exponent used to decrypt the message
-       calculated as 
-          public_exponent*private_exponent = 1 modulo totient\(p*q\)
-       The private exponent is often named 'd'
-    ).freeze,
+      comment: "\n       The exponent used to decrypt the message\n       calculated as \n          public_exponent*private_exponent = 1 modulo totient(p*q)\n       The private exponent is often named 'd'\n    ".freeze,
       domain: "cert:PrivateKey".freeze,
       isDefinedBy: "cert:".freeze,
       label: "private".freeze,
@@ -260,51 +196,8 @@ module RDF::Vocab
 
     # Datatype definitions
     term :hex,
-      comment: %(<span xmlns="http://www.w3.org/1999/xhtml" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:vs="http://www.w3.org/2003/06/sw-vocab-status/ns#"><p>
-   An encoding of a positive integer \(from 0 to infinity\) as a hexadecimal string that makes it easy to read and/or fun to present on the web.</p>
-   <p>The purpose of this way of representing hexadecimals is to enable users to copy and paste hexadecimal notations as shown by most browsers, keychains or tools such as opensso, into their rdf representation of choice.  There are a wide variety of ways in which such strings can be presented. One finds the following:</p>
-<pre>
-  e1 dc d5 e1 00 8f 21 5e d5 cc 7c 7e c4 9c ad 86 
-  64 aa dc 29 f2 8d d9 56 7f 31 b6 bd 1b fd b8 ee 
-  51 0d 3c 84 59 a2 45 d2 13 59 2a 14 82 1a 0f 6e 
-  d3 d1 4a 2d a9 4c 7e db 90 07 fc f1 8d a3 8e 38 
-  25 21 0a 32 c1 95 31 3c ba 56 cc 17 45 87 e1 eb 
-  fd 9f 0f 82 16 67 9f 67 fa 91 e4 0d 55 4e 52 c0 
-  66 64 2f fe 98 8f ae f8 96 21 5e ea 38 9e 5c 4f 
-  27 e2 48 ca ca f2 90 23 ad 99 4b cc 38 32 6d bf  
-</pre>
-<p>
- Or the same as the above, with ':' instead of spaces. We can't guarantee that these are the only ways such tools will present hexadecimals, so we are very lax.</p>
- <p>The letters can be uppercase or lowercase, or mixed.  </p>
- <p>Some strings may start with initial 00's, and can be stripped in this notation as they often are. Doing this could, in complement of 2 notation turn a positive number into a negative one, if the first hexadecimal character happens to be one of  the set {'8', '9', 'a', 'A', 'b', 'B', 'c', 'C', 'd', 'D', 'e', 'E', 'f', 'F'} .  As we interpret this string as a hexadecimal number leading 00s are not important  \(Complement of 2 notation and hexadecimal overlap for positive numbers\)</p>
-<p> In order to make this fun, we allow any unicode characters in the string. A parser should </p>
-  <ol>
-<li>remove all non hexadecimal characters</li>
-<li>treat the resulting as a hexadecimal representation of a number</li>
-</ol>
-<p>
- This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.
-</p>
-<p>
-  Cert hex is also a datatype property because we used to write it out like this
-</p>
- <pre>
-   [] a rsa:RSAPublicKey;
-     rsa:public_exponent [ cert:hex "e1 dc d5 ..."] 
- </pre> 
-<p> The above notation is now deprecated. Now we prefer the literal format below.</p>
- <pre>
-   [] a rsa:RSAPublicKey;
-     rsa:public_exponent "e1 dc d5 ..."^^cert:hex .
- </pre> 
-   </span>
-        ).freeze,
-      editorialNote: %(<span xmlns="http://www.w3.org/1999/xhtml"><p> 
-     This relation should slowly be transited to just being a datatype.</p>
-     <p>Being a datatype and a property is legal as explained here
-  <a href="http://lists.w3.org/Archives/Public/semantic-web/2010Mar/0037.html">on the semantic web mailing list in March 2010</a>. 
- But it may be somewhat confusing, especially if it goes against a pattern - still to be set - by the xsd datatypes as the follow up email makes clear. </p></span>
-   ).freeze,
+      comment: "<span xmlns=\"http://www.w3.org/1999/xhtml\" xmlns:dc=\"http://purl.org/dc/terms/\" xmlns:foaf=\"http://xmlns.com/foaf/0.1/\" xmlns:owl=\"http://www.w3.org/2002/07/owl#\" xmlns:rdf=\"http://www.w3.org/1999/02/22-rdf-syntax-ns#\" xmlns:rdfs=\"http://www.w3.org/2000/01/rdf-schema#\" xmlns:skos=\"http://www.w3.org/2004/02/skos/core#\" xmlns:vs=\"http://www.w3.org/2003/06/sw-vocab-status/ns#\"><p>\n   An encoding of a positive integer (from 0 to infinity) as a hexadecimal string that makes it easy to read and/or fun to present on the web.</p>\n   <p>The purpose of this way of representing hexadecimals is to enable users to copy and paste hexadecimal notations as shown by most browsers, keychains or tools such as opensso, into their rdf representation of choice.  There are a wide variety of ways in which such strings can be presented. One finds the following:</p>\n<pre>\n  e1 dc d5 e1 00 8f 21 5e d5 cc 7c 7e c4 9c ad 86 \n  64 aa dc 29 f2 8d d9 56 7f 31 b6 bd 1b fd b8 ee \n  51 0d 3c 84 59 a2 45 d2 13 59 2a 14 82 1a 0f 6e \n  d3 d1 4a 2d a9 4c 7e db 90 07 fc f1 8d a3 8e 38 \n  25 21 0a 32 c1 95 31 3c ba 56 cc 17 45 87 e1 eb \n  fd 9f 0f 82 16 67 9f 67 fa 91 e4 0d 55 4e 52 c0 \n  66 64 2f fe 98 8f ae f8 96 21 5e ea 38 9e 5c 4f \n  27 e2 48 ca ca f2 90 23 ad 99 4b cc 38 32 6d bf  \n</pre>\n<p>\n Or the same as the above, with ':' instead of spaces. We can't guarantee that these are the only ways such tools will present hexadecimals, so we are very lax.</p>\n <p>The letters can be uppercase or lowercase, or mixed.  </p>\n <p>Some strings may start with initial 00's, and can be stripped in this notation as they often are. Doing this could, in complement of 2 notation turn a positive number into a negative one, if the first hexadecimal character happens to be one of  the set {'8', '9', 'a', 'A', 'b', 'B', 'c', 'C', 'd', 'D', 'e', 'E', 'f', 'F'} .  As we interpret this string as a hexadecimal number leading 00s are not important  (Complement of 2 notation and hexadecimal overlap for positive numbers)</p>\n<p> In order to make this fun, we allow any unicode characters in the string. A parser should </p>\n  <ol>\n<li>remove all non hexadecimal characters</li>\n<li>treat the resulting as a hexadecimal representation of a number</li>\n</ol>\n<p>\n This will allow people to make an ascii - better yet a UTF-8 - picture of their public key when publishing it on the web.\n</p>\n<p>\n  Cert hex is also a datatype property because we used to write it out like this\n</p>\n <pre>\n   [] a rsa:RSAPublicKey;\n     rsa:public_exponent [ cert:hex \"e1 dc d5 ...\"] \n </pre> \n<p> The above notation is now deprecated. Now we prefer the literal format below.</p>\n <pre>\n   [] a rsa:RSAPublicKey;\n     rsa:public_exponent \"e1 dc d5 ...\"^^cert:hex .\n </pre> \n   </span>\n        ".freeze,
+      editorialNote: "<span xmlns=\"http://www.w3.org/1999/xhtml\"><p> \n     This relation should slowly be transited to just being a datatype.</p>\n     <p>Being a datatype and a property is legal as explained here\n  <a href=\"http://lists.w3.org/Archives/Public/semantic-web/2010Mar/0037.html\">on the semantic web mailing list in March 2010</a>. \n But it may be somewhat confusing, especially if it goes against a pattern - still to be set - by the xsd datatypes as the follow up email makes clear. </p></span>\n   ".freeze,
       equivalentClass: "xsd:nonNegativeInteger".freeze,
       isDefinedBy: "cert:".freeze,
       label: "hexadecimal".freeze,

data/lib/rdf/vocab/cnt.rb

@@ -89,7 +89,7 @@ module RDF::Vocab
 
     # Ontology definition
     ontology :"http://www.w3.org/2011/content#",
-      comment: %(Representing Content in RDF as defined by http://www.w3.org/TR/Content-in-RDF/).freeze,
+      comment: "Representing Content in RDF as defined by http://www.w3.org/TR/Content-in-RDF/".freeze,
       isDefinedBy: "http://www.w3.org/TR/Content-in-RDF/".freeze,
       label: "Representing Content in RDF".freeze,
       "owl:imports": "dc:".freeze,
@@ -99,104 +99,104 @@ module RDF::Vocab
 
     # Class definitions
     term :Content,
-      comment: %(The content.).freeze,
+      comment: "The content.".freeze,
       label: "Content".freeze,
       type: ["owl:Class".freeze, "rdfs:Class".freeze]
     term :ContentAsBase64,
-      comment: %(The base64 encoded content \(can be used for binary content\).).freeze,
+      comment: "The base64 encoded content (can be used for binary content).".freeze,
       label: "Base64 content".freeze,
       subClassOf: "cnt:Content".freeze,
       type: ["owl:Class".freeze, "rdfs:Class".freeze]
     term :ContentAsText,
-      comment: %(The text content \(can be used for text content\).).freeze,
+      comment: "The text content (can be used for text content).".freeze,
       label: "Text content".freeze,
       subClassOf: "cnt:Content".freeze,
       type: ["owl:Class".freeze, "rdfs:Class".freeze]
     term :ContentAsXML,
-      comment: %(The XML content \(can only be used for XML-wellformed content\).).freeze,
+      comment: "The XML content (can only be used for XML-wellformed content).".freeze,
       label: "XML content".freeze,
       subClassOf: "cnt:Content".freeze,
       type: ["owl:Class".freeze, "rdfs:Class".freeze]
     term :DoctypeDecl,
-      comment: %(The document type declaration.).freeze,
+      comment: "The document type declaration.".freeze,
       label: "Document type declaration".freeze,
       type: ["owl:Class".freeze, "rdfs:Class".freeze]
 
     # Property definitions
     property :bytes,
-      comment: %(The Base64 encoded byte sequence of the content.).freeze,
+      comment: "The Base64 encoded byte sequence of the content.".freeze,
       domain: "cnt:ContentAsBase64".freeze,
       label: "Base64 encoded byte sequence".freeze,
       range: "xsd:base64Binary".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :characterEncoding,
-      comment: %(The character encoding used to create a character sequence from a byte sequence or vice versa.).freeze,
+      comment: "The character encoding used to create a character sequence from a byte sequence or vice versa.".freeze,
       domain: "cnt:Content".freeze,
       label: "Character encoding".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :chars,
-      comment: %(The character sequence of the text content.).freeze,
+      comment: "The character sequence of the text content.".freeze,
       domain: "cnt:ContentAsText".freeze,
       label: "Character sequence".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :declaredEncoding,
-      comment: %(The character encoding declared in the XML declaration.).freeze,
+      comment: "The character encoding declared in the XML declaration.".freeze,
       domain: "cnt:ContentAsXML".freeze,
       label: "XML character encoding".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :doctypeName,
-      comment: %(The document type name.).freeze,
+      comment: "The document type name.".freeze,
       domain: "cnt:DoctypeDecl".freeze,
       label: "Document type name".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :dtDecl,
-      comment: %(The document type declaration.).freeze,
+      comment: "The document type declaration.".freeze,
       domain: "cnt:ContentAsXML".freeze,
       label: "Document type declaration".freeze,
       range: "cnt:DoctypeDecl".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :internalSubset,
-      comment: %(The internal document type definition subset within the document type declarations.).freeze,
+      comment: "The internal document type definition subset within the document type declarations.".freeze,
       domain: "cnt:DoctypeDecl".freeze,
       label: "Internal DTD subset".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :leadingMisc,
-      comment: %(The XML content preceding the document type declaration.).freeze,
+      comment: "The XML content preceding the document type declaration.".freeze,
       domain: "cnt:ContentAsXML".freeze,
       label: "XML leading misc".freeze,
       range: "rdf:XMLLiteral".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :publicId,
-      comment: %(The document type declarations's public identifier.).freeze,
+      comment: "The document type declarations's public identifier.".freeze,
       domain: "cnt:DoctypeDecl".freeze,
       label: "Public ID".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :rest,
-      comment: %(The XML content following the document type declaration.).freeze,
+      comment: "The XML content following the document type declaration.".freeze,
       domain: "cnt:ContentAsXML".freeze,
       label: "XML rest".freeze,
       range: "rdf:XMLLiteral".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :standalone,
-      comment: %(The standalone declaration in the XML declaration.).freeze,
+      comment: "The standalone declaration in the XML declaration.".freeze,
       domain: "cnt:ContentAsXML".freeze,
       label: "XML standalone document declaration".freeze,
       range: "rdfs:Literal".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :systemId,
-      comment: %(The document type declarations's system identifier \(typed: xsd:anyURI\)).freeze,
+      comment: "The document type declarations's system identifier (typed: xsd:anyURI)".freeze,
       domain: "cnt:DoctypeDecl".freeze,
       label: "System ID".freeze,
       range: "xsd:anyURI".freeze,
       type: ["owl:ObjectProperty".freeze, "rdf:Property".freeze]
     property :version,
-      comment: %(The XML version declared in the XML declaration.).freeze,
+      comment: "The XML version declared in the XML declaration.".freeze,
       domain: "cnt:ContentAsXML".freeze,
       label: "XML version".freeze,
       range: "rdfs:Literal".freeze,

data/lib/rdf/vocab/dbo.rb

@@ -10474,12 +10474,7 @@ module RDF::Vocab
     # Ontology definition
     ontology :"http://dbpedia.org/ontology/",
       "cc:license": ["http://creativecommons.org/licenses/by-sa/3.0/".freeze, "http://www.gnu.org/copyleft/fdl.html".freeze],
-      comment: %(
-              This ontology is generated from the manually created specifications in the DBpedia Mappings
-              Wiki. Each release of this ontology corresponds to a new release of the DBpedia data set which
-              contains instance data extracted from the different language versions of Wikipedia. For
-              information regarding changes in this ontology, please refer to the DBpedia Mappings Wiki.
-            ).freeze,
+      comment: "\n              This ontology is generated from the manually created specifications in the DBpedia Mappings\n              Wiki. Each release of this ontology corresponds to a new release of the DBpedia data set which\n              contains instance data extracted from the different language versions of Wikipedia. For\n              information regarding changes in this ontology, please refer to the DBpedia Mappings Wiki.\n            ".freeze,
       "dc:creator": "DBpedia Maintainers and Contributors".freeze,
       "dc:description": "\n              The DBpedia ontology provides the classes and properties used in the DBpedia data set.\n            ".freeze,
       "dc:issued": "2008-11-17T12:00Z".freeze,

data/lib/rdf/vocab/dcat.rb

@@ -9,8 +9,8 @@ module RDF::Vocab
   #   # The data catalog vocabulary
   #   #
   #   # DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation. DCAT is defined at http://www.w3.org/TR/vocab-dcat/. Any variance between that normative document and this schema is an error in this schema.
-  #   # @version Questa è una copia aggiornata del vocabolario DCAT v2.0 disponibile in https://www.w3.org/ns/dcat.ttl
   #   # @version This is an updated copy of v2.0 of the DCAT vocabulary, taken from https://www.w3.org/ns/dcat.ttl
+  #   # @version Questa è una copia aggiornata del vocabolario DCAT v2.0 disponibile in https://www.w3.org/ns/dcat.ttl
   #   class DCAT < RDF::StrictVocabulary
   #     # A curated collection of metadata about resources (e.g., datasets and data services in the context of a data catalog).
   #     # @return [RDF::Vocabulary::Term]
@@ -24,7 +24,7 @@ module RDF::Vocab
   #     # @return [RDF::Vocabulary::Term]
   #     attr_reader :DataService
   #
-  #     # A collection of data, published or curated by a single source, and available for access or download in one or more represenations.
+  #     # A collection of data, published or curated by a single source, and available for access or download in one or more representations.
   #     # @return [RDF::Vocabulary::Term]
   #     attr_reader :Dataset
   #
@@ -133,9 +133,9 @@ module RDF::Vocab
   #     # @return [RDF::Vocabulary::Term]
   #     attr_reader :service
   #
-  #     # minimum spatial separation resolvable in a dataset, measured in meters.
-  #     #
   #     # minimum spatial separation resolvable in a dataset, measured in metres.
+  #     #
+  #     # minimum spatial separation resolvable in a dataset, measured in meters.
   #     # @return [RDF::Vocabulary::Term]
   #     attr_reader :spatialResolutionInMeters
   #
@@ -238,7 +238,7 @@ module RDF::Vocab
           "foaf:name": "John Erickson".freeze
         )],
       "dc:license": "https://creativecommons.org/licenses/by/4.0/".freeze,
-      "dc:modified": ["2012-04-24".freeze, "2013-09-20".freeze, "2013-11-28".freeze, "2017-12-19".freeze, "2019".freeze],
+      "dc:modified": ["2012-04-24".freeze, "2013-09-20".freeze, "2013-11-28".freeze, "2017-12-19".freeze, "2019".freeze, "2020-11-30".freeze],
       editorialNote: "English language definitions updated in this revision in line with ED. Multilingual text unevenly updated.".freeze,
       "foaf:maker": term(
           "foaf:homepage": "http://www.w3.org/2011/gld/".freeze,
@@ -293,12 +293,13 @@ module RDF::Vocab
         )],
       type: "owl:Class".freeze
     term :Dataset,
-      comment: "A collection of data, published or curated by a single source, and available for access or download in one or more represenations.".freeze,
+      comment: "A collection of data, published or curated by a single source, and available for access or download in one or more representations.".freeze,
       definition: "A collection of data, published or curated by a single source, and available for access or download in one or more represenations.".freeze,
+      editorialNote: "2020-03-16 A new scopenote added and need to be translated".freeze,
       isDefinedBy: "http://www.w3.org/TR/vocab-dcat/".freeze,
       label: "Dataset".freeze,
       "skos:changeNote": "2018-02 - subclass of dctype:Dataset removed because scope of dcat:Dataset includes several other types from the dctype vocabulary.".freeze,
-      "skos:scopeNote": ["This class describes the conceptual dataset. One or more representations might be available, with differing schematic layouts and formats or serializations.".freeze, "This class represents the actual dataset as published by the dataset provider. In cases where a distinction between the actual dataset and its entry in the catalog is necessary (because metadata such as modification date and maintainer might differ), the catalog record class can be used for the latter.".freeze],
+      "skos:scopeNote": ["The notion of dataset in DCAT is broad and inclusive, with the intention of accommodating resource types arising from all communities. Data comes in many forms including numbers, text, pixels, imagery, sound and other multi-media, and potentially other types, any of which might be collected into a dataset.".freeze, "This class describes the conceptual dataset. One or more representations might be available, with differing schematic layouts and formats or serializations.".freeze, "This class represents the actual dataset as published by the dataset provider. In cases where a distinction between the actual dataset and its entry in the catalog is necessary (because metadata such as modification date and maintainer might differ), the catalog record class can be used for the latter.".freeze],
       subClassOf: "dcat:Resource".freeze,
       type: ["owl:Class".freeze, "rdfs:Class".freeze]
     term :Distribution,
@@ -333,7 +334,7 @@ module RDF::Vocab
       editorialNote: "Introduced into DCAT to complement prov:Role (whose use is limited to roles in the context of an activity, as the range of prov:hadRole).".freeze,
       label: "Role".freeze,
       "rdfs:seeAlso": "dcat:hadRole".freeze,
-      "skos:changeNote": "New class added in DCAT 2.0.".freeze,
+      "skos:changeNote": ["New class added in DCAT 2.0.".freeze, "Ny klasse tilføjet i DCAT 2.0.".freeze],
       "skos:scopeNote": ["Used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the values be managed as a controlled vocabulary of agent roles, such as http://registry.it.csiro.au/def/isotc211/CI_RoleCode.".freeze, "Used in a qualified-relation to specify the role of an Entity with respect to another Entity. It is recommended that the values be managed as a controlled vocabulary of entity roles such as: ISO 19115 DS_AssociationTypeCode http://registry.it.csiro.au/def/isotc211/DS_AssociationTypeCode; IANA Registry of Link Relations https://www.iana.org/assignments/link-relation;  DataCite metadata schema;  MARC relators https://id.loc.gov/vocabulary/relators.".freeze],
       subClassOf: "skos:Concept".freeze,
       type: "owl:Class".freeze
@@ -363,7 +364,7 @@ module RDF::Vocab
       label: "bounding box".freeze,
       range: "rdfs:Literal".freeze,
       "skos:changeNote": "New property added in DCAT 2.0.".freeze,
-      "skos:scopeNote": "The range of this property is intentionally generic, with the purpose of allowing different geometry encodings. E.g., the geometry could be encoded with as WKT (geosparql:asWKT [GeoSPARQL]) or [GML] (geosparql:asGML [GeoSPARQL]).".freeze,
+      "skos:scopeNote": "The range of this property is intentionally generic, with the purpose of allowing different geometry encodings. E.g., the geometry could be encoded with as WKT (geosparql:wktLiteral [GeoSPARQL]) or [GML] (geosparql:asGML [GeoSPARQL]).".freeze,
       type: ["owl:DatatypeProperty".freeze, "rdf:Property".freeze]
     property :byteSize,
       comment: "The size of a distribution in bytes.".freeze,
@@ -389,7 +390,7 @@ module RDF::Vocab
       label: "centroid".freeze,
       range: "rdfs:Literal".freeze,
       "skos:changeNote": "New property added in DCAT 2.0.".freeze,
-      "skos:scopeNote": "The range of this property is intentionally generic, with the purpose of allowing different geometry encodings. E.g., the geometry could be encoded with as WKT (geosparql:asWKT [GeoSPARQL]) or [GML] (geosparql:asGML [GeoSPARQL]).".freeze,
+      "skos:scopeNote": "The range of this property is intentionally generic, with the purpose of allowing different geometry encodings. E.g., the geometry could be encoded with as WKT (geosparql:wktLiteral [GeoSPARQL]) or [GML] (geosparql:asGML [GeoSPARQL]).".freeze,
       type: ["owl:DatatypeProperty".freeze, "rdf:Property".freeze]
     property :compressFormat,
       comment: "The compression format of the distribution in which the data is contained in a compressed form, e.g. to reduce the size of the downloadable file.".freeze,
@@ -454,7 +455,7 @@ module RDF::Vocab
       domain: "dcat:DataService".freeze,
       label: "description of service end-point".freeze,
       "skos:changeNote": ["New property in DCAT 2.0.".freeze, "Nueva propiedad agregada en DCAT 2.0.".freeze],
-      "skos:scopeNote": ["An endpoint description may be expressed in a machine-readable form, such as an OpenAPI (Swagger) description, an OGC GetCapabilities response, a SPARQL Service Description, an OpenSearch or WSDL document, a Hydra API description, else in text or some other informal mode if a formal representation is not possible.".freeze, "The endpoint decription gives specific details of the actual endpoint instance, while dct:conformsTo is used to indicate the general standard or specification that the endpoint implements.".freeze],
+      "skos:scopeNote": ["An endpoint description may be expressed in a machine-readable form, such as an OpenAPI (Swagger) description, an OGC GetCapabilities response, a SPARQL Service Description, an OpenSearch or WSDL document, a Hydra API description, else in text or some other informal mode if a formal representation is not possible.".freeze, "The endpoint description gives specific details of the actual endpoint instance, while dct:conformsTo is used to indicate the general standard or specification that the endpoint implements.".freeze],
       type: "owl:ObjectProperty".freeze
     property :endpointURL,
       comment: "The root location or primary endpoint of the service (a web-resolvable IRI).".freeze,