OSLC Core Meeting December 1, 2010

Last week's meeting

Link to OSLC Core spec: OslcCoreSpecification

Meeting logistics

See the OslcCoreMeetings for more information, more dial-in numbers and on-line meeting information.

• Conference Access
  • Toll free: 1-866-423-8350
  • Toll: 1-719-387-8273
• Participant passcode: 558663

Online meeting:

• For IBM employees, use the following link:
  https://lli.ibm.com/meeting/join/?schedid=4446009 (IBM intranet authentication required)

• For people outside IBM, use the following link:
  https://apps.lotuslive.com/meetings/join?id=4446009

Agenda

• Issue: with the Use of dcterms:title and dcterms:description with oslc:ResponseInfo
  • http://open-services.net/pipermail/oslc-core_open-services.net/2010-November/000638.html
  • Martin pointed out that there is no problem here because of the oslc.paging=true URL query string key/value pair
• Issue: clarification needed for the oslc:totalCount property of a oslc:ResponseInfo type resource.
  • Not clear whether this is number of triples or number of resources (grouped triples) that match

• Proposed Schedule for Workgroup December 2010 - January 2011
  • Dec 1 - Discuss schedule. Check!
  • Dec 8 - Multi-typed resources, Jim Conallen
    • There will be cases where a resource is of multiple rdf:types but we have no guidance on how this situation should be handled. Jim will lead a discussion to explain the related scenarios, the open issues and his recommendations for Core and/or other Domain work-group activities around this topic.
  • Dec 15 - OSLC Primer, Dave Johnson
    • Consensus is that we need an approachable introduction for those new to OSLC, one designed for developers who understand web development but may be new to REST, HTTP, RDF and other foundational technologies. Dave will explain his proposed outline and seek feedback.
  • Jan 5 - Baselining, Nick Crossley
    • Baselining is an important topic in the PLM and other work-groups. There are different use cases and terminologies. Nick will explain the current situation and lead a discussion on how baselining should fit into the OSLC specs
  • Jan 12 - Comments / Discussions, Steve Speicher, John Vasta
    • The OSLC Core spec includes Comments and Discussion resources but they have not been widely adopted. Steve and John will cover the state of union in regard to comments/discussions and lead a discussion of options for moving forward.
  • Jan 19 - Test Suite, Steve Speicher
    • Test Suite code should be contributed by this time and Steve will explain what is there, how it works and lead a discussion of next steps for improving test coverage and consumability.
  • Jan 26 - Reference Implementation, Dave Johnson
    • OSLC RI code should be contributed by this time and Dave will explain what is there, how it works and lead a discussion of next steps for improving the RI implementation and consumability.
  • Feb 2 - Attachments (Dave Johnson)
    • We use a number of patterns for storing non OSLC defined resources (e.g. JAR files, images, video and Word processing files) and then annotating them with properties. Dave will explain the patterns in use and propose an outline for guidance on the topic.

• Proposed outline for OSLC Primer document
  • Any feedback before I flesh this out for next week?
  • http://open-services.net/bin/view/Main/OslcPrimer

Other issues for discussion

Got issues?

Minutes

Attendees and notes from the meeting

Attendees

• DaveJohnson
• NickCrossley
• ScottBosworth
• SteveSpeicher
• IanGreen

Topics discussed

• Topic: Paging clarifications
  • Consensus:
    • No need to remove oslc.paging
    • Give guidance on what service should do when page too large
  • Relevant implementation status:
    • Scott B: Only Rational Insight does paged resources
    • Ian G: RRC does as well
    • Scott B: RQM and RTC provide paged query responses, but not for "plain old" resources
  • AI: Dave J to propose spec changes
  • AI: Dave J to document each issue we've discussed, here are some:
    • ResponseInfo? URI
    • How and when should redirects be used in paging
    • Should clients have to request paging (as they do now in Core spec)
    • What should servers do when response is too large
  • Dave J: OSLC services MAY return partial representations via 302 redirect even when clients didn't ask for paging
  • Ian G: OSLC services MAY respond to requests that exceed size limits with partial representations, and if they do they MUST do it this way...
  • Dave J: concur

• Dave J: Need to clarify oslc:totalCount, total number of resources returned or total triples
  • Nick C: we meant "top-level resources" (and everybody agrees)
  • Dave J: top level resources is not defined. How about total number of "member property values"
  • Steve S: or triples where subject is query URI, predicate is member property and value is query result
  • Ian G: that would map to the SPARQL count of the query Steve just stated
  • Scott B: need to mention stable vs. unstable in the new text
  • AI: Dave to propose new text

• Topic: Schedule
  • Agreed to proposed schedule
  • AI: Dave to publicize to other work-groups