Christos suggested that it could be good to have the same structure for all the items in Section 2. It followed a short discussion and the following structure emerged as the a viable approach: Models/Technologies/Use Cases/Emerging Patterns/Issues.
It is well understood that for the Use Cases and Technologies sub-sections are to be filled, only later the Models, Emerging Patterns and Issues sub-sections could be really worked out.
Davide pointed out that Token Translation Service (TTS) actually lack a strong definition, so each time we speak about it we have to choose which Technologies are TTS or not (TCS is the most apparent case), so he proposed to create a Definition item in the TTS section;
Christos suggested not to divide the items in Section 3 by protocols translations services, but by main topics (like in Section 2); Lalla pointed out that we can change the structure but we should not loose focus on the protocols, since they are the real business of TTS; with all the comments and views in mind, it was agreed to make some modification to the Section 3 to take into account all the hints;
Nicolas suggested that a more formal structure (like in Section 2) could be used for Section 5 too;
The initial title of Section 5 — Delegation of Authorisation Management — was deemed somehow ambiguos, it was agreed to get rid of the world "Management", and maybe review it once again after we have some content;
Shiraz, to avoid duplication of efforts already made in other Tasks (namely the Blueprint), made a proposal to anchor the content of the Non Web Access section to the very topics of JRA1.4, so two items were added in the section: Attribute Management and Token Translation;
It still remain questionable if there is the case for LOA for Attributes in JRA 1.4; it was agreed to investigate further and then decide if the section could stay or be deleted;
Nicolas proposed to move the Consent content in the Issues items of relevant Section 2 points;
15min
Assignments and next VC
Since the VC lasted too long, only few actions could be assigned, there will be a next round of assignments either via aarc-jra1 mailing list or in the next VC;
Next VC will be held next week, it follows a foodle on the aarc-jra1 mailing list;
Action items
Davide Vaghetti: clean up the TOC; make the modification according to the VC discussion;
Davide Vaghetti: give an initial definition of Token Translation Service (to be further reviewed and questioned);
Davide Vaghetti: will collect links to existing relevant works for Section 1;
Davide Vaghetti: will ask to the people behind CILogon to contribute to the deliverable in the relevant section;
Nicolas Liampotis: will take care of point 2.1.2.1 (Idp/Shibboleth);
Nicolas Liampotis: will take care of point 2.1.2.2 (Idp/SimpleSAMLphp);
Nicolas Liampotis: will give an initial outline to the point 2.3.1 (Attribute Aggregation Services/Models);
Ahmed Shiraz Memon: will take care of point 2.1.2.4 (Idp/Technologies/UNITY);