[oslc-scm] One more change to closure syntax

[Nick Crossley]

Minor corrections to my last mail - I left out a matching 'foo' pattern in 
some of my examples:

In a provider implementing the full future syntax: 
foo{bar} would match nothing, or just foo if that property exists but is 
not a resource with a bar property, or foo and foo.bar if the foo property 
exists and is a link to a resource with a bar property 
foo?{bar} matches nothing, bar, foo, and foo.bar 
foo*{bar} matches nothing, bar, foo, foo.bar, foo.foo.bar, 
foo.foo.foo.bar, etc., without limit, 
foo+{bar} matches nothing, foo, foo.bar, foo.foo.bar, foo.foo.foo.bar, 
etc., without limit 
foo!{bar} matches nothing, bar, foo, foo.bar, foo.foo.bar, 
foo.foo.foo.bar, etc., up to some domain or provider specified limit or 
boundary 
foo!!{bar} matches nothing, bar, foo, foo.bar, foo.foo.bar, 
foo.foo.foo.bar, etc., up to a deeper domain or provider specified limit 
or boundary 
foo!!!{bar} matches nothing, bar, foo, foo.bar, foo.foo.bar, 
foo.foo.foo.bar, etc., up to an even deeper domain or provider specified 
limit or boundary

Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-scm_open-services.net/attachments/20100806/85ccd32d/attachment-0003.html>