perfsonar development work

["Jeff W. Boote" <>]

So, there are two pieces here that we should talk about separately.

First, the 'temporary' solution to get lots of what we need in the  
short term is to use a 'keyword' parameter that is specifically a  
"word". If specific groups/users want to structure the value, they can  
do that. (i.e. "Project:LHC").

The second question is how we allow user defined 'discovery hints'  
long term.

I do not think we should be putting this inside parameters. If this is  
a general concept that we want to use throughout, I think it warrants  
a new element outside of parameters for the reasons outlined a few  
weeks ago on the email list.

jeff

On Jun 26, 2008, at 10:04 AM, Roman wrote:

> Martin Swany wrote:
> > Hi Verena,
> >
> > I think that what Jeff and I are referring to is more like
> >
> > <nmwg:parameter name="keyword" value="something meaningful"/>
> >
> > <nmwg:parameter name="discoveryHint">
> >    <project>
> >        Internet2-DCN
> >    </project>
> > </nmwg:parameter>
>
> I used to propose to have structures like a list or a map inside a  
> parameter. Maybe it would be worth to consider it again.
>
> <nmwg:parameters>
> <!-- list parameter -->
> <nmwg:parameter name="parameter_which_consists_of_list">
>   <list:item>value1</list:item>
>   <list:item>value2</list:item>
>   <list:item>value3</list:item>
> </nmwg:parameter>
> <!-- map parameter -->
> <nmwg:parameter name="parameter_which_consists_of_map">
>   <map:item name="name1">value1</map:item>
>   <map:item name="name2">value2</map:item>
>   <map:item name="name3">value3</map:item>
> </nmwg:parameter>
> </nmwg:parameters>
>
>
> example for keyword parameter:
>
> <nmwg:parameters>
> <nmwg:parameter name="keyword">
>   <map:item name="project">geant2</map:item>
>   <map:item name="status">test</map:item>
>   <map:item name="expiration">2009/01/01</map:item>
>   <!--
>   <map:item name="expiration">
>       <nmtm:time type="ISO" value="2009-01-01T10:40:00Z"/>
>   </map:item>
>   -->
> </nmwg:parameter>
> </nmwg:parameters>
>
>
> Roman
>
>
>
> > That needs some thought, but the point if that if we move beyond
> > a "key" "word", then we add structure to the parameter.
> >
> > best,
> > martin
> >
> > On Jun 26, 2008, at 12:55 PM, Verena Venus wrote:
> >
> > > Am Donnerstag, 26. Juni 2008 12:47 schrieb Martin Swany:
> > > > Hi Roman,
> > > >
> > > > > I agree, adding new attribute(s) to the parameter element is  
> > > > > risky.
> > > > > The pair name/value should rather be rigid. But in some situation
> > > > > more information for keywords would be very useful.
> > > >
> > > > Maybe we can agree that a keyword is really only a "key" "word"
> > > > and that we can discuss some more structured "discovery hints"
> > > > that would include things like "project" or "virtual organization".
> > > > This could still be a parameter, but might be a more structured
> > > > one.
> > >
> > > So, am I right that you are suggesting something like:
> > >
> > > <nmwg:parameter name="project" value="Internet2"/>
> > >
> > > and
> > >
> > > <nmwg:parameter name="keyword" value="something meaningful"/>
> > > ?
> > >
> > > Hmm, why not. Sounds reasonable :)
> > >
> > > Regards,
> > > Verena