[Oslc-Automation] spec typo? Either Reference or Inline phrase

[Michael F Fiedler]

I agree - the wording in the resource definition should match the
vocabulary.   I've updated the specification.

Regards,
Mike




                                                                           
             John                                                          
             Arwe/Poughkeepsie                                             
             /IBM at IBMUS                                                 To 
             Sent by:                  oslc-automation at open-services.net,  
             oslc-automation-b                                          cc 
             ounces at open-servi                                             
             ces.net                                               Subject 
                                       Re: [Oslc-Automation] spec typo?    
                                       Either Reference or Inline phrase   
             03/22/2012 08:07                                              
             AM                                                            
                                                                           
                                                                           
                                                                           
                                                                           




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 at IBMUS
To:        oslc-automation at open-services.net
Date:        03/21/2012 05:24 PM
Subject:        Re: [Oslc-Automation] spec typo? Either Reference or Inline
phrase
Sent by:        oslc-automation-bounces at open-services.net



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
fiedler at us.ibm.com
919-254-4170







_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net

_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net