Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: questions about the LS protocol

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: questions about the LS protocol


Chronological Thread 
  • From: Jason Zurawski <>
  • To: Maciej Glowiak <>
  • Cc: ulisses <>,
  • Subject: Re: [pS-dev] Re: questions about the LS protocol
  • Date: Fri, 28 Jul 2006 14:05:26 -0400




But I think Ulisses asked also why <metadata> is inside <data> element. Maybe you've already answered him, but I redirected him to you, because you will explain him it better ;-) I suppose the reason is in semantic difference between metadata (meta-description of data) and data.



I didn't notice that was the actual question from the first e-mail, I thought he was asking about each element in the interface.
The metadata element is inside of a data element because it is being submitted as data to the LS. For example we know that an MA has a certain service description (described here as metadata):


<nmwg:metadata id="serviceLookupInfo">
<perfsonar:subject id="commonParameters" xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/";>
<psservice:service id="serviceParameters" xmlns:psservice="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/1.0/";>
<!-- some description of service for an MA, or MP, or whatever -->
</psservice:service>
</perfsonar:subject>
</nmwg:metadata>


And the MA or MP allows access to certain metadata/data pairs:



<nmwg:metadata id="meta1">
<perfsonar:subject id="subj1" xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/";>
<!-- some description of an interface, or end point -->
</perfsonar:subject>
<nmwg:eventType>utilization</nmwg:eventType>
</nmwg:metadata>

<nmwg:data id="data1" metadataIdRef="meta1">
<!-- datum elements -->
</nmwg:data>


To properly submit this to the LS we send a service description and its 'data' (which is really just the metadata of other measurements):


<nmwg:metadata id="serviceLookupInfo">
<perfsonar:subject id="commonParameters" xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/";>
<psservice:service id="serviceParameters" xmlns:psservice="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/1.0/";>
<!-- some description of service for an MA, or MP, or whatever -->
</psservice:service>
</perfsonar:subject>
</nmwg:metadata>
<nmwg:data id="data0" metadataIdRef="serviceLookupInfo">
<nmwg:metadata id="meta1">
<perfsonar:subject id="subj1" xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/";>
<!-- some description of an interface, or end point -->
</perfsonar:subject>
<nmwg:eventType>utilization</nmwg:eventType>
</nmwg:metadata>
</nmwg:data>


Does this make more sense Ulisses?

-jason




Archive powered by MHonArc 2.6.16.

Top of Page