RE: [legalxml-courtfiling] base64 encoding

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

Thanks for the clarification.

> -------- Original Message --------
> Subject: RE: [legalxml-courtfiling] base64 encoding
> From: "Nick Pope" <pope@secstan.com>
> Date: Thu, May 12, 2005 10:35 am
> To: "John Messing" <jmessing@law-on-line.com>,
> <legalxml-courtfiling@lists.oasis-open.org>
> 
> John,
> 
> I think that you have misunderstood some of the discussions that have gone
> on in DSS.
> 
> DSS supports a range of encodings.  If the whole document to be signed is
> pure 100% binary then it is recommended that this be encoded as base64, but
> any alternative means of carrying binary data within XML is supported.
> 
> What little I have been able to glean about what the "DIME" encoding you
> mentioned this is not a direct replacement for base64 as a means of encoding
> binary data.
> 
> So, DSS does not exclusively use base64.  And from what I have currectly
> understood what CF TC are proposing should not be an issue.
> 
> Once the details have been specified a bit further we can help with how the
> entity seal best fits in the court filing structure.
> 
> Hope this helps clarify things
> 
> Regards
> 
> Nick
> 
> > -----Original Message-----
> > From: John Messing [mailto:jmessing@law-on-line.com]
> > Sent: 12 May 2005 14:45
> > To: legalxml-courtfiling@lists.oasis-open.org
> > Subject: [legalxml-courtfiling] base64 encoding
> >
> >
> > At the f2f in New Orleans, a comment was made that we would not refer to
> > base64 encoding in Blue because of the emergence of another mime
> > encoding type. The DSS TC exclusively uses base64 encoding and has
> > requested of the CF TC a reference to the newer encoding standard so
> > that it may consider changing as well. I have made some informal
> > requests of individual members, but without much luck. Is there anyone
> > who can provide the requested reference? Thanks.
> >
> > > -------- Original Message --------
> > > Subject: RE: [legalxml-courtfiling] Globally unique identifiers -
> > > approach
> > > From: "Cabral, James E." <JCabral@mtgmc.com>
> > > Date: Wed, May 11, 2005 5:53 pm
> > > To: "Cusick, James" <James.Cusick@wkglobal.com>,
> > > <legalxml-courtfiling@lists.oasis-open.org>
> > > Cc: "John Greacen" <john@greacen.net>
> > >
> > > James,
> > >
> > > That approach seems appropriate for identifying things that occur at a
> > > specific time, e.g. Filing Identifiers, but do we need a timestamp for
> > > things that do not change often (e.g. FilingAssembly or FilingReview
> > > ID)?
> > >
> > >   jim
> > >
> > > ________________________________
> > >
> > > From: Cusick, James [mailto:James.Cusick@wkglobal.com]
> > > Sent: Wednesday, May 11, 2005 12:41 PM
> > > To: legalxml-courtfiling@lists.oasis-open.org
> > > Cc: John Greacen
> > > Subject: [legalxml-courtfiling] Globally unique identifiers - approach
> > >
> > >
> > > John and all,
> > >
> > > At the New Orleans meeting I agreed to propose an approach to generating
> > > globally unique identifiers. After searching around on this topic I
> > > would like to recommend using UUIDs as per the IETF DRAFT RFC. This
> > > approach requires NO global coordination.
> > >
> > > Please see:
> > > http://www.ietf.org/internet-drafts/draft-mealling-uuid-urn-05.txt
> > >
> > >
> > > This RFC is currently in draft status and is based on Unique ID
> > > generation technique used in Open Software Foundation's Distributed
> > > Computing Environment. The RFC guarantees that ID's generated using the
> > > recommended algorithms will be unique across space and time.
> > >
> > > This RFC specifies 4 algorithms to generate universally unique ID's.
> > > The following subset is recommended for LegalXML standards:
> > >
> > >   1. System timestamp up to a 100 nanoseconds
> > >
> > >   2. MAC address of the machine where UUID is generated
> > >
> > >   3. Use of Random or pseudo random numbers
> > >
> > >
> > > Finally, the RFC contains C code sample on how to generate UUID's based
> > > on the generation algorithms listed above.
> > >
> > > Please let me know what you think and how you would like to see this
> > > phrased within Blue.
> > >
> > > Regards,
> > > james
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> >