Hi.
Thanks for your explanation. I'll try your temporary workaround. It looks
like the zip file you're point is correct package that I used.

Thanks again.
On Fri, Oct 9, 2009 at 2:08 PM, Dave Kuhlman <dkuhl...@rexx.com> wrote:

> > From: Matt Oh <oh.jeongw...@gmail.com>
> > Sent: Friday, October 9, 2009 12:04:56 AM
> >
> > Actually it's
> >
> >
> http://oval.mitre.org/language/download/schema/version5.3/ovaldefinition/complete/windows-definitions-schema.xsd
> >
> > and it eventually includes
> >
> >
> http://oval.mitre.org/language/download/schema/version5.3/ovaldefinition/complete/xmldsig-core-schema.xsd
> >
>
> Matt -
>
> I was mistaken.  base64Binary is a built-in type.  You should not need
> to define it in your schema.
>
> That means that this is a bug in generateDS.py, I think.  So, I'll
> get back to you next week.
>
> In the meantime, and after a bit of investigation, it looks like
> the problem is related to the fact that the namespace prefix for
> XML schema in windows-definitions-schema.xsd is "xsd:", but the
> namespace prefix for XML schema in xmldsig-core-schema.xsd
> which is "" (that is, no prefix).  generateDS.py is not capable of
> switching from one namespace prefix to another in the middle of
> processing.  At least, I don't see (yet ?) how it could.
>
> If you are interested in patching around this problem, here is a
> patch:
>
>    --- ../orig/xmldsig-core-schema.xsd    2007-05-30 11:28:54.000000000
> -0700
>    +++ xmldsig-core-schema.xsd    2009-10-09 13:26:45.000000000 -0700
>    @@ -45,7 +45,7 @@
>       <element name="SignatureValue" type="ds:SignatureValueType"/>
>       <complexType name="SignatureValueType">
>         <simpleContent>
>    -      <extension base="base64Binary">
>    +      <extension base="xsd:base64Binary">
>             <attribute name="Id" type="ID" use="optional"/>
>           </extension>
>         </simpleContent>
>
> But, I think that this patch ought not to be needed if
> generateDS.py knew how to handle these namespaces correctly and
> knew how to switch from one namespace prefix to another depending
> on the prefix defined in and imported file.  I'll have to admit
> that I don't understand this too clearly myself.
>
> I'll look into it a bit more next week.  But, I believe that it is
> a structural problem that would be way too difficult for me to fix
> anytime soon, if at all.  I'm not sure yet.
>
> Thanks for pointing out this problem to me.
>
> By the way, in order to test this I downloaded and unrolled:
>
>    oval-definitions-schema-complete.zip
>
> from:
>
>    http://oval.mitre.org/language/download/schema/version5.3/
>
> Is that what you are working with?
>
> - Dave
>
>
>  --
>
>
> Dave Kuhlman
> http://www.rexx.com/~dkuhlman
>



-- 
-matt
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
generateds-users mailing list
generateds-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/generateds-users

Reply via email to