Integrated Fisheries Management Workshop Strategy

1. Technical Requirements/ Development/ Maintenance and Relevance of FOS, oneFish and FI Integrated Information Strategy Presentation for Workshop “Considerations on the proposed ACP Fish II Fisheries Management Knowledge Exchange System – FMKES” Monday 7th July 2003. FAO Rome Ian Pettman, SIFAR ACP Fish II - FMKES Workshop, 7 July 2003

2. Based on the parameters we have so far started to define: Users and user needs, Resource types, Fostering participation Themes/Topics Management arrangements And the basic constraints agreed: Low cost software Non-commercial Built on existing systems if available Link and be interoperable with existing systems. Where are we? ACP Fish II - FMKES Workshop, 7 July 2003

3. What strategies for the Technical requirements etc. • Define functionalities and prioritise • Define interoperability strategies • Consider options for: • Use of mark up standards • Controlled or uncontrolled vocabularies ACP Fish II - FMKES Workshop, 7 July 2003

4. What functionalities are required? –Slide 1 • Internet based system • A range of user access permissions (browser, registered, editor, etc..) • A range of user languages supported + • Interface translation (design criteria) • Metadata translation (add form design) • Resource translation (upload functionality) • Discussions (summaries in several languages, machine translation tools ?) • A system of indicating target audience level • User defined themes/topics (changeable) ACP Fish II - FMKES Workshop, 7 July 2003

5. What functionalities are required? –Slide 2 • A set of resource types? (using metadata standards?) • A method of uploading and downloading resources remotely • Various “publishing” methods – remote printing, RSS syndication • A method of “sharing” resources from other information systems (non-editable) • A method of automatic allocation of resource to themes • Data quality control systems (Editors etc) • Discussion facilities (discussions, comments, mentoring, Q&A systems…) • Virtual communities spaces, home rooms for small groups (similar to VOs?) • Online events and conferences? – real-time events? ACP Fish II - FMKES Workshop, 7 July 2003

6. What functionalities are required? –Slide 3 • Directory functions for individuals and organisations • Prompting systems (for editors, expert query answering, translating etc..) • Newsletter system (by profile? …) • Browsing methods and search (simple and advanced) • Most frequently accessed items • Range of input systems (manual online; manual offline; bulk upload?; “shared”, RSS syndication… ) • Flag ACP inputs v non-ACP inputs? ACP Fish II - FMKES Workshop, 7 July 2003

7. What functionalities are required? –Slide 4 • Timely information (deletion dates; archiving..) • Distance learning? • Gap highlighting? (rolling profile updates, newsletter requests…) • Access restrictions to topics and resources? • Alternative dissemination: • CD-ROM • Web to Email • Snail mail • Tell a friend… • Radio outputs…….. ACP Fish II - FMKES Workshop, 7 July 2003

8. Standards – why should they be used (if at all) and when? • Resource standards • Dublin Core • AgMes • Activity standards • IDML • CERIS • Etc ACP Fish II - FMKES Workshop, 7 July 2003

9. Decision on controlled or uncontrolled vocabulary • Glossaries • Thesauri • Ontologies ACP Fish II - FMKES Workshop, 7 July 2003

10. What is an Ontology? • [Gruber 1993] “A specification of a conceptualization”. • An ontology defines a common vocabulary for users who need to share information in a domain (e.g. fisheries) • includes machine-interpretable definitions of basic concepts in the domain and the relations among these concepts. ACP Fish II - FMKES Workshop, 7 July 2003

11. The Ontology Spectrum An ontology spectrum produced by Deborah L. McGuinness, Associate Director, Knowledge Systems Laboratory, Stanford University ACP Fish II - FMKES Workshop, 7 July 2003

12. General system requirements • Well designed user interface • Good performance speeds • Keep it lean……… • Keep it dynamic as “user needs” change • Interoperable – based on international mark up standards and controlled vocabulary/ontology • Focus statement ACP Fish II - FMKES Workshop, 7 July 2003

