Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Talk:ALF/Vocabularies/Requirements Management/Event WSDL"

(Impacts and Links)
(Impacts and Links)
 
Line 8: Line 8:
  
 
eg: createRequirement would sent the Requirement as described by the Requirement schema type.  This save performing a getRequirement call.
 
eg: createRequirement would sent the Requirement as described by the Requirement schema type.  This save performing a getRequirement call.
 
== Impacts and Links ==
 
 
Impacts are not modeled yet since their defintion seems vague.  Links are modelled explictly although this does not seem to be the intent
 

Latest revision as of 20:24, 10 August 2007

Event Factoring

The eventsTypes are factored by the objectType, Requirement, Comment, Link and ChangeProposal

The detail data is minimal sending only the requirementId which is probably unecessary sin teh ObjectId Field in the base evetn will contain an ID that should be adequate.

And alternative would be to provide the Object Content in the Detail.

eg: createRequirement would sent the Requirement as described by the Requirement schema type. This save performing a getRequirement call.

Back to the top