Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] question on LS registration (XML schema for registration)

Subject: perfsonar development work

List archive

Re: [pS-dev] question on LS registration (XML schema for registration)


Chronological Thread 
  • From: Jason Zurawski <>
  • To: ulisses <>
  • Cc: Martin Swany <>, ,
  • Subject: Re: [pS-dev] question on LS registration (XML schema for registration)
  • Date: Thu, 30 Nov 2006 22:32:54 -0500

Ulisses;



but again, I don't know which xml element should I include in the data,
none fits our needs (eg: It is not a Node), and then we should use something like anyElement and then some kind of ad-hoc "domain" element.

is this right?

Metadata =
element nmwg:metadata {
(
Identifier &
MetadataIdentifierRef? &
MetadataContent
),
anyElement*
}



Because it is possible to put un-expected elements in Metadata, I dont see a problem doing something like this:

<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/";>

<!-- service info -->

</psservice:service>
</perfsonar:subject>
</nmwg:metadata>
<nmwg:data id="data0" metadataIdRef="serviceLookupInfo">
<nmwg:metadata id="meta1">

<!-- whatever topo info you want to advertise -->

</nmwg:metadata>
</nmwg:data>

-jason



Archive powered by MHonArc 2.6.16.

Top of Page