[OASIS Issue Tracker] (XDI-4) Section 2.7 Protocol Expression and Transport Independence

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Joseph Boyle  commented on XDI-4:
---------------------------------

An XDI design principle was to consider the graph model as primary.

The XDI2 code deserializes a message to form a graph (not part of the main graph) then executes the message graph.

We have been discussing all messaging examples in serialization format (Display), which gives the impression this format is primary, but this impression is at variance with both design principle and current implementation.

> Section 2.7 Protocol Expression and Transport Independence
> ----------------------------------------------------------
>
>                 Key: XDI-4
>                 URL: https://issues.oasis-open.org/browse/XDI-4
>             Project: OASIS XRI Data Interchange (XDI) TC
>          Issue Type: Task
>          Components: XDI Core
>    Affects Versions: 1.0
>            Reporter: Hubert Le Van Gong
>            Priority: Minor
>
> "To make semantic data interchange as simple and extensible as possible, another XDI design goal is to define the XDI semantic data interchange protocol in XDI itself. This means all XDI messages must be valid XDI graphs, and all XDI data sharing operations are XDI graph merge operations."
> Comment: while this may indeed make interchange extensible, I think that defining messages with XDI graphs is *more* complicated and harder to understand. There are other ways than XDI graph based messages to achieve transport independence.
> Question: what is the motivation for XDI graph based messages?



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