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


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

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

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

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

Nick Crossley commented on OSLCCORE-121:

I have added text in the section on version resolution to require consistency from a provider. Jim, please review to see that meets your first point.

As for finding the alternatives, while there is no built-in operation for this, I do not believe one is needed. A user can at any time read the selection resources in a GC hierarchy and find which concept resources have multiple versions and where.

re avoiding skew - I do expect day-to-day practitioners to operate in unskewed environments most of the time, but any realistic representation of sufficiently large or complex systems must allow for the fact that skew does happen.

> 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

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