RE: DATATYPES: mental dump.

> x learnedToCountUpTo http://www.w3.org/2001/XMLSchema#integer:10

No. You wouldn't express it that way. URV's don't themselves
contain the data type URIs but map to them. I.e.:

You would express it as

  x learnedToCountUpTo <xsd:integer:10>.

and from the definition defined in the schema for
the 'xsd:' URV schema

  <xsd:integer> lit:mapsTo http://www.w3.org/2001/XMLSchema#integer .

implies

  x learnedToCountUpTo _:1 .
  _:1 rdf:value "10" .
  _:1 rdf:type http://www.w3.org/2001/XMLSchema#integer .


And if you had two statements

  x learnedToCountUpTo <xsd:integer:10>.
  y ageInYears <xsd:integer:10> .

Then your graph would be

   x --learnedToCountUpTo---> <xsd:integer:10>
                                  ^
                                  |
   y --ageInYears------------------

But the interpretation would be

  x learnedToCountUpTo _:1 .
  _:1 rdf:value "10" .
  _:1 rdf:type http://www.w3.org/2001/XMLSchema#integer .
  y ageInYears _:2 .
  _:2 rdf:value "10" .
  _:1 rdf:type http://www.w3.org/2001/XMLSchema#integer .

Thus, it is the object slot of the triple that denotes the
value, not the graph entity filling the slot.

Using URVs allows for far more graph nodes to be tidy and
thus results in a far more compressed graph, but they
are only a more concise, compressed "synonym" for the idiom

   x someProperty _:1 .
   _:1 rdf:value "someLiteral" .
   _:1 rdf:type   some:type .

Is that clearer?

Patrick