RE: [legalxml-courtfiling] Newest version (0.2) of IEPD/WSDL bundle--and an issue

[John Messing <jmessing@law-on-line.com>]

In the New Orleans face-to-face, the TC voted to at least recommend if
not flat-out require digital signatures for document security purposes
in 3.0 using the DSS TC's entity seal profile. Scott's note deals with
digital signatures for messaging purposes only, and not with the
document security piece.

What has happened to the work on the TC's recommendation/requirement for
document security using the entity seal profile?


> -------- Original Message --------
> Subject: [legalxml-courtfiling] Newest version (0.2) of IEPD/WSDL
> bundle--and an issue
> From: "Scott Came" <scott@justiceintegration.com>
> Date: Sat, September 10, 2005 3:05 pm
> To: legalxml-courtfiling@lists.oasis-open.org
> 
> Per a conference call held with the "editing team" on Thursday, I have
> updated the IEPDs and WSDLs to include the XML Signature KeyInfo element
> in the Court Policy message schema.  This is used to allow a court to
> publish their public key information, per the domain model.
> 
> As I did with the initial submission last week, I tested the WSDL and
> schemas by generating endpoint code with Apache Axis 1.2.1.  The 0.1
> submission generated fine (using Axis' wsdl2java utility.)  This is a
> pretty good test that the WSDL and schemas aren't missing any referenced
> types/elements, that the WSDL and schemas are all valid, etc.
> 
> Unfortunately, adding the XML Signature stuff broke the clean
> generation.  I am fairly certain the element reference from within the
> Court Policy extension schema is correct.  I suspect there is a problem
> in how Axis is handling the XML Signature schema.  I did a little
> searching of the Axis mailing lists and bug lists, but couldn't find
> anything specifically reporting this problem.
> 
> I invite the more technical TC members to take a look at this, first to
> see if you can replicate it, but also to see if you have ideas as to
> what's wrong and hopefully a solution.
> 
> Thanks.
> --Scott
>  --------------------------------------------------------------------- To
> unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all your TCs in
> OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php