This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
Date: 18 Feburary 2010
Time: 7:00 AM Pacific, 10:00 AM Eastern, 3:00 PM UK, 4:00 PM Frankfurt, 5:00 PM Haifa
Call In Number: (emailed)
Participation request: contact JimConallen

Agenda

  1. Quickly summarize points from last meeting.
  2. Continue to review the detailed scenarios. We will make sure that all the essential scenarios are covered.

Minutes

Atendees: Brenda Ellis, David Johnson, Thomas Piccoli, Jim Conallen

  1. Continued review of detailed scenarios.
  2. We discussed the required fields in the the ATOM results to queries. Dave pointed out some elements that are considered required by thee spec, but yet functioal without. Since we are defining the resource for clients we can omit ATOM required fields if necessary. Jim suggested that we include those ATOM required fields as part of the spec to make them eaiser to consume by commodity tools.
  3. David questioned the usefulness of the OSLC AM specific root element in the AM resource format. We concluded that the resource format was just as consumable with a generic RDF root element instead of the <oslc_am:Resource> one.
  4. We discussed the usefulness of OSLC specific content types, and engaged in a conversation over content negotiation in AM resources.
  5. Brenda raised concerns that the form of the AM resource might be different enough to hinder adoption across domains. Jim reassured the team that the nature of differences we are looking at here for the 1.0 generation of specifications was insignificant, compared to the overall picture of integration.
Topic revision: r2 - 03 Mar 2010 - 21:57:19 - JimConallen
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback