Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kickoff Meeting for the Interoperable Geographic Information for Biosphere Study (IGIBS) Project

1,128 views

Published on

Presentation by Chris Higgins at the Interoperable Geographic Information for Biosphere Study (IGIBS) project Kickoff, 11 April 2011.

Published in: Education
  • Be the first to comment

  • Be the first to like this

Kickoff Meeting for the Interoperable Geographic Information for Biosphere Study (IGIBS) Project

  1. 1. Kickoff Meeting for the Interoperable Geographic Information for Biosphere Study (IGIBS) Project Welsh Institute for Sustainable Education, 11 th April, 2011, Chris Higgins, Project Manager, [email_address]
  2. 2. Agenda WP4: Access Control 1530-1600 WP3: Application Development 1500-1530 WP2: Stakeholder Engagement 1430-1500 WP1: Project Management – Project Plan 1400-1430 Lunch 1230-1400 IGIBS in the University Aberystwyth/IGES context 1155-1230 IGIBS in the Welsh Assembly Government context 1120-1155 IGIBS in the EDINA/JISC context 1045-1120 Intro to the Dyfi Biosphere 1030-1045 Scene setting 1015-1030 Participant Introductions 1000-1015
  3. 3. Align Business Objectives Institute of Geography and Earth Sciences EDINA Welsh Assembly Government Within limits of the JISC programme aims and the project proposal. Suggest we spend afternoon fleshing out project plan and maximising the size of the sweet spot in the middle
  4. 4. Panel Comments on the IGIBS Proposal 1of2 <ul><li>... interoperability with the emerging national SDI through INSPIRE compliance. </li></ul><ul><li>Shibboleth authenticated OWS will be of particular benefit to the academic community </li></ul><ul><li>... the bid fails to present the use case with sufficient clarity </li></ul><ul><li>...could have been presented with much greater force.  </li></ul><ul><li>... may well be valuable work and an important use case , but flaws in presentation and argumentation mean that it is impossible to give it wholehearted endorsement. </li></ul><ul><li>... through the interoperability of its components, is worthwhile.  Secondly, by engaging with a specific biosphere initiative the project potentially extends the breadth and depth of the JISC geospatial user community. </li></ul><ul><li>Less is said directly about the benefits for HE ... </li></ul><ul><li>The proposal is missing a forceful and clear, general, layman's description of the benefits and purpose of the tool.  </li></ul><ul><li>The central benefit appears to be the creation of an application that 'will allow users to upload data and automatically generate an instance of a WMS </li></ul>
  5. 5. Panel Comments on the IGIBS Proposal 2of2 <ul><li>... should release 2 or more months to achieve the necessary staff recruitment, mitigating the associated risk. </li></ul><ul><li>...no visual or verbal description of timings and, above all, dependencies.  The bid alludes to checkpoint meetings, without indicating, even roughly, key milestones, timings for progress checking. </li></ul><ul><li>... bid does not really present a clear case for the reuse of the outputs in other scenarios ... </li></ul><ul><li>...a substantial contribution from the Welsh Assembly Government. </li></ul><ul><li>...would perhaps have liked to see some more thought given to extension of tools from this project across a broader range of (potential) users . </li></ul><ul><li>Stakeholder engagement will be primarily through the RA employed at IGES (recruitment required). </li></ul><ul><li>26% contribution to costs by the participants... </li></ul><ul><li>... this team is highly qualified for the work proposed... </li></ul>
  6. 6. IGIBS Deliverables (from proposal) <ul><li>Demo of UK access management technology being used to secure public sector services in combination with academic sector services </li></ul><ul><li>Recommendations for further work </li></ul>WP4 <ul><li>Working prototype of the “WMS factory” tool </li></ul><ul><li>Simple mapping application </li></ul><ul><li>Technical recommendations for what is necessary to take the “WMS factory” tool into production </li></ul><ul><li>Technical suggestions for enhancements to the relevant components of the UK academic SDI </li></ul><ul><li>Technical suggestions for taking the mapping application forward </li></ul>WP3 <ul><li>Report articulating real world end user problems that drove project </li></ul><ul><li>Best Practice model for using UK academic SDI at the dept level </li></ul><ul><li>Report articulating future requirements </li></ul>WP2 <ul><li>Project website; wiki and blog </li></ul><ul><li>Programme reporting and project management documentation </li></ul>WP1
  7. 7. <ul><li>Introduction to </li></ul><ul><li>Biosffer Dyfi Biosphere </li></ul>
  8. 8. Vision Statement <ul><li>“ The Dyfi Biosphere will be recognised and respected internationally, nationally and locally for the diversity of its natural beauty, heritage and wildlife, and for its people’s efforts to make a positive contribution to a more sustainable world. It will be a self confident, healthy, caring and bilingual community, supported by a strong locally-based economy.” </li></ul>
  9. 9. Constitution <ul><li>Coordination Body - Dyfi Partnership </li></ul><ul><ul><li>Sets strategy </li></ul></ul><ul><ul><li>Action plan (currently under compilation, comprised of relevant independent endorsed projects) </li></ul></ul><ul><li>Secretariat </li></ul><ul><ul><li>Initially CCW </li></ul></ul><ul><ul><li>Now WAG </li></ul></ul><ul><ul><li>The 4 LA’s next </li></ul></ul><ul><li>Representatives (approx 30) from: </li></ul><ul><ul><li>Local community </li></ul></ul><ul><ul><li>WAG </li></ul></ul><ul><ul><li>Thematic Groups (Mike Woods for Research?) </li></ul></ul>
  10. 10. Thematic Groupings <ul><li>Education: schools mostly </li></ul><ul><li>Tourism </li></ul><ul><li>Welsh Language Culture: brings together language initiatives, stimulate activity related to Welsh cultural heritage </li></ul><ul><li>Community & Heritage: example of uploading material to http:// beta.peoplescollectionwales.co.uk </li></ul><ul><li>Conservation, landscape, land use and rural livelihoods: low carbon based livelihoods, adaptation to environmental change </li></ul><ul><li>Farming </li></ul><ul><li>Research & Monitoring </li></ul><ul><ul><li>Last meeting was in Autumn 2010 </li></ul></ul><ul><ul><li>Next meeting 18 th May 2011 </li></ul></ul><ul><ul><li>Chaired by IGES </li></ul></ul>
  11. 11. Some example linked activities/ideas <ul><li>“ Passport” to the Biosphere </li></ul><ul><li>Dyfi Footprint Project </li></ul><ul><li>Tirwedd Dyfi. (Arts project, connections between Welsh language/culture and landscape) </li></ul><ul><li>New Pathways for Sustainable Rural Livelihoods </li></ul><ul><li>Dyfi Osprey Project </li></ul><ul><li>Wood-fuelled district heating for Dinas Mawddwy </li></ul><ul><li>Feasibility study into how local farmers could obtain a premium through using a Biosphere brand </li></ul><ul><li>Darganfod Dyfi / Explore Dyfi </li></ul>
  12. 12. <ul><li>IGIBS in the EDINA/JISC context </li></ul><ul><ul><li>essential background to this project from this perspective </li></ul></ul><ul><ul><li>what others need to know to understand why in IGIBS. </li></ul></ul><ul><ul><li>what we want/expect out the project </li></ul></ul>
  13. 13. JISC <ul><li>Joint Information Systems Committee </li></ul><ul><li>JISC Infrastructure for Education and Research Programme </li></ul><ul><li>Geospatial Strand (Tagged JISCGeo) </li></ul><ul><ul><li>Projects to increase the use of geospatial tools, infrastructure (data and services) and information for learners, teachers and researchers; to enhance tools and services and related practice as well as identifying future requirements </li></ul></ul><ul><li>Projects must… address real world end user problems </li></ul>
  14. 14. EDINA <ul><li>JISC Designated, part of University of Edinburgh </li></ul><ul><li>A National Data Centre for Tertiary Education since 1995 </li></ul><ul><li>to enhance the productivity of research, learning and teaching in UK higher and further education (mission statement) </li></ul><ul><li>Focus is on services but also undertake r&D </li></ul><ul><li>EDINA provides technical support in the operation of the UK Access Management Federation </li></ul><ul><ul><li>Uses Shibboleth open source software (an implementation of OASIS Security Assertion Markup Language) </li></ul></ul><ul><ul><li>Approx 8 million users </li></ul></ul><ul><ul><li>837 Member Organisations (IdPs and SPs) </li></ul></ul>EDINA
  15. 15. GECO <ul><li>Geospatial Engagement & Community Outreach </li></ul><ul><ul><li>http:// geco.blogs.edina.ac.uk / </li></ul></ul><ul><li>Managed by EDINA (James Reid) </li></ul><ul><li>The overarching purpose of GECO is to foster a community(ies) of users of geospatial resources (data, services, support). Geospatial, taken in its broadest sense underpins a vast array of academic endeavour - geography represents a fundamental organising axis for information </li></ul>
  16. 16. Spatial Data Infrastructure <ul><li>Infrastructure for Spatial Information in Europe (INSPIRE) Directive </li></ul><ul><li>UK Location Programme (Our National SDI) </li></ul><ul><li>UK Academic SDI </li></ul><ul><li>Some key EDINA/JISC components of the UK Academic SDI relevant to IGIBS: </li></ul><ul><ul><li>GoGeo! http:// www.gogeo.ac.uk / </li></ul></ul><ul><ul><li>GeoDoc </li></ul></ul><ul><ul><li>ShareGeo </li></ul></ul>“ SDI encompasses the policies, organisational remits, data, technologies, standard delivery mechanism and financial and human resources necessary to ensure that those working with spatial data, whether at the global or local scale, are not impeded in meeting their objectives (INSPIRE consultation paper, 2003)”
  17. 17. Main IGIBS Aim – Improve UK SDI Interoperability <ul><li>Public </li></ul><ul><li>sector </li></ul>Academic sector <ul><li>Real world SDI R&D requirements </li></ul><ul><li>Resources </li></ul><ul><li>Data </li></ul><ul><li>Better educated graduates </li></ul><ul><li>Future customers/employees used to using high quality public sector reference data via Geospatial Web Services </li></ul><ul><li>R&D requirements get met </li></ul>Virtuous Circle
  18. 18. What EDINA wants from the project <ul><li>A successful story! In other words, some serious progress with aim expressed on the previous slide. </li></ul><ul><li>Specifically: </li></ul><ul><ul><li>UK Public Authorities using Shibboleth and it made easier for them to share data with the academic sector </li></ul></ul><ul><ul><li>Those EDINA Academic SDI components getting used more, eg, 10-15 good quality metadata records </li></ul></ul><ul><ul><li>A “WMS factory” tool that demonstrably works and gets taken up by the wider GI community </li></ul></ul><ul><ul><li>A simple mapping application that progresses to being integral to the Dyfi Biosphere Reserve </li></ul></ul><ul><li>Follow-on project(s). Only so much can be achieved in 7 months </li></ul>
  19. 19. If I had to prioritise… <ul><li>Demo of UK access management technology being used to secure public sector services in combination with academic sector services </li></ul><ul><li>Recommendations for further work </li></ul>WP4 <ul><li>Working prototype of the “WMS factory” tool </li></ul><ul><li>Simple mapping application </li></ul><ul><li>Technical recommendations for what is necessary to take the “WMS factory” tool into production </li></ul><ul><li>Technical suggestions for enhancements to the relevant components of the UK academic SDI </li></ul><ul><li>Technical suggestions for taking the mapping application forward </li></ul>WP3 <ul><li>Report articulating real world end user problems that drove project </li></ul><ul><li>Best Practice model for using UK academic SDI at the dept level </li></ul><ul><li>Report articulating future requirements </li></ul>WP2 <ul><li>Project website; wiki and blog </li></ul><ul><li>Programme reporting and project management documentation </li></ul>WP1
  20. 20. What EDINA GETS from the project depends on …
  21. 21. <ul><li>IGIBS in the Welsh Assembly Government context </li></ul>
  22. 22. <ul><li>IGIBS in the University Aberystwyth/IGES context </li></ul>
  23. 23. <ul><li>WP1: Project Management </li></ul>
  24. 24. Project Orientation <ul><li>jiscGEO wiki </li></ul><ul><li>“ Official” JISC page </li></ul><ul><li>Programme Manager SLA </li></ul><ul><li>igibs tag and its use </li></ul><ul><li>Video on project documentation (the 7 steps) </li></ul><ul><ul><li>How many of the deliverables can be presented during the project as part of the “community conversation”? </li></ul></ul><ul><li>Turn project plan into Blog posts </li></ul><ul><li>Team use of Blog </li></ul>
  25. 25. With your help today, consider how to re-write sections, re-package and post Core IGIBS team (CH, BC, MK) to meet as close to possible to weekly at IGES and blog regularly. All others welcome any time either physically or by Skype
  26. 26. Which of these can be blog posts? <ul><li>Demo of UK access management technology being used to secure public sector services in combination with academic sector services </li></ul><ul><li>Recommendations for further work </li></ul>WP4 <ul><li>Working prototype of the “WMS factory” tool </li></ul><ul><li>Simple mapping application </li></ul><ul><li>Technical recommendations for what is necessary to take the “WMS factory” tool into production </li></ul><ul><li>Technical suggestions for enhancements to the relevant components of the UK academic SDI </li></ul><ul><li>Technical suggestions for taking the mapping application forward </li></ul>WP3 <ul><li>Report articulating real world end user problems that drove project </li></ul><ul><li>Best Practice model for using UK academic SDI at the dept level </li></ul><ul><li>Report articulating future requirements </li></ul>WP2 <ul><li>Project website; wiki and blog </li></ul><ul><li>Programme reporting and project management documentation </li></ul>WP1
  27. 27. Meetings <ul><li>Weekly, or close to weekly, at IGES. CH will come and meet with BC to hold Skype call with MK. Others to participate in Skype calls or drop in as they wish, or as required, etc. </li></ul><ul><li>Monthly UKLP Data Publishing Working Group meetings </li></ul><ul><li>18 th May. Dyfi Biosphere Research and Monitoring Group meeting </li></ul><ul><li>27-30 June, INSPIRE Conference, Edinburgh </li></ul><ul><li>Final project meeting, Sept/Oct </li></ul>
  28. 28. <ul><li>WP2: Stakeholder Engagement </li></ul>
  29. 29. IGIBS Deliverables (from proposal) <ul><li>Demo of UK access management technology being used to secure public sector services in combination with academic sector services </li></ul><ul><li>Recommendations for further work </li></ul>WP4 <ul><li>Working prototype of the “WMS factory” tool </li></ul><ul><li>Simple mapping application </li></ul><ul><li>Technical recommendations for what is necessary to take the “WMS factory” tool into production </li></ul><ul><li>Technical suggestions for enhancements to the relevant components of the UK academic SDI </li></ul><ul><li>Technical suggestions for taking the mapping application forward </li></ul>WP3 <ul><li>Report articulating real world end user problems that drove project </li></ul><ul><li>Best Practice model for using UK academic SDI at the dept level </li></ul><ul><li>Report articulating future requirements </li></ul>WP2 <ul><li>Project website; wiki and blog </li></ul><ul><li>Programme reporting and project management documentation </li></ul>WP1
  30. 30. From the proposal <ul><li>Real world, localised, inter-disciplinary, end user problems are brought into focus by concentrating on research and education requirements which have emerged from the UNESCO Dyfi Biosphere reserve </li></ul><ul><li>… work with a range of endusers and potential end-users to make sure their requirements inform… </li></ul><ul><li>… primarily by the range of academic disciplines and public sector organisations represented on the Dyfi Biosphere reserve Scientific Advisory Group… </li></ul>
  31. 31. Methodology <ul><li>Include: </li></ul><ul><ul><li>Site visits </li></ul></ul><ul><ul><li>Hosted meetings </li></ul></ul><ul><ul><li>Interviews </li></ul></ul><ul><ul><li>Use of social media tools </li></ul></ul><ul><li>UoA will “test” needs tested in: </li></ul><ul><ul><li>Forest Research Platform </li></ul></ul><ul><ul><li>Education via IGES digital resource centre </li></ul></ul>
  32. 32. User Groups <ul><li>Students, researchers, etc, within IGES </li></ul><ul><li>Students, researchers, etc, within the rest of the University of Aberystwyth, ie, other disciplines </li></ul><ul><li>Other academic sector Wales, UK </li></ul><ul><li>Other non-academic sector users </li></ul><ul><li>Groups 1-3 research and education related to Dyfi Biosphere </li></ul><ul><li>Group 4. Citizens, see thematic groupings </li></ul>2 3 4 1
  33. 33. Report articulating real world end user problems that drove project <ul><li>Use cases not well articulated in project plan </li></ul><ul><li>Need to be fleshed out </li></ul><ul><li>Can document in the blog? </li></ul><ul><li>How to do it? </li></ul>
  34. 34. Best Practice model for using UK academic SDI at the dept level <ul><li>What is this? </li></ul><ul><ul><li>A report primarily for other departments in other universities to use </li></ul></ul><ul><ul><li>Focussed on IGES </li></ul></ul><ul><ul><li>Needs scoped as will stray into wider Research Data Management issues </li></ul></ul>
  35. 35. Report articulating future requirements <ul><li>Hopefully one or more blog posts that will emerge from the “community conversation” over the duration of the project? </li></ul>
  36. 36. <ul><li>WP3: Application Development </li></ul>
  37. 37. IGIBS Deliverables (from proposal) <ul><li>Demo of UK access management technology being used to secure public sector services in combination with academic sector services </li></ul><ul><li>Recommendations for further work </li></ul>WP4 <ul><li>Working prototype of the “WMS factory” tool </li></ul><ul><li>Simple mapping application </li></ul><ul><li>Technical recommendations for what is necessary to take the “WMS factory” tool into production </li></ul><ul><li>Technical suggestions for enhancements to the relevant components of the UK academic SDI </li></ul><ul><li>Technical suggestions for taking the mapping application forward </li></ul>WP3 <ul><li>Report articulating real world end user problems that drove project </li></ul><ul><li>Best Practice model for using UK academic SDI at the dept level </li></ul><ul><li>Report articulating future requirements </li></ul>WP2 <ul><li>Project website; wiki and blog </li></ul><ul><li>Programme reporting and project management documentation </li></ul>WP1
  38. 38. Working prototype of the “WMS factory” tool <ul><li>Mapserver vs.Geoserver </li></ul><ul><li>Natural Environment Framework (NEF) </li></ul><ul><li>GIS Library to process user-uploaded data: </li></ul><ul><ul><li>Gdal/Ogr </li></ul></ul><ul><ul><li>Geotools </li></ul></ul>Implementation Questions
  39. 39. Choice of WMS <ul><li>Minnesota WMS </li></ul><ul><ul><li>Existing work done with UKLP </li></ul></ul><ul><ul><li>Tested for INSPIRE compliance (with EDINA extensions) </li></ul></ul><ul><ul><li>Very fast (given our requirements) </li></ul></ul><ul><ul><li>Easy to create dynamic WMS instances </li></ul></ul><ul><li>Geoserver 2.1 RC4 (released 5 th April) </li></ul><ul><ul><li>Still a Release Candidate </li></ul></ul><ul><ul><li>There is a community plugin funded by OS which does not yet implement all the necessary extensions for full Technical Guidance v3 compliance. </li></ul></ul>
  40. 40. User-uploaded data <ul><li>Vector and/or raster ? </li></ul><ul><ul><li>SHAPE, GML (>3.1.1), E00 </li></ul></ul><ul><ul><li>Geotiff, JPEG etc. </li></ul></ul><ul><li>Metadata : </li></ul><ul><ul><li>The input data alone are not sufficient for a production WMS Service. </li></ul></ul><ul><ul><li>Should the user provide extra metadata? To what extent? </li></ul></ul><ul><ul><li>source , scale , accuracy and intended audience of a particular data set. </li></ul></ul>
  41. 41. Data Quality <ul><li>Questions to be answered: </li></ul><ul><ul><li>What is the age of the data? </li></ul></ul><ul><ul><li>Where did it come from? </li></ul></ul><ul><ul><li>In what medium was it originally produced? </li></ul></ul><ul><ul><li>What is the areal coverage of the data? (probed) </li></ul></ul><ul><ul><li>What projection, coordinate system, and datum were used in maps? (probed) </li></ul></ul><ul><ul><li>In what format is the data kept? </li></ul></ul><ul><ul><li>How was the data checked? </li></ul></ul><ul><ul><li>Why was the data compiled? </li></ul></ul><ul><ul><li>What is the reliability of the provider? </li></ul></ul>
  42. 42. Current Plan <ul><li>Continuous incremental improvements: </li></ul><ul><ul><li>Design and implement a prototype that can be used within a month. </li></ul></ul><ul><ul><li>Use a “point of contact” to provide feedback after each development iteration </li></ul></ul><ul><ul><li>Ensure that the project constantly satisfies user requirements. </li></ul></ul><ul><ul><li>Ensure that the project constantly satisfies user requirements. </li></ul></ul>
  43. 43. Simple mapping application <ul><li>Essential for demonstration purposes </li></ul><ul><li>Based on the Wales Ecosystem portal if possible (an OpenLayers client) </li></ul>
  44. 44. <ul><li>WP4: Access Control </li></ul>
  45. 45. Shibboleth <ul><li>Internet2 consortium </li></ul><ul><li>Open source package for web Single Sign On across admin boundaries based on standards: </li></ul><ul><ul><li>Security Assertion Markup Language (SAML)‏ </li></ul></ul><ul><li>Organisations can exchange user information and make security assertions by obeying privacy policies </li></ul><ul><li>Devolved authentication – maintain and leverage existing user management </li></ul><ul><li>Enables finer grained authorisation through use of attributes </li></ul><ul><li>Small coordination centre, large federation of organisations (service and identity providers) </li></ul><ul><li>Many Shibboleth Access Management Federations: </li></ul><ul><ul><li>https:// www.aai.dfn.de /links/ </li></ul></ul><ul><ul><li>https://spaces.internet2.edu/display/SHIB/ShibbolethFederations </li></ul></ul>
  46. 46. UK Access Management Federation <ul><li>Managed by JISC Collections (previously JANET) and EDINA </li></ul><ul><ul><li>Federation Operator: JISC Collections </li></ul></ul><ul><ul><li>Technical and Operational Support: EDINA </li></ul></ul><ul><li>840 Member Organisations (IdPs and SPs) </li></ul><ul><li>Approximately 8 million users </li></ul><ul><li>Cost of running is not insignificant </li></ul>
  47. 47. Key Roles within an Access Management Federation SP SP SP SP SP SP SP SP SP SP SP Coordinating Centre Federation Service Providers Identity Providers Users Organisations SP SP IdP IdP IdP IdP IdP IdP
  48. 48. Example Shibboleth Login Procedures http:// www.switch.ch/aai/demo/medium.html
  49. 49. Why put effort into federated access control? <ul><li>Authentication is the process of verifying that claims made concerning a subject, eg, identity, who is attempting to access a resource are true, ie, authentic </li></ul><ul><li>Frequently, SDI content and service providers need to know who is accessing their valuable, secure, protected, etc, data </li></ul><ul><li>The ability for a group of organisations with common objectives, ie, a federation, to securely exchange authentication information is a powerful SDI enabler </li></ul><ul><li>Article 19 of the INSPIRE Directive ”…Member States may limit public access…etc, etc”. </li></ul><ul><li>Even more so if removing some of the barriers to interoperability… </li></ul>
  50. 50. Why put effort into federated access control round OWS? <ul><li>Open geospatial interoperability standards underpin SDI </li></ul><ul><li>OGC Standards agnostic about security </li></ul><ul><li>Grand challenge: lack of a genuinely interoperable security solution a major barrier to all sectors </li></ul><ul><li>EU requested that ESDIN project focus on testing practical existing solutions </li></ul><ul><li>Prior work by same team (JISC funded SEE-GEO project) </li></ul><ul><ul><li>Demonstrated Shibb Access Control around WMS </li></ul></ul><ul><ul><li>No changes to the OWS interface specification </li></ul></ul><ul><ul><li>No changes to the core mainstream Shibboleth </li></ul></ul>
  51. 51. Why put effort into federated access control round OWS? <ul><li>Open geospatial interoperability standards underpin SDI </li></ul><ul><li>OGC Standards agnostic about security </li></ul><ul><li>Grand challenge: lack of a genuinely interoperable security solution a major barrier to all sectors </li></ul><ul><li>EU requested that ESDIN project focus on testing practical existing solutions </li></ul><ul><li>Prior work by same team (JISC funded SEE-GEO project) </li></ul><ul><ul><li>Demonstrated Shibb Access Control around WMS </li></ul></ul><ul><ul><li>No changes to the OWS interface specification </li></ul></ul><ul><ul><li>No changes to the core mainstream Shibboleth </li></ul></ul>
  52. 52. Technology Integration Experiment Webinar <ul><li>Afternoon of Thurs 18 th November </li></ul><ul><li>Approx 30 people turned up on the day </li></ul><ul><li>EDINA, Snowflake, Cadcorp, Envitia, con terra, JRC all demonstrated: </li></ul><ul><ul><li>Different clients (desktop, browser, proxy) </li></ul></ul><ul><ul><li>Different services (WMS and WFS) </li></ul></ul><ul><ul><li>Different federations (ESDIN and BKG) </li></ul></ul>
  53. 53. OSI - Outcomes <ul><li>Using Shibboleth to protect OWS is practical </li></ul><ul><li>Not particularly difficult on server side </li></ul><ul><li>Not particularly difficult with browser based clients </li></ul><ul><li>More subtle with desktop based clients but possible with some effort in short space of time </li></ul><ul><li>This kind of “IE testbed” approach appreciated by participating OGC members </li></ul><ul><li>Highly likely community support and tooling will be available if decision made to operationalise </li></ul><ul><li>Draft Engineering Report (OGC 11-019r1) </li></ul>
  54. 54. An INSPIRE Federation? <ul><li>One federation and every legally mandated organisation joins </li></ul><ul><li>Multiple federations: one in each country and one pan-European </li></ul><ul><li>One federation: one organisation in each country, the INSPIRE point of contact joins the single pan-European federation and acts as the gateway for all the other legally mandated organisations in the country that are standing up INSPIRE services </li></ul>
  55. 55. An INSPIRE Federation? OWS Providers Member State organisations, eg, INSPIRE Points of Contact WMS Key organisations, eg. EEA, JRC WMS WMS WMS WMS WMS WFS WFS WFS WFS WFS WFS Coordinating Centre IdP IdP IdP IdP IdP IdP
  56. 56. Workshop at INSPIRE Conference in June <ul><li>Title: Shibboleth Federations and Secure SDI: Outcome and Demonstrations from the OGC Web Service Shibboleth Interoperability Experiment </li></ul><ul><li>Original intention is a re-run of the Nov 2010 “plugfest” </li></ul><ul><li>More public, slicker </li></ul><ul><li>More member state NMCA’s in ESDIN Federation </li></ul><ul><li>Maybe get more system suppliers to modify their software </li></ul><ul><li>Up the level of discussion </li></ul><ul><li>IOC Task Force Involvement? </li></ul>
  57. 57. IGIBS Deliverables (from proposal) INSPIRE Conference June, Edinburgh <ul><li>Demo of UK access management technology being used to secure public sector services in combination with academic sector services </li></ul><ul><li>Recommendations for further work </li></ul>WP4 <ul><li>Working prototype of the “WMS factory” tool </li></ul><ul><li>Simple mapping application </li></ul><ul><li>Technical recommendations for what is necessary to take the “WMS factory” tool into production </li></ul><ul><li>Technical suggestions for enhancements to the relevant components of the UK academic SDI </li></ul><ul><li>Technical suggestions for taking the mapping application forward </li></ul>WP3 <ul><li>Report articulating real world end user problems that drove project </li></ul><ul><li>Best Practice model for using UK academic SDI at the dept level </li></ul><ul><li>Report articulating future requirements </li></ul>WP2 <ul><li>Project website; wiki and blog </li></ul><ul><li>Programme reporting and project management documentation </li></ul>WP1

×