OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (XDI-11) 3.4.1 - Clarification


    [ https://issues.oasis-open.org/browse/XDI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40666#comment-40666 ] 

Joseph Boyle  commented on XDI-11:
----------------------------------

Q1: It's saying, we can say that an XDI address must start with a root, because if there isn't an explicit other root in parens, we can consider that there is an initial zero-length string which can be interpreted as the common root.

In a Unix or HTTP path, the / character is both root symbol and term separator, but in XDI the context symbols =+*! or "context function" delimiters ()[]<>{} are enough to function as term separators, while / is used to separate the addresses of a triple or inner root instead. (can we refer to them as "pairs"?). 

In a Unix path you indicate it's a relative path (starting from sessions's current directory, instead of an "absolute path" starting from root) by omitting the root symbol /. In XDI you would instead indicate a path starts somewhere other than common root, by explicitly including one or more parenthesized root expressions before the rest of the address. 

Q2: It is addressable as empty string, per first sentence. In a statement or inner root, the slashes and parentheses separate the slots, so that an empty slot is possible.


> 3.4.1 - Clarification
> ---------------------
>
>                 Key: XDI-11
>                 URL: https://issues.oasis-open.org/browse/XDI-11
>             Project: OASIS XRI Data Interchange (XDI) TC
>          Issue Type: Task
>          Components: XDI Core
>    Affects Versions: 1.0
>            Reporter: Hubert Le Van Gong
>            Assignee: Hubert Le Van Gong
>
> "The XDI address of the common root node is the empty address. Thus any XDI statement that does not begin with a peer root address or an inner root address is by definition relative to the common root node."
> Q1: does this imply that such statement (per 2nd sentence) has an empty address?
> Q2: as I read this, I wondered how the 2nd sentence doesn't contradict the 100% addressability goal (for the object node)? 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]