[OASIS Issue Tracker] (OSLCCORE-121) Allow alternative skew resolution algorithms

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

     [ https://issues.oasis-open.org/browse/OSLCCORE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCORE-121:
-----------------------------------

    Proposal: 
Allow servers to resolve skew in whatever manner they choose. Add an informative note that a server should document their skew resolution algorithm, and that the algorithm should be predictable/repeatable.

Drop the explicit description of the lookup algorithms.

Future versions of the spec may choose to define specific algorithms once we have experience of them with real implementations.

  was:
Allow servers to resolve skew in whatever manner they choose. Add an informative note that a server should document their skew resolution algorithm, and that the algorithm should be predictable/repeatable.

Future versions of the spec may choose to define specific algorithms once we have experience of them with real implementations.


> Allow alternative skew resolution algorithms
> --------------------------------------------
>
>                 Key: OSLCCORE-121
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-121
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>
> In the current draft, a Config Mgmt server MUST provide a version resolution process using a first match in a depth-first search starting at the top of the configuration context, and MAY provide a way to find all matches.
> Neither of these two algorithms necessarily meets client needs. No implementations exist for the All Matches approach.
> The specification is overly precise, and its precision is not useful in this case.



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