[oslc-core] ANNOUNCEMENT: No OSLC Core meeting on July 7, 2010 + Some homework

[Dave]

We will not be meeting next week and will resume on Wednesday, July 14, 2010.

You can use the time to review the latest changes in the OSLC Core
guidance documents. I think the Link Guidance and Partial Update
Guidance are now mostly complete, but in need of wider review --  so
please, take a look. There have also been some small changes in the
OSLC Core spec, mostly wording and a couple of representation tweaks.


Here's a summary of recent changes:

*** Changes in Link Guidance
   http://open-services.net/bin/view/Main/OSLCCoreLinksDRAFT

- Now includes Jim's Reified Statement form of Anchor
- External Anchors now documented, also using Reified Statement
- JSON representations for Anchor and External Anchor


*** Changes in Partial Update
   http://open-services.net/bin/view/Main/OSLCCorePartialUpdateDRAFT

- Patch document is now a subset of SPARQL Update
- Refined list use cases supported to this:
   1. Adding property-values of any value-type
   2. Deleting property-values from a resource
   3. Updating values in a resource
- Limit partial update to one resource at a time
- Added some limitations on what providers are required to support
- Still need a content-type for patch document


*** Changes to OSLC Core spec
   http://open-services.net/bin/view/Main/OSLCCoreSpecDRAFT

- Changes to RDF/XML representation rules to use <rdf:RDF> as root
element of representations
- Wording changes in the OSLC Defined Resource section to clear up
confusion around name and type URI.
- Wording changes in Resource Paging section, replacing term "URL
parameter" with "query string key=value pair"
- Changes in the Resource Paging section so that <oslc:ResponseInfo>
is not an inlined property-value of the resource
- Changes to RDF/XML representation rules to represent
<oslc:ResponseInfo> when paging is in effect
- Example in Resource Paging section that shows a resource with
<oslc:ResopnseInfo>


Feedback is most welcome.

Thanks,
- Dave