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

["Nick Pope" <pope@secstan.com>]

I would suggest that there are advantages in including the digital signature
in the payload as this enables the signature to be used to provide
additional end to end security, not only protecting data when transferred
between systems.

The signature carried with the document protects the document in storage.
It also can be used to provide a signature which can verified by any party
retieving a file.

Nick Pope

> -----Original Message-----
> From: John M. Greacen [mailto:john@greacen.net]
> Sent: 11 September 2005 14:35
> To: 'John Messing'; scott@justiceintegration.com
> Cc: legalxml-courtfiling@lists.oasis-open.org
> Subject: RE: [legalxml-courtfiling] Newest version (0.2) of IEPD/WSDL
> bundle--and an issue
>
>
> In Atlanta, the TC decided not to use the entity seal approach to digital
> signatures.  We maintained our commitment to recommend use of digital
> signatures, just not in the form of the entity seal, which includes
> additional elements none of which we felt were relevant to our work.
>
> Next week at the face to face in Seattle, we will have to address
> the issue
> that Dallas has raised which I understand is whether the digital signature
> is contained in the message layer or in the payload.
>
> > -----Original Message-----
> > From: John Messing [mailto:jmessing@law-on-line.com]
> > Sent: Sunday, September 11, 2005 7:34 AM
> > To: scott@justiceintegration.com
> > Cc: legalxml-courtfiling@lists.oasis-open.org
> > Subject: RE: [legalxml-courtfiling] Newest version (0.2) of IEPD/WSDL
> > bundle--and an issue
> >
> > 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
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
>
>
>
> ---------------------------------------------------------------------
> 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
>
>
>