Now that it's getting easier to track the unfinished parts of 43, this is one of the outstanding items.
Resource shape [1] has a mismatch between oslc:range 0:* and oslc:valueShape 0:1 (not 0:*) Is there any reason to allow an implementation to assert that it supports a range of >1 resource types, but restrict it to exposing a valueShape for only one of them? [1] http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA?sortcol=table;up=#oslc_ResourceShape_Resource Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario
