OSLC Core Meeting June 29, 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

• Workgroup changes
• OSLC Core v2 retrospecive
  • History of Core spec effort
    • January 2010: First draft written
    • Early issues and decisions
      • The "nothing protocol" just do HTTP, REST and Linked Data the right way
      • Should we base on Atompub protocol? No
      • Should we require RDF/XML? Yes
      • Use approach: define resources and rules for creating representations
    • February 2010: Core workgroup formed, draft spec introduced
    • March 2010: Series of 2 hour meetings to review spec
    • Preconvergence issues and decisions
      • Adopt "value types" of resource and local resource. Also, "representations" of reference and inline
      • Really need resource shapes? Yes
      • Do we need notion of a collection? No
      • Use XHTML for rich text
      • Cannot assume property values are in order
      • Use POST for executing query, with form-encoded parameters
      • Use our own JSON representation
    • April 2010: Core spec v2 converged
    • Convergence issues and decisions
      • Reviewed UI Preview, Link and Partial Update Guidance
      • How to do versioning? Version header, no breaking changes allowed
      • Query Syntax spec is too complex, so we drop oslc.from
      • Worried about Resource Shapes, so we "minimize" them, move them to appendix
      • Added Common Properties appendix
      • Continued work on Link Guidance, which becomes an appendix
      • RDF/XML subset will cause problems later, so we adopt "full" RDF/XML
    • July 2010: Core spec v2 entered finalization
    • May 2011: Core spec v2 final
  • Things that we deferred or tabled
    • Renaming for Response Info and paging properties
    • Formal BNF or ANTLR grammar for Query Syntax
    • Extended Properties
    • Ordered Resources
    • See also OslcCoreV3Issues?
  • Touch on key parts of Core spec
    • Glossary
    • OSLC Defined Resources
    • Service Providers
    • Creation Factories
    • Query Capabilties
    • Delegated UI
    • UI Preview
    • Authentication
    • Error Responses
    • Specification Versioning
    • OSLC Defined Resource Representations
    • Appendix A: Common Properties and Resources
    • Appendix B: Representation Guidance
    • Appendix C: Guidance on Links and Relationships

Minutes

Attendees and notes from the meeting

Attendees

TBD

Topics discussed

Things that we deferred or tabled

Renaming for Response Info and paging properties

Formal BNF or ANTLR grammar for Query Syntax

Extended Properties

Ordered Resources

Touch on key parts of Core spec*

Glossary

OSLC Defined Resources

Service Providers

Creation Factories

Query Capabilities

Delegated UI

UI Preview

Authentication

Error Responses

Specification Versioning

OSLC Defined Resource Representations

Appendix A: Common Properties and Resources

Appendix B: Representation Guidance

Appendix C: Guidance on Links and Relationships