I see I went too quickly on the first attempt and conflated Value-type with Representation values. ugh, my bad.
> Automation specification can be updated to just say "Either" if there is agreement. I have a mild preference for doing that, purely for simplicity. The alternative is updating Core [3] to assign a meaning to the phrase Automation is currently using. The first choice is simpler because it avoids introducing the complexity of defining a new term of art. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario From: Michael F Fiedler/Durham/IBM@IBMUS To: [email protected] Date: 03/21/2012 05:24 PM Subject: Re: [Oslc-Automation] spec typo? Either Reference or Inline phrase Sent by: [email protected] 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 _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
