| 00000 |
Caching versioned resource when passing config context in header |
Sarabura, Martin
|
2016-05-10 22:16 |
| 00001 |
Re: [oslc-ccm] Caching versioned resource when passing config context in header |
David Honey
|
2016-05-11 08:36 |
| 00002 |
Re: [oslc-ccm] Caching versioned resource when passing config context in header |
Nicholas Crossley
|
2016-05-11 12:52 |
| 00003 |
Version Control Commit by ndjc |
[email protected]
|
2016-05-18 03:41 |
| 00004 |
[OASIS Issue Tracker] (OSLCCCM-20) Should a config management service provider indicate the types of configuration items it selects? |
OASIS Issues Tracker
|
2016-05-18 04:03 |
| 00005 |
[OASIS Issue Tracker] (OSLCCCM-3) Write RFC and apply to IANA to register Configuration-Context header |
OASIS Issues Tracker
|
2016-05-18 04:05 |
| 00006 |
[OASIS Issue Tracker] (OSLCCCM-4) Consider whether query strings need any form of registration |
OASIS Issues Tracker
|
2016-05-18 04:05 |
| 00007 |
[OASIS Issue Tracker] (OSLCCCM-13) Clarify correct and incorrect use of configuration context |
OASIS Issues Tracker
|
2016-05-18 04:07 |
| 00008 |
[OASIS Issue Tracker] (OSLCCCM-6) Write a primer for OSLC Configuration Management |
OASIS Issues Tracker
|
2016-05-18 04:07 |
| 00009 |
[OASIS Issue Tracker] (OSLCCCM-7) Provide details on location headers and other link headers returned from each operation |
OASIS Issues Tracker
|
2016-05-18 04:07 |
| 00010 |
[OASIS Issue Tracker] (OSLCCCM-5) Error conditions and status codes need to be described in the Configuration Management draft spec |
OASIS Issues Tracker
|
2016-05-18 04:07 |
| 00011 |
[OASIS Issue Tracker] (OSLCCCM-11) Some form of subscription and/or update notification may be required |
OASIS Issues Tracker
|
2016-05-18 04:07 |
| 00012 |
[OASIS Issue Tracker] (OSLCCCM-16) Document the CCM use cases and how the CCM capabilities support them |
OASIS Issues Tracker
|
2016-05-18 04:09 |
| 00013 |
[OASIS Issue Tracker] (OSLCCCM-19) Resource shapes for versioned type systems |
OASIS Issues Tracker
|
2016-05-18 04:09 |
| 00014 |
[OASIS Issue Tracker] (OSLCCCM-21) Provide a way for a client to discover the default configuration for a given configuration provider |
OASIS Issues Tracker
|
2016-05-18 07:32 |
| 00015 |
[OASIS Issue Tracker] (OSLCCCM-22) CLONE - Provide a way for a client to discover the default configuration for a given configuration provider |
OASIS Issues Tracker
|
2016-05-18 07:34 |
| 00016 |
Version Control Commit by ndjc |
[email protected]
|
2016-05-18 07:47 |
| 00017 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-05-18 07:51 |
| 00018 |
OASIS OSLC CCM TC meeting this week |
Nicholas Crossley
|
2016-05-18 08:01 |
| 00019 |
[OASIS Issue Tracker] (OSLCCCM-17) Potential confusion about oslc_config:previousBaseline |
OASIS Issues Tracker
|
2016-05-19 13:59 |
| 00020 |
[OASIS Issue Tracker] (OSLCCCM-19) Resource shapes for versioned type systems |
OASIS Issues Tracker
|
2016-05-19 13:59 |
| 00021 |
[OASIS Issue Tracker] (OSLCCCM-16) Document the CCM use cases and how the CCM capabilities support them |
OASIS Issues Tracker
|
2016-05-19 14:01 |
| 00022 |
[OASIS Issue Tracker] (OSLCCCM-21) Provide a way for a client to discover the default configuration for a given configuration provider |
OASIS Issues Tracker
|
2016-05-19 14:04 |
| 00023 |
[OASIS Issue Tracker] (OSLCCCM-21) Provide a way for a client to discover the default configuration for a given configuration provider |
OASIS Issues Tracker
|
2016-05-19 14:04 |
| 00024 |
[OASIS Issue Tracker] (OSLCCCM-19) Resource shapes for versioned type systems |
OASIS Issues Tracker
|
2016-05-23 13:01 |
| 00025 |
Version Control Commit by jamsden |
[email protected]
|
2016-05-26 18:13 |
| 00026 |
Version Control Commit by jamsden |
[email protected]
|
2016-05-26 18:13 |
| 00027 |
Please review Change Management drafts for vote this week |
Nicholas Crossley
|
2016-05-31 16:04 |
