I think the usage in Automation is consistent with other specs [1] [2], including core. It does use AnyResource instead of "Either Resource or Local Resource", but the "Either Reference or Inline" is the same. The Core specification [3] states that the allowed values for representation for resources are
http://open-service.net/ns/core#Reference http://open-service.net/ns/core#Inline http://open-service.net/ns/core#Either The Automation specification can be updated to just say "Either" if there is agreement. [1] - http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA?sortcol=table;table=up;up=#Dublin_Core_Properties [2] - http://open-services.net/bin/view/Main/CmSpecificationV2?sortcol=table;up=#Resource_ChangeRequest [3] - http://open-services.net/bin/view/Main/OslcCoreSpecification?sortcol=table;table=up#OSLC_Defined_Resources Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170 John Arwe/Poughkeepsie /IBM@IBMUS To Sent by: [email protected], oslc-automation-b cc ounces@open-servi ces.net Subject [Oslc-Automation] spec typo? Either Reference or Inline phrase 03/20/2012 02:51 PM [1] has occurrences of the subject phrase. [2] assigns no meaning to "Inline" - appears it should be "Local Resource" instead [1] http://open-services.net/bin/view/Main/AutoSpecificationV1 [2] http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA?sortcol=table;table=up#oslc_ResourceShape_Resource Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
