[MOBY-dev] rfcf 12. Services

[Paul Gordon]

I absolutely agree on (b).  Anonymous data members is crazy.

For (a) I would say that articleNnames should be manditory if there is 
more than one parameter.  You could make a lot fancier rules, but you 
start dealing with a lot of parameter ambiguity issues.  It's easier to 
just require them if there is any question.  This would be a very minor 
change, since I don't think that there are many services that take more 
than one parameter, are there?  All of the simple one-parameter services 
would still be valid.

>>>a. should article names for service instance input and
>>>output datatypes be mandatory?
>>>      
>>>
>>Well, in my opinion, I think they should be mandatory when there is more
>>than one input (or output).
>>
>>    
>>
>   This question hides actually two situations: a) article names for 
>inputs (or outputs), and b) article names for elements attached by HAS[A] 
>relationships.
>   For b) situation I would say hat the article name should be mandatory,
>because one never knows who is going to extend his object and add new
>attributes. Having it mandatory will make life (and verification) easier. 
>Also, it will help to understand what individual HASA attributes mean if 
>they have an article name.
>   For a) situation it is not that crucial, I would say. But I know that
>INB people will come with a suggestion how to handle errors in a new way,
>and for their solution the article names are important (if I remember it
>correctly). And a similar situation may appear again in the future. And
>because having article names mandatory is not hard to do (and if your 
>current services do not do it, it will not break them, only some verifiers 
>may complain) I am inclined to say make them mandatory.
>
>   Regards,
>   Martin
>
>  
>