[gin-info] Possible list of subset data for info interop

[Jennifer M. Schopf]

The first step (what was decided at the meeting, not what was initially 
proposed, for clairifcation) was to get everyone to publish a little bit of 
common data as defined by a set of attributes, using their own schemas. 
There are many schema-agnostic tools that can pick this up and display it, 
the PRAGMA tool was mentioned as a possibility, or likely the MDS4 WebMDS 
interface could be altered slightly to do this.

(as an aside -  I've written up some notes from the meeting - general ones, 
not about info directly - would it be helpful for people here if i posted 
them?)

Second step may be a common schema, but probably not. More likely a way to 
translate between the schemas to allow a broker to translate what the data 
is.  The agreed on goal was data to allow resource selection as a first 
step. We didn't get as far as agreeing on a second step.

TG uses MDS4 which uses the GLUE schema when it can, and the 
project-specific extensions for that data where it makes sense. But, as you 
say, that's separate from the GIN work.

  -j


At 18:45 01/03/2006, Oxana Smirnova wrote:
>I see; so shall we just pick up these values from wherever they sit in our 
>own schemas and dump them somewhere in a flat list? Fine by me, but what's 
>the use of it? To make nice HTML tables?
>
>Also, regardless of GIN activities, shouldn't TG be planning for a schema?
>
>Oxana
>
>Jennifer M. Schopf пишет:
>>but guys, we're NOT defining a schema
>>we're saying -here's a minimal set of attributes which we think most 
>>sites are already gathering that we should communicate out
>>  -j
>>
>>At 18:02 01/03/2006, Oxana Smirnova wrote:
>>
>>>... right, that's another point I forgot to mention in my previous mail:
>>>
>>>- it would be very useful to see the inter-dependencies and/or relations 
>>>of the objects/classes, like e.g. an LDAP DIT.
>>>
>>>So Thomas' sketches are very helpful in getting the overview and 
>>>idetifying missing or redundant items.
>>>
>>>Oxana
>>>
>>>Dr. Thomas Soddemann пишеÑ‚:
>
>>>
>>>>Jen,
>>>>well, in order to get a consistent picture of we want as a kind of 
>>>>minimum requirements for a schema, I think it is by far more easy to 
>>>>use a structured visualization including dependencies of classes rather 
>>>>than gathering lists of attributes. You certainly agree, that 
>>>>unstructured information is almost worthless.
>>>>Hence, as implementors we should try to advertise our minimum set of 
>>>>attributes in way which makes sense to everyone. IMHO, that is more 
>>>>than just gathering lists of attributes. And in your first e-mail 
>>>>message you have already started to structure your data, which I later 
>>>>tried to visualize.
>>>>Cheers,
>>>>Thomas
>>
>>Dr. Jennifer M. Schopf
>>Scientist                              eInfrastructure Policy Advisor
>>Distributed Systems Lab       National eScience Centre and JISC
>>Argonne National Laboratory  The University of Edinburgh
>>jms at mcs.anl.gov                 jms at nesc.ac.uk
>>http://www.mcs.anl.gov/~jms http://homepages.nesc.ac.uk/~jms


Dr. Jennifer M. Schopf
Scientist                              eInfrastructure Policy Advisor
Distributed Systems Lab       National eScience Centre and JISC
Argonne National Laboratory  The University of Edinburgh
jms at mcs.anl.gov                 jms at nesc.ac.uk
http://www.mcs.anl.gov/~jms http://homepages.nesc.ac.uk/~jms