Mike, I guess I was making the assumption that the dcterms:creator would be carried through from either the request or the schedule that kicks off the request, a convenience so that consumers do not have to go back to the request to find out who started the automation process.
Regards, David ____________________________________________________ David Brauneis STSM, Rational Software Delivery Automation Chief Architect email: [email protected] | phone: 720-395-5659 | mobile: 919-656-0874 From: Michael F Fiedler/Durham/IBM@IBMUS To: [email protected], Date: 09/04/2012 08:15 PM Subject: [Oslc-Automation] dcterms:creator for Automation Result Sent by: [email protected] The current definition of Automation Result has a zero-or-many dcterms:creator predicate which is described as likely to be a FOAF Person. Does it make sense to have a creator for Automation Results which is described as likely to be a Person? Since the Result is most likely to be created by the service provider (or perhaps an agent/worker), should we keep it at all? or state it is likely to be the URI of the service provider itself? Any implementation feedback here? 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
