Quantum Jim's Journal: URI References and data: URI strings

Not to overload sw@w3, I'm going to propose answers to my questions on URI References in RDF. Any comments are greatly welcomed, since I don't know if I am correct!

1) RDF describes URI references - not URI strings themselves - in anticipation of IRIs (AKA a 'URIRef') URIRefs are always encoded in UTF-8 too. Correct?

Correct. (of course ;-)

2) My main question concerns converting a URIRef into a URI. Say we have the URIRef:

<data:,Hello, World>

Is that legal? Would that be converted into the URI:

<data:,Hello%2C%20World>

Since the comma is illegal in the URI after the first one?

Not entirely. The comma is legal in both the context and in RDF, so that URIRef would properly be converted to the URI:

<data:,Hello,%20World>

Note that I think (hope) that only the RDF semantics section applies and not the context in the scheme.

3) If there was an ambigious situation, how would it be represented as an URIRef? For example take the URI (yes, it is an unusual case where the name contains a slash - it is just an example):

<http://example.com/name%2Fslash/>

Would that be converted to the URIRef:

<http://example.com/name/slash/>

(I don't think so). But wouldn't the URIRef:

<http://example.com/name%2Fslash/>

be converted to the URI:

<http://example.com/name%252Fslash/>

That is all true, so the URI:

<http://example.com/name%2Fslash/>

Can not be represented as a URIRef. However that's not a problem, even though that means the scope of URIRefs is smaller than the scope of URI strings. RDF concerns URIRefs and not URI strings. So this is a non issue.