[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dss-x] Interop: elapsed time estimation, some proposals forleading certain tasks
Thanks for this Andreas... See below intermixed. Regards Juan Carlos. kuehne@trustable.de escribió: > Hi Juan Carlos, > > I agree with your estimations in general but I guess two weeks for task 4 is a bit optimistic, espacially in case of the detailed verification report. > Actually, after a second thought, I also think that it is too optimistic... I would go then for around 4 weeks.... > My idea for the core is to derive a set of requirements from the spec that are building the foundation for the test cases. And additionally we can define conformance level to each of this requirements. So we don't have to touch the core document and schema but add a set of assertions like the way it's done in the TAG spec. I am not familiar with TAG spec...will take a look ...it may be a good way... > A similiar approach is around in W3C documents. Let's see what's the best for our needs. > > Greetings > > Andreas > > ----- original Nachricht -------- > > Betreff: [dss-x] Interop: elapsed time estimation, some proposals for leading certain tasks > Gesendet: So, 28. Feb 2010 > Von: Juan Carlos Cruellas<cruellas@ac.upc.edu> > >> Dear all, >> >> Below follows some initial estimation of elapsed time for the interop >> tasks as well as a proposal for leaders of certain tasks/sub-tasks >> >> TASK 1. INTEROPERABILITY SCOPE: 2 weeks for initial proposals >> >> >> For each profile and the core, identify what features (optional inputs >> and optional outputs) will be tested. >> >> So far it seems that most of TC members agreed in having interop on >> certain features of: >> >> . core (leader: Andreas; other volunteers: Stefan, Juan Carlos, other?) >> >> . complete validation report (leader: Detlef; other volunteers: Juan >> Carlos, other?) >> >> . visual signatures (leader: Ezer, other volunteers?) >> >> and maybe others like AdES.... >> >> >> TASK 2. SPECIFICATION OF TEST CASES. 4 to 6 weeks. >> (the leaders for core and profiles as before) >> >> >> For each profile and the core, completely define the test cases. This >> means, at least, to generate a document (probably better if contains >> tables) that provides all the details of the test cases. >> >> If ETSI's portal used, use the template already developed for previous >> interop tests. >> >> TASK 3. TAILORING OF THE PORTAL FOR THE DSS INTEROP 3 weeks (leader ETSI >> CTI if ETSI portal eventually used) >> >> TASK 4. DEFINITION OF TRUST INFRASTRUCTURE (PKI: CAs chain, CRL issuers, >> OCSP responses issuers) 2 weeks? >> >> TASK 5. COMPLETE PKI'S DEPLOYMENT IF ANY PIECE IS MISSING IN THE PORTAL >> (would depend on the trust infrastructure to be used) >> >> TASK 6. COMPLETE DOCUMENTATION IN THE PORTAL (this includes producing >> explanatory material ) 4 weeks >> >> TASK 7. GENERATE THE DSS REQUESTS AND RESPONSES CORRESPONDING TO THE >> TEST CASES (TC MEMBERS INVOLVED). (??) >> >> >> --------------------------------------------------------------------- >> 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 >> >> > > --- original Nachricht Ende ---- >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]