OASIS XRI Data Interchange (XDI) TCIcon indicating the project type

OASIS XRI Data Interchange (XDI) TC

Open issues

Order by Priority
Order by Priority
  1. New Feature
    XDI-29Versioning of XDI graph
  2. Task
    XDI-42Draft Variables section
  3. Task
    XDI-43Draft Core Relations section
  4. Task
    XDI-49Draft Appendix with Collected ABNF
  5. Task
    XDI-50Draft Appendix for XDI Context Symbol and Role Reference
  6. Task
    XDI-53Draft Introduction section
  7. Task
    XDI-52Draft Appendix with Example XDI Graph
  8. Task
    XDI-51Draft Appendix for XDI Keyword ($word) Reference
  9. Task
    XDI-48Draft Versioning section
  10. Task
    XDI-47Review Serialization section
  11. Task
    XDI-46Draft XDI Addressing section
  12. Task
    XDI-45Finalize ABNF section
  13. Task
    XDI-44Scrub ABNF
  14. Task
    XDI-133.4.3 Inner root nodes
  15. Task
    XDI-143.5 Subgraphs
  16. Bug
    XDI-39Zero operator policy
  17. Bug
    XDI-38Rework intro to policy expression pattern
  18. Bug
    XDI-40<Condition> is misleading
  19. Bug
    XDI-37Message -> Requested operation
  20. Bug
    XDI-36“An XDI message policy is part of the input message”
  21. Bug
    XDI-35Operational policies vs. data usage policies
  22. Bug
    XDI-34Policy Model - rework intro
  23. Bug
    XDI-33Controlling authority
  24. Bug
    XDI-32No one has access
  25. Bug
    XDI-31Unauthorized access operations vs. Unauthorized usage
  26. Bug
    XDI-183.5.3 Attributes
  27. Bug
    XDI-214.1 Literal Statements
  28. Bug
    XDI-234.3 $is
  29. Task
    XDI-173.5.2 Entities
  30. Task
    XDI-153.5.1 Variables
  31. Bug
    XDI-30Consider adding an Overview (non-normative) document to serve as an introduction
  32. Bug
    XDI-27Section 3 - XDI Display format
  33. Bug
    XDI-241 - Introduction
  34. Task
    XDI-163.5 subgraph example
  35. Bug
    XDI-252 - XDI Messaging
  36. Bug
    XDI-224.1 - inverse
  37. Bug
    XDI-283 - Clarify which statement is optional for which message type
  38. Bug
    XDI-262 - XDI Messaging (2)
  39. Task
    XDI-113.4.1 - Clarification
  40. Task
    XDI-63.2 - Literals
  41. Task
    XDI-93.4 Graph Root Nodes
  42. Task
    XDI-123.4.2 - references
  43. Task
    XDI-73 - The XDI Graph Model
  44. Task
    XDI-83.4 Graph Root Nodes
  45. Bug
    XDI-203.11.1 Reserved
  46. Bug
    XDI-193.5.4 Values - typo
  47. Task
    XDI-103.4.1 - The common root node
  48. Task
    XDI-5Section 3.3 - Contexts
  49. Bug
    XDI-41Typos
  50. Task
    XDI-42.7 Protocol Expression and Transport Independence
  51. Task
    XDI-32.4 - Persistent Identification
Refresh results
Uploaded image for project: 'OASIS XRI Data Interchange (XDI) TC'
  1. OASIS XRI Data Interchange (XDI) TC
  2. XDI-29

Versioning of XDI graph

    Details

    • Type: New Feature
    • Status: New
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: None
    • Component/s: XDI Core
    • Labels:

      Description

      Following a conversation about the notation shift, we need to discuss the need to support XDI-graph versioning.
      There is a version defined at the Messaging level but it is probably preferable to have a separate one for XDI graph definitions.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          hubert_levangong Hubert Le Van Gong (Inactive) added a comment - - edited

          To be clear, I'm talking about the versioning of the XDI standard, not versioning of data (e.g. collection).
          For instance to differentiate pre and post notation shift XDI standard.

          Show
          hubert_levangong Hubert Le Van Gong (Inactive) added a comment - - edited To be clear, I'm talking about the versioning of the XDI standard, not versioning of data (e.g. collection). For instance to differentiate pre and post notation shift XDI standard.
          Hide
          Permalink
          joseph Joseph Boyle (Inactive) added a comment -

          Pre-1.0 versions of the standard are identified by working draft number.

          Show
          joseph Joseph Boyle (Inactive) added a comment - Pre-1.0 versions of the standard are identified by working draft number.
          Hide
          Permalink
          hubert_levangong Hubert Le Van Gong (Inactive) added a comment -

          We still need to add versioning starting 1.0 (to prepare for subsequent releases).

          BTW how do we expect 2 implementations that use different pre-1.0 versions to interoperate...?

          Show
          hubert_levangong Hubert Le Van Gong (Inactive) added a comment - We still need to add versioning starting 1.0 (to prepare for subsequent releases). BTW how do we expect 2 implementations that use different pre-1.0 versions to interoperate...?
          Hide
          Permalink
          joseph Joseph Boyle (Inactive) added a comment -

          We've discussed this in TC meeting - if we can avoid having to support pre-1.0 versions that would be better.

          In any case I don't think this is a bug against the spec - it may be for XDI itself.

          Show
          joseph Joseph Boyle (Inactive) added a comment - We've discussed this in TC meeting - if we can avoid having to support pre-1.0 versions that would be better. In any case I don't think this is a bug against the spec - it may be for XDI itself.
          Hide
          Permalink
          hubert_levangong Hubert Le Van Gong (Inactive) added a comment -

          Isn't this a bug for 1.0 though?
          In other words, aren't we going to address graph versioning in 1.0?

          Show
          hubert_levangong Hubert Le Van Gong (Inactive) added a comment - Isn't this a bug for 1.0 though? In other words, aren't we going to address graph versioning in 1.0?
          Hide
          Permalink
          peter.davis Peter Davis (Inactive) added a comment -

          ED: to clarify the comment a bit, "We need a mechanism to express the version of the serialization and XDI graph model. I would expect this to have an initial value of 1.0". See proposed resolution in https://lists.oasis-open.org/archives/xdi/201407/msg00107.html

          Agree that Core should include details on how Graph and serialization version is expressed.

          Messaging will need additional material (esp. wrt messaging versions)

          Show
          peter.davis Peter Davis (Inactive) added a comment - ED: to clarify the comment a bit, "We need a mechanism to express the version of the serialization and XDI graph model. I would expect this to have an initial value of 1.0". See proposed resolution in https://lists.oasis-open.org/archives/xdi/201407/msg00107.html Agree that Core should include details on how Graph and serialization version is expressed. Messaging will need additional material (esp. wrt messaging versions)

            People

            • Assignee:
              peacekeeper Markus Sabadello (Inactive)
              Reporter:
              hubert_levangong Hubert Le Van Gong (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
              1 of 51