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: 5 Aug 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. Update the workgroup on Core 2.0 Status.
  2. Address any open issues on AM 2.0 specification.
  3. Continue work on new scenarios.

Minutes

Atendees:Tom Piccoli, Bob Maksimchuk, Sandeep Kohli, Scott Bosworth, Ian Green, Jim Conallen

  1. After some disucssion we agreed that query capability should be a MUST requirement. For service implementors that do not implement it fully, they will just have to document that in their application. The delegated UI selector is a SHOULD requirement.
  2. Scott said that sometime in Q4 the core will be implementing test suites on specifications.
  3. We agreed that we would not require Atom responses in queries, since we only state a requirement to support RDF/XML. Scott also wanted us to be clear that RDF/XML support means that clients are expected to accept any valid RDF/XML response. Jim mentioned that in the samples document there is an example of a resource with two different yet equivalent RDF/XML responses.
  4. Ian pointed out that we may want to include text in the specification that explicitly says that RDF/XML resources begin with an outer rdf:RDF element.
  5. Sandeep brought up a question regarding the automated discovery of which optional parts of the specification an implementer has implemented. This idea was tabled, as it is something that the core group would need to discuss, not this domain specific workgroup.
Topic revision: r2 - 05 Aug 2010 - 15:37:14 - 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