OSLC Core Meeting May 4, 2011

Previous meeting

Link to OSLC Core spec: OslcCoreSpecification

Meeting logistics

How to dial-in to our telecon and login to our screen-sharing session.

Telecon Info

• USA Toll-Free: 888-426-6840
• USA Caller Paid: 215-861-6239
• Participant Code: 6867265#

• Other numbers:
  • https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6867265&accessNumber=2158616239

Online meeting

(if we need it)

• 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

• Specification Status
  • Reference to incomplete Partial Udpate guidance removed from spec
  • Fix to inlined-properties example at end of Link Guidance
  • OSLC-RM v2 specification now FINAL
  • OSLC-QM v2 will be FINAL once RDFS vocabulary document in place

• Community News and Status
  • Help wanted with OSLC Tools planning and execution
    • Email to OSLC Tools dev list with roadmap ideas
  • Help wanted with OSLC website planning and execution
    • oslc-core: Ideas for improving Open-Services.net website
  • Progress on OSLC Tutorial
    • There is a new section in Part 1 about POST to create
    • And Part 2 with accompanying Bugzilla Adapter is nearing completion
    • https://docs.google.com/document/pub?id=168GlmdArN5vn2j_yu5eyMEv0Krm_xJHvfTYhdV0A0fA
  • OSLC-related activities at Rational's Innovate 2011 conference

• Next steps
  • Comeback on Baselining? Change Log?

Minutes

Attendees and notes from the meeting

Attendees

Dave Johnson

Nick Crossley

John Arwe

(Regrets from Jim Conallen)

(Regrets from Ian Green)

Topics discussed

(short meeting due to low attendance)

Nick: I'm wrapping up a new revision of the Baseline proposal based on feedback from previous workgroup review, e.g. being more aggressive about handling cross domain links. I would like to schedule two sessions to wrap up the work, possibly May 18th and May 25th, but I worry that workgroup members may be too busy with Innovate 2011 conference prep.

Dave: I will put the Baselines proposal on the schedule for May 25th and notify the workgroup mailing list.

Nick: Do you see Baselines as a standalone spec, or something that is part of OSLC Core v3?

Dave: I think it can and should be a standalone spec, similar to the Reporting spec which tells OSLC implementations which parts of OSLC must be supported if reporting is to be supported. Do we know if Baselining can be done solely in terms of what we have defined in v2 or do we need v3 ideas?

Nick: Baselines does call out to the (incomplete) Partial Update guidance, and that could be removed, but clients will really want it. Being unable to update a Baseline could mean lots of extra work for clients.

John: I am aware of some implementations of the (un-complete) Partial Update spec, some taking slightly simpler approach of putting new properties rather than using SPARQL update syntax for every thing

Dave: I'm not sure how much time we will have for completing Partial Update this year; perhaps we need to figure out how to make it a priority

Action Items

AI: Dave to get baselines on May 18th agenda, inform workgroup