From: SourceForge.net <no...@so...> - 2006-11-15 08:50:04
|
Feature Requests item #1596758, was opened at 2006-11-15 03:10 Message generated for change (Comment added) made by kal_ahmed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391882&aid=1596758&group_id=27895 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: Next Release (example) Status: Open Priority: 3 Private: No Submitted By: Ichiro Furusato (ifurusato) Assigned to: Nobody/Anonymous (nobody) Summary: support subjectIndicatorRef in parameters Initial Comment: currently the Variant interface includes an addParameter(Topic) method, but XTM 1.0 also permits <subjectIndicatorRef> elements as children of <parameters>, so there should probably be an addParameter(Locator) method in the API as well. Calls to this method would add a Locator instead of a Topic. When one doesn't want to reify the subject of the parameter (such as XTM 'Display') as a Topic, this would be welcome. ---------------------------------------------------------------------- >Comment By: Kal Ahmed (kal_ahmed) Date: 2006-11-15 08:50 Message: Logged In: YES user_id=176992 Originator: NO My feeling is that the underlying data model should keep all parameters as topics, otherwise it gets messy for a programmer calling getParameters to have to deal with a list of Topic and Locator objects. However, a convenience method addParameter(Locator l) could operate as follows: 1) Find a topic with subject identifier l. If found add that topic as a parameter otherwise, 2) Find a topic with source locator l. If found add that topic as a parameter otherwise, 3) Create a new topic and add l as a subject identifier then add that topic as a parameter. (Note that step (2) is required because a topic T with subject identifier L will merge with a topic T with source locator L under topic map merging rules, so if you didn't do that step then step (3) would create a topic which would instantly get merged). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391882&aid=1596758&group_id=27895 |