I'm not sure if this answers any questions for this post, but here is some info on the XML. If you configure FCS to output an XML file, it will show you the exact format that you need to use to format your XML files to be read in by FCS. So, here is what it looks like:
<?xml version="1.0"?>
<FinalCutServer>
<getMdReply>
*<entity entityType="asset" entityId="/asset/1046">*
<metadata>
<mdValue fieldName="Location" dataType="string">Orlando, Florida</mdValue>
</metadata>
</entity>
</getMdReply>
</FinalCutServer>
To be able to read in XML data, however, you need to know the specific ID number of the asset and/or production that you are working with. That's under the EntityID line. Most likely, you will need to run a script or command search to find the production or asset that you want to work with and then have that script write out an xml file using this format.
Keep in mind that the format above is an outputted XML file. For the bolded parts of the code, you will need to change it to the following to format an input XML data file:
<request reqId="setMd" entityId = "/asset/153">
<params>
Make sure your closeout tags correspond to those as well. You can have as many mdValue tags as you want - but they all have to correspond to fields in FCS.
To integrate with Ruby, PHP, or CGI for a web interface, I'm thinking that you'd need to either parse out this file using a program, or I'm sure there is an easier way to get around it. I know there are a wide range of command-line programs built into FCS that will output this data without having to parse out an XML file. The getMd command is available from the command line thought the unix FCS client, where the return is simply the value of the field you are looking for (much easier to work with). I'm really hoping that Apple comes out with some docs on this. I'm going to keep an eye on the developer site.