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/Service WSDL"

("get" opeerations)
("get" opeerations)
Line 3: Line 3:
 
Impacts are not modeled yet since their defintion seems vague.  Links are modeled explictly although this does not seem to be the original intent.  This needs some discussion
 
Impacts are not modeled yet since their defintion seems vague.  Links are modeled explictly although this does not seem to be the original intent.  This needs some discussion
  
== "get" opeerations ==
+
== "get" operations ==
  
"get" operations were not described but will be necessary to get the object data for the objects that are raising events.  See getRequirement, getComment, getLink, getChangeProposal.  There is no getImpact since Impacts are not yet modeled.  Possibly theya re part of Links.
+
"get" operations are not described but will be necessary to get the object data for the objects that are raising events.  I have added these.  See getRequirement, getComment, getLink, getChangeProposal.  There is no getImpact since impacts are not yet modeled.  Possibly they are part of Links or vice-versa

Revision as of 20:32, 10 August 2007

Impacts and Links

Impacts are not modeled yet since their defintion seems vague. Links are modeled explictly although this does not seem to be the original intent. This needs some discussion

"get" operations

"get" operations are not described but will be necessary to get the object data for the objects that are raising events. I have added these. See getRequirement, getComment, getLink, getChangeProposal. There is no getImpact since impacts are not yet modeled. Possibly they are part of Links or vice-versa

Back to the top