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-82) Propose method for access context discovery


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

Nick Crossley commented on OSLCCORE-82:
---------------------------------------

I believe there are good arguments for separating the Access Context spec and vocabulary from the TRS spec - they use different namespaces anyway, and either one could be used without the other. If they are separate, we can debate the timeframe and requirements for Access Contexts more carefully.

> Propose method for access context discovery
> -------------------------------------------
>
>                 Key: OSLCCORE-82
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-82
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: TRS
>            Reporter: Martin Sarabura
>            Assignee: Axel Reichwein
>            Priority: Major
>              Labels: TRS
>
> Currently I believe we don't specify how to discover access contexts in our Tracked Resource Specification. We need to fill this gap.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)


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