[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri-editors] Interpretation of "relative XRIs"
That’s an interesting question. The way I read the normative rules in 2396, it would actually resolve to xri:@foobar, but the example in appendix C makes it clear that the desired result is xri:@foo/bar.
To answer your question, though, the proposed text I’m submitting would always append after a “/”, never after a “.”. I’m glad you brought this up because it’s fairly important to understand so that dot segments are used sanely in a base XRI. Take this example.
Base: xri://www.foo.com/a.b.c Relative reference: d.e.f Resolved XRI: xri://www.foo.com/d.e.f
Base: xri://www.foo.com/a/b/c Relative reference: d.e.f Resolved XRI: xri://www.foo.com/a/b/d.e.f
Another point to note (and that naturally follows) is that . and .. move up slash delimited segments, not dot delimited segments.
Dave
-----Original Message-----
I'd really like the 2396 interpretation to be the case. I just wanted to make sure.
So the * gcs really is the "use default naming authority" and the relative xri form is really the 2396 meaning, which I interpret (like you) to basically mean that to get a "non-relative" xri from a relative XRI, you syntactically append something before the relative XRI. Where that "something" comes from is defined generally in 2396 (but ends up depending on how you got the relative XRI in the first place).
Great, fine. Just needed clarification and amplification. I want this specifically said in the spec!
-Gabe
P.S. Why would "xri:@foo" + "bar" make "xri:@foo/bar" ? Why not "xri:@foo.bar"? Is the insertion of the "/" specified in 2396?
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]