[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dss-x] Action Item DSS Usage
Hello Attached an updated version of the slides. - The docRef usage removed and stated that it can be useful if the document is not at the client-side or (DSS) server-side. - A number of findings and explicit decision points are added at the end. - An example application, based on slide 21 of Frank Cornelis, is shown at the end. It's "a first shot"! Please feel free to comment, adjust, improve! Regards Ernst Jan On 3-6-2011 18:05, Juan Carlos Cruellas wrote: > Dear Ernst, > > Thank you very much for the slides, and thanks Andreas for the > comments. Some comments/questions came to my mind while reading them: > > 1. I see there several places where apparently there is a DSS message > that does not contain neither the document nor its digest, but an ID > or its reference. After reviewing the core my conclusion is that this > particular way of identifying a document is not present in the XML > schema, so I guess that we should include this new element somewhere > (maybe as a child of the "Other" field of the current InputDocuments? > > 2. Conceptually speaking Andreas, would not the transfer of documents > be relevant in use cases wher the What you see is what you sign is a > requirement (ie. sign payments documents)? > > Regards > > Juan Carlos. > > > El 01/06/2011 17:51, kuehne@trustable.de escribió: >> Hi Ernst, >> >> thanks for the update ! >> Still I'm a bit concerned about all the document transfer tasks >> dragged into our scope. This could best be done by all the protocols >> that are already in place for it. >> Of course it may be nacessary for the use case, but not as a target >> of the DSS scope. A device that's not capable of building a hash on a >> file but able to act as a file server ( use case 1b ) soungs a bit >> strange to me. Moreover I don't get the advantage of this use case >> where a DSS call is done to the server _without_ a document which >> will be requested by the server immediately for hash calculation ! >> Why don't do a request _including_ the document or _including_ the >> hash ? >> >> >> Greetings >> >> Andreas >> >> ----- original Nachricht -------- >> >> Betreff: Re: [dss-x] Action Item DSS Usage >> Gesendet: So, 29. Mai 2011 >> Von: Ernst Jan van Nigtevecht<EJvN@Sonnenglanz.net> >> >>> Hello, >>> >>> Attached an update of the slides (date May 29) regarding: >>> (1) the user client calculates the hash (Use Case variants 1c, 2b >>> and 2d) >>> (2) the REST binding..... I only added a slide with TO DO... as a >>> reminder.. >>> >>> By the way, we could also think of an extension to give the signed hash >>> as an argument to the DSS, instead of providing the hash and let the >>> DSS >>> 'get' the signature by means of the getSignature (see the Use Case >>> diagrams). But this can be viewed as an optimization... >>> >>> I explicitly made the difference between UC1 and UC2 just to make it >>> clear and to show the differences/similarities. And it's true: UC1 is >>> actually a special case of UC2, where the User-Device and the >>> User-Agent >>> collide. >>> >>> Regarding the calculation of a hash: if a document is treated as a >>> binary document it is of course a simple case. But in case of, for >>> example, PDF I expect more difficulties.. >>> >>> With kind regards >>> >>> Ernst Jan >>> >>> On 29-5-2011 14:07, Andreas Kuehne wrote: >>>> Hi Ernst, >>>> thanks for updating the slides !. >>>> >>>> Oooking at the differences of Use Cases 1 and 2 I would guess that >>>> UC 2 is >>> the more general approach. Isn't UC1 the special case where User >>> Agent and >>> User device are collocated ? >>>> >>>> Another remark : Why are the documents being transferred to the server >>> side ? Especially in this case whre the documents are located a the >>> client >>> side it would be more efficient to transfer just e hash. Even a >>> simple smart >>> phone is able to calculate a hash, nowadays ... >>>> >>>> Greetings >>>> >>>> Andreas >>>> >>>> ----- original Nachricht -------- >>>> >>>> Betreff: Re: [dss-x] Action Item DSS Usage >>>> Gesendet: Fr, 27. Mai 2011 >>>> Von: Ernst Jan van Nigtevecht >>>> >>>> Hello, >>>> >>>> Based on the discussions during the last telephone conferences andthe >>> feedback by email, an update is created of the slides regardingthe >>> use of >>> DSS(-X) in a particular client/server setting. >>>> >>>> With kind regards >>>> >>>> Ernst Jan >>>> >>>> On 6-5-2011 14:08, Ernst Jan van Nigtevecht wrote:During the previous >>> conference call an action point was mentioned aboutthe use of the DSS >>> protocol in a more complex case with a user agent, anapplication >>> system and >>> a DSS server (request initiated by Òscar Burgos).Attached a >>> document; it >>> describes some assumptions, a use case, twoscenario's (sequence >>> diagrams) >>> and the possible use of POAS or ebMSv3 asa transport binding.With kind >>> regardsErnst >>> Jan---------------------------------------------------------------------To >>> >>> unsubscribe from this mail list, you must leave the OASIS TC >>> thatgenerates >>> this mail. Follow this link to all your TCs in OASIS >>> at:https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>> >>>> >>>> --- original Nachricht Ende ---- >>>> >>> >> >> --- original Nachricht Ende ---- >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to 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. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >
Creating Signatures at User Agent with DSS - June9-2011.ppt
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]