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.

OSLC Core Meeting May 26, 2010

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

Agenda

No prediction about length of meeting today.

First, I want to to bring everybody up to date on the current state of the spec, which is: all issues RESOLVED!

Here's a summary of the latest round of changes:

  • Created OSLC Query Syntax v.Next: this is a snapshot of the Query Syntax part of the OSLC Core spec as of sometime this morning, with all of the features including oslc.from, oslc.offset, etc. It may eventually become the OSLC Core Query Syntax specification.
  • Removed features from OSLC Query Syntax v2 spec To further simplify the already simple query syntax, we removed the oslc.from, oslc.limit and oslc.offset URL parameters.
  • Added Resource Paging back to Core spec Paging of any resource, and not just query resources, is now back in the Core spec, but clients must specifically request it via oslc.paging is true
  • Created OSLC Core Common Properties: this new document is intended to be a "living" registry of common properties used in OSLC resources. OSLC workgroups should consult this list before defining new properties.
  • Moved common properties out of Appendix A, leaving only Core properties Core properties are those that are defined in the Core spec or used in the Core spec.
  • De-emphasized namespace concept: 1) in the Service Provider resource we now refer to PrefixDefinitions? , 2) when defining a new resource you define a name and a URL and no namespace URI or type URI and 3) when defining a new property you define a name and a URI and no namespace URI or type URI.

And second, if we have time:

  • Partial Update Guidance: I've gotten more feedback about the Partial Fetch and Update guidance and my Partial Fetch scheme did not fare well. Instead, as mentioned above, we've added Resource Paging back into the spec. I got good feedback about Partial Update but also a recommendation that I take a second look at SPARQL Update.
  • [[OSLCCoreLinksDRAFT][Link Guidance]: A first draft of OSLC Core Guidance on Modeling Links is now available for review. It states what I hope are some platitudes about links and then lists the recommended common links, based on work from Steve Spiecher and Ian Green.
Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 25 May 2010 - 23:16:02 - DaveJohnson
 
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