| Re: Re[2]: [higgins-dev] IdAS update proposals |
|
>>> Valery Kokhan <vkokhan@xxxxxxxxxxxxxx> 4/16/07 3:14 PM >>>
>Jim, > >See in-line. > >-- >Thanks, > >Valery > <snip> >> I think I see what you're asking. My intent was that it would >> return an IAttribute instance which had neither a type, nor any >> values. We could optionally or also make addAttribute take a type >> argument so that the returned IAttribute has a type associated with it. >> >As for me an IAttribute which has neither a type, nor any values is >useless because in this case we don't have any way to find out what >values it could contains at all. The thought was that the user would call addAttribute to create a new IAttribute. Next, the user can call something like IAttribute.setType(URI). Alternately, we could say the user always passes the either the type or an IAttribute to addAttribute. Then the user would never have a typeless attribute.
>>What we could is to define two methods: > >IAttribute addAttribute(URI type, ...); >IAttribute addAttribute(IAttribute attr, ...); > >In this case the first method will create, add and return newly added >IAttribute while the second will create, add, make a deep copy of attr >parameter and returns newly added IAttribute. I shouldn't type before I read :) I agree with the above (assuming we're thinking of the same trailing arguments). I'll update the wiki with this. |