Comments on: OVF work in progress published http://stage.vambenepe.com/archives/236 IT management in a changing IT world Wed, 17 Mar 2010 19:31:41 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Recent Links Tagged With "xsd" - JabberTags http://stage.vambenepe.com/archives/236#comment-57647 Recent Links Tagged With "xsd" - JabberTags Sat, 27 Dec 2008 22:04:26 +0000 http://stage.vambenepe.com/?p=236#comment-57647 [...] miyuu on Sat 27-12-2008 xsd command and multiple xsd files Saved by stdstaff on Tue 23-12-2008 OVF work in progress published Saved by skwerley on Sat 13-12-2008 [AXIS2-3996] WS-Security/Rampart: Must Understand check [...] [...] miyuu on Sat 27-12-2008 xsd command and multiple xsd files Saved by stdstaff on Tue 23-12-2008 OVF work in progress published Saved by skwerley on Sat 13-12-2008 [AXIS2-3996] WS-Security/Rampart: Must Understand check [...]

]]> By: William Vambenepe’s blog » Blog Archive » Reviewing DMTF OVF as a “preliminary standard” http://stage.vambenepe.com/archives/236#comment-52796 William Vambenepe’s blog » Blog Archive » Reviewing DMTF OVF as a “preliminary standard” Tue, 14 Oct 2008 08:08:00 +0000 http://stage.vambenepe.com/?p=236#comment-52796 [...] summer, which itself wasn’t a big change from the original specification. As I wrote in the review of the “work in progress”, the DMTF tightened the language of the  specification more [...] [...] summer, which itself wasn’t a big change from the original specification. As I wrote in the review of the “work in progress”, the DMTF tightened the language of the  specification more [...]

]]> By: William Vambenepe http://stage.vambenepe.com/archives/236#comment-49235 William Vambenepe Tue, 19 Aug 2008 16:22:31 +0000 http://stage.vambenepe.com/?p=236#comment-49235 Fermin: Yes, this is a problem. The original spec has the XSD in appendix in the PDF file, but it's a real pain to copy/paste that into a document that can be processed by an XML parser (copying out of PDF is always hell). I complained about that in my initial review. You're right that the updated version doesn't give you (that I can see) any access to the updated XSD docs. Fermin: Yes, this is a problem. The original spec has the XSD in appendix in the PDF file, but it’s a real pain to copy/paste that into a document that can be processed by an XML parser (copying out of PDF is always hell). I complained about that in my initial review. You’re right that the updated version doesn’t give you (that I can see) any access to the updated XSD docs.

]]> By: fermin http://stage.vambenepe.com/archives/236#comment-49222 fermin Tue, 19 Aug 2008 10:39:00 +0000 http://stage.vambenepe.com/?p=236#comment-49222 What's funny with this 1.0 work in progress publication is that the OVF XSD referred in the document are not available as told in Annex C (<em>"A normative copy of the XML schemas for this specification may be retrieved resolving the XML namespace URIs for this specification. Note that .xsd has to be appended to the URIs."</em>). That is, http://schemas.dmtf.org/ovf/envelope/1.xsd, http://schemas.dmtf.org/ovf/environment/1.xsd, http://schemas.dmtf.org/wbem/wscim/1/schema/2/CIM_VirtualSystemSettingData.xsd and http://schemas.dmtf.org/wbem/wscim/1/schema/2/CIM_ResourceAllocationSettingData.xsd all point to a "404 Not Found" :/ Maybe the XSD are still on progress so they are not available, but anybody knows if they are publicly available (in other URL), please? A throughout analysis of the specification would need to consider the XSDs too... What’s funny with this 1.0 work in progress publication is that the OVF XSD referred in the document are not available as told in Annex C (“A normative copy of the XML schemas for this specification may be retrieved resolving the XML namespace URIs for this specification. Note that .xsd has to be appended to the URIs.”).

That is, http://schemas.dmtf.org/ovf/envelope/1.xsd, http://schemas.dmtf.org/ovf/environment/1.xsd, http://schemas.dmtf.org/wbem/wscim/1/schema/2/CIM_VirtualSystemSettingData.xsd and http://schemas.dmtf.org/wbem/wscim/1/schema/2/CIM_ResourceAllocationSettingData.xsd all point to a “404 Not Found” :/

Maybe the XSD are still on progress so they are not available, but anybody knows if they are publicly available (in other URL), please? A throughout analysis of the specification would need to consider the XSDs too…

]]>