On 9/30/10 11:45 AM, Alok Aggarwal wrote:
On Thu, 30 Sep 2010, Keith Mitchell wrote:
I chose "li" simply for example purposes (it's the HTML tag for a list item).
I think it'd make sense to have the tag imply 'list' somehow - value might be
confusing in that someone might try to use it for a checkpoint argument that
expects a single item:
<arg name="foo">
<value>bar</value>
</arg>
<!-- results in the checkpoint failing since it's expecting a string, not a
list -->
So a tag such as "list_item", or "li" or "list" or something of the sort might
be better. Alternatively, we could have separate <arg> and <arglist> tags.
<arg> would not have any subelements, and <arglist> would allow subelements
(<value> or <item>). That would probably be easier to define in the schema, as
well.
<arg name="foo">bar</arg>
<arglist name="foo_list">
<item>bar1</item>
<item>bar2</item>
</arglist>
I actually like the <arglist> specification better. That
way, <arg> is always a single value and in the cases a list
is expected <arglist> is used. And, it is infact clearer to
define in the schema as well.
I'm going to go with that unless anyone objects.
I like this approach as well but I'd prefer the use of <name/> instead of
<item/> or even <file/> so that it's clear that this is a list of files that
will not be compressed.
(just my $0.02) :)
-evan
Alok
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
