Now that it's getting easier to track the unfinished parts of 43, this is one of the outstanding items.
Core resource definitions allow >1 value type [1] "A property MAY allow multiple value-types and a value MUST satisfy one or more of them.", but resource shapes permit only 1 value type [2] "oslc:valueType exactly-one". For "resource" Property shapes, the Resource value-types enumeration covers all the cases I can think of. For "literal" Property shapes, the Literal value-types enumeration lists 8 potential values, versus the single one allowed for an implementation on the Property's resource shape entry. I also don't see anything limiting a Property from allowing both literal and resource value types, although I have yet to see this capability used in practice. Is there any reason Core limits an implementation to a single value-type when it permits specifications wider latitude? [1] http://open-services.net/bin/view/Main/OslcCoreSpecification?sortcol=table;up=#OSLC_Defined_Resources [2] 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
