[Oslc-pm] spec updates

[John Arwe]

Following updates now live - note 2 questions raised as well.

Compliance table: fixed internal links on rows with query capabilities and 
query syntax; they had been pointing to the compliance table.
Namespaces: added table of those we use
Clarified that outgoing link targets can be anything not just oslc domain 
resources.

We've got a stray MUST in the guidelines section, which is bound to 
confuse people (guidelines are intended to be informative, so 
capital-musting will likely make people think we have a spec error).  We 
need to figure out what we want to say in here.

Changed dateTimeStamp into dateTime + a MUST on time zone, based on 
results of discussions with Core.  I can explain on the WG call if there 
are any questions.  From a provider's or consumer's point of view, it 
should be zero change, it's just a matter of where/how the requirement is 
levied.

Added 2 "Question to WG" points, you can just search on "WG" or look for a 
block of red text.
1: we talk about oslc.properties ... the text makes me think this is a 
leftover from Automation, and it may not apply to use.   .properties 
itself I would expect to be of limited usefulness on a PMR, since 
many/most of the predicates are going to be ems:observes.  oslc.select 
would be much more useful.

2: availability status has a conflict - the table says it's a reference 
(only - no in-line) but the paragraph below clearly says that in-line is 
also "valid" (allowed).  Not sure what the WG intent is.

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20121008/03db7298/attachment-0003.html>