perfsonar development work

[Jason Zurawski <>]

Ulisses;


> > > Because of my problems in XML conversions and some comments, I'm not sure 
> > > If I'm doing right when returning the xml. I understood that any XML 
> > > document syntactically correct should be ok.
> > >
> > > am I right? in this case I don't understand why I have xml to dom failures.
> > >
> > > Of course, a well organized xml document is preferable. Currently, in the 
> > > xml output I have to send as response, I have to return a list of links, a 
> > > list of n
> > > odes [*] and the return code.
> > >
> > > Which should be the way do structure the document? are there guidelines?
> > >
> > >       

In the various design documents that were created for the Topo service, 
were requests and responses discussed?  If so they should look like that. 

> > > Maybe the way to do it should be:
> > >       
> > This is much closer to correct. As others have already pointed out - you 
> > had a very strange looking structure (nested data elements - metadata 
> > information in data elements...)
> >
> >     
> > > <nmwg:message>
> > >         <nmwg:metadata id="TOPSDownloadDBResponseMetadata"/>
> > >       

There should be some justification as to why this is blank.

> > >         <nmwg:data metadataIdRef="TOPSDownloadDBResponseMetadata">
> > >
> > >       
<nmwg:metadata>
 <nmwg:subject>
   <!-- link(s) -->
 </nmwg:subject>
<nmwg:metadata>

<!-- more metadata elements if necessary, that way multiple data blocks 
are not needed -->
> > >         </nmwg:data>
> > >
> > >
> > >
> > >         // result code metadata and data
> > >
> > >         <nmwg:metadata id="result code">
> > >                 <nmwg:eventType>success.ls.remove</nmwg:eventType>
> > >       

You will need to define your own result codes of course...

> > >         </nmwg:metadata>
> > >
> > >         <nmwg:data id="result code description"    metadataIdRef="result 
> > > code">
> > >                 <nmwg:datum>Text explaining the error message</nmwg:datum>
> > >         </nmwg:data>
> > >       

If there was an error that occured.

> > > </nmwg:message>
> > >       

I think with a little bit more work this basic example will look good 
for a response, but we still need to rough out a request and address 
some of the other issues.

-jason