13. Development • Hit the ground running (min development time) • Use oneFish as the “Store” for the FMKES (eliminates populating delay, keeps FMKES clean..) • Coming soon developments …(strategy) • New modules – build, open source or buy • Produce regular promotional, news (& training?) materials for the users of FMKES (whilst the development is progressing) • Set up interoperability agreements and systems. ACP Fish II - FMKES Workshop, 7 July 2003

14. What maintenance will be required? • Ensure resources for a maintenance developer? • Systems administrator/chief editor • Editor for newsletter, online conferences… • If using an ontology – regular updating and maintenance will be required – system/ process and resources • Translation…. ACP Fish II - FMKES Workshop, 7 July 2003

15. Summary • Technical Requirements • Define functionalities and prioritise • Define interoperability needs • Decide on standards and vocabulary control • Development • Define strategy and timetable • Maintenance • Don’t underestimate ACP Fish II - FMKES Workshop, 7 July 2003

16. End of Presentation Move on to Discussion. ACP Fish II - FMKES Workshop, 7 July 2003

17. Users and user needs • User groups identified: • Policy makers (decision makers) • Industry Associations • NGOs • Fishing Unions • Information intermediaries/ Extension workers • Experts • Fishers themselves (when empowered to manage) • Editors/ Data quality people ACP Fish II - FMKES Workshop, 7 July 2003

18. Fisheries Ontology Service Project Presentation for Workshop “Considerations on the proposed ACP Fish II Fisheries Management Knowledge Exchange System – FMKES” Monday 7th July 2003. FAO Rome

19. What is an Ontology? • [Gruber 1993] “A specification of a conceptualization”. • An ontology defines a common vocabulary for users who need to share information in a domain (e.g. fisheries) • includes machine-interpretable definitions of basic concepts in the domain and the relations among these concepts. ACP Fish II - FMKES Workshop, 7 July 2003

20. The Ontology Spectrum An ontology spectrum produced by Deborah L. McGuinness, Associate Director, Knowledge Systems Laboratory, Stanford University ACP Fish II - FMKES Workshop, 7 July 2003

21. Why have an Ontology? – Slide 1 • Simple Ontologies provide • A controlled vocabulary to aid resource indexing • Site organization and navigation support. • Browsing support • Search support – query expansion (plurals, synonyms, languages, etc) • “Sense disambiguation” support ACP Fish II - FMKES Workshop, 7 July 2003

22. Why have an Ontology? – Slide 2 • Structured Ontologies provide: • Consistency checking • Completion • Interoperability support • Exploitation of generalisation/specialisation information • Support for structured, comparative and customised search ACP Fish II - FMKES Workshop, 7 July 2003

23. What is involved in building one? • Methodology (for ontology building) • Language (for ontology representation) • Tools (for ontology building) • Environment –maintenance, versioning, etc. • Applications interfaces (APIs) ACP Fish II - FMKES Workshop, 7 July 2003

24. FOS Project – Slide 1 • Partners and initial objectives • FIGIS, WAICENT, SIFAR, ASFA & IP-CNR • Initial Objectives • “Proof of concept” for integration of 4 existing sources (Ref Tables and DTDs of FIGIS; ASFA thesaurus; fishery part of AGROVOC; and oneFish Topic Trees) • Collect new concepts and terms for an Enhanced Online Fisheries Thesaurus ACP Fish II - FMKES Workshop, 7 July 2003

25. FOS Project – Slide 2 • Methodologies, languages and tools chosen • Ontoclean & ONIONS • Loom; DAML-OIL; RDFS • Loom-Ontsaurus; OilEd; KAON • Present position • Future and possible relevance to FKMES, oneFish and FI Integrated Information strategy ACP Fish II - FMKES Workshop, 7 July 2003

26. End of Presentation Move on to Discussion. ACP Fish II - FMKES Workshop, 7 July 2003

27. ACP Fish II - FMKES Workshop, 7 July 2003