Choice for Configuration context request headder (was: [oslc-core] Agenda for 15 May 2014)

[Steve K Speicher <sspeiche@us.ibm.com>]

(Side point: please change the subjects
of emails to match the subject of the discussion.  We all get way
too many emails to have to dig through to see what it is really about,
thanks.)

Also, this was associated with Ian's
assigned action from the May 15th meeting [1]

[1]: https://wiki.oasis-open.org/oslc-core/Meetings/Telecon2014.05.15#Configuration-ContextheaderfromNicksemail

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> http://open-services.net



From:      
 Ian Green1 <ian.green@uk.ibm.com>
To:      
 oslc-core@lists.oasis-open.org
Cc:      
 Nick Crossley/Irvine/IBM@IBMUS
Date:      
 05/15/2014 11:57 AM
Subject:    
   Re: [oslc-core]
Agenda for 15 May 2014
Sent by:    
   <oslc-core@lists.oasis-open.org>

---

This topic  was discussed on the
conf. call earlier today where John suggestion another option which is
to instead use a Link header with a rel which described the configuration
context. 

If we define a new http header, servers are able to use Vary header to
influence how caches deal with entries that are configuration-sensitive.
 for example: 

        Vary: X-OSLC-Configuration-Context

means that http caches should not use entries that have a different : X-OSLC-Configuration-Context
header value. 

Using Link header would be expressed as 

        Vary: Link 

But this has a broader scope since Link values have meaning outside of
CM.  I think has some bearing on the decision on whether or not to
use Link or mint a fresh header. 

best wishes,
   -ian

ian.green@uk.ibm.com (Ian Green1/UK/IBM@IBMGB)
IBM Rational 

<oslc-core@lists.oasis-open.org> wrote on 14/05/2014 19:28:42:

> From: Nick Crossley <ncrossley@us.ibm.com>
> To: oslc-core@lists.oasis-open.org 
> Date: 14/05/2014 19:29 
> Subject: Re: [oslc-core] Agenda for 15 May 2014
> Sent by: <oslc-core@lists.oasis-open.org>
> 
> Arnaud,
> 
> I am unable to attend tomorrow, since I am doing an eWeek 
> presentation at a local school.
> 
> I have one bit of other business: for OSLC Configuration Management,
> I need to propose a new standard http header, communicating the 
> configuration context to be used for the request. A question is 
> whether headers proposed by OSLC TCs should just use a bare name 
> that is relevant to the purpose, or whether they should have an OSLC
> prefix. For the OSLC Configuration Management context header, I am
> currently proposing the header 'Configuration-Context' - but should
> this be 'OSLC-Configuration-Context'? Existing practice does not,
in
> general, prefix each header with the organization proposing that header
- see 
> http://www.iana.org/assignments/message-headers/message-headers.xhtml.
> 
> Nick.
> 
> 
> [image removed] Arnaud Le Hors---05/14/2014 09:02:50 AM---Hi all,
> Here is the agenda for tomorrow's call:
> 
> From: Arnaud Le Hors/Cupertino/IBM@IBMUS
> To: oslc-core@lists.oasis-open.org
> Date: 05/14/2014 09:02 AM
> Subject: [oslc-core] Agenda for 15 May 2014
> Sent by: <oslc-core@lists.oasis-open.org>
> 
> 
> 
> Hi all, 
> Here is the agenda for tomorrow's call: 
> http://wiki.oasis-open.org/oslc-core/Meetings/Telecon2014.05.15
> 
> Meetings/Telecon2014.05.15   
> Event details 
> https://www.oasis-open.org/apps/org/workgroup/oslc-core/event.php?
> event_id=36376   
> New Call-in info: https://www.oasis-open.org/apps/org/workgroup/
> oslc-core/members/action_item.php?action_item_id=3688 (access 
> restricted to OASIS members) 
> Chat room: http://webconf.soaphub.org/conf/room/oslc
  
> Agenda   
> Roll Call 
> Approval of Minutes of 1 May 2014  
> Next call: 29 May 
> Namespaces for OSLC-affiliated TCs - Vocabulary URIs  
> Resource preview updates   
> Discuss Document and Specification Roadmap timetable: +2 months 
> delay (dealing with conferences and summary breaks) 
> Any other business 
> Adjourn 
> --
> Arnaud  Le Hors - Software Standards Architect - IBM Software
Group
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU