9254f250cc77544b42dd1f84da1de6ae.ppt
- Количество слайдов: 33
Electronic certification - status of IPPC e. Phyto developments Rebecca Lee NAPPO Technical Director e. Phyto Steering Committee member November, 2012 www. nappo. org Ottawa, Canada
Steps in the development of e. Phytos • Netherlands (2007), Ottawa (2009), Korea (2011), Paris (2012) meetings • Steering committee in place • Working Groups: 1 - XML schema 2 - Code lists 3 - Communication protocols • Brazil training workshop, November, 2012
Steps in the development of e. Phytos (cont. ) • July 1 – October 20, 2012 IPPC member consultation: “Draft Appendix to ISPM 12: Electronic certification, information on standard XML schemes and exchange mechanisms” • Meeting of WGs 2 and 3 held Sept 10 to 13, 2012, in Paris
Steps in the development of e. Phytos (cont. ) Current schedule: ü Country comments received until October 20 ü Revision of country comments and Appendix 1 at spring 2013 IPPC Standards Committee meeting ü Substantial concerns commenting process – to end of Sept 2013 and new draft to SC in Nov 2013 ü Included in agenda for approval during CPM 2014
e. Phyto WG 1: Issues to consider • The structure of the XML message • What elements are in the schema • What are the names of the elements e. g. Country, issuing party name • Coverage of all ISPM 12 elements
UN/CEFACT Schema • UN/CEFACT: Centre for Trade Facilitation and e-business • UN/CEFACT standard schema • Covers Sanitary and Phytosanitary issues • This schema was adapted for the phytosanitary context (ISPM 12) • Agreement needed on use of fields
How does it work? • XML language, communication between computer systems • All certificate elements in the XML message • Secure transmission between NPPOs
What is XML • Sheryn to provide
Issues for WG 1(con’t) • • • Data mapping, e. g. treatments, import permit etc. Mixed consignments, e. g. containing roses and chrysanthemum cut flowers; mixed products, e. g. bouquets that consist of roses and gypsophila cut flowers. Data mapping of elements that are specific for a re-export certificate and for a replacement certificate.
e. Phyto WG 2: Harmonisation of contents: Codes • Why codes? Fullest use of electronic system possible – – – Avoids mismatches by typing errors Unambiguous spelling of names, etc. Language independent Makes digital checks possible More efficient Flexibility to update
Codes • Botanical names – plants: will use EPPO list • • Scientific names – pests (EPPO list) Commodity classes Treatments Additional declarations Note: any codes already used, eg ISO codes for country and points of entry, will be used here as well, as per UN/CEFACT
e. Phyto WG 3 Exchange mechanism ØObjective is to complete the methods for transfer, security measures and validation for Appendix 1 of ISPM 12 for the exchange of information between countries.
e. Phyto EWG Achievements
WG 1 • Version 1. 0 of a global data map for electronic phytosanitary certification • Solutions for consignments consisting of: - a single lot containing only a single product - different lots, each of them containing only a single product - a lot containing different plant species or plant products - UNCEFACT will be approached to request an additional certificate type, for re-export situations - there is no electronic equivalent for alteration, but in these cases a replacement certificate is issued.
XML message • • • • • • •
Example of XML Schema ISPM 12 Element E-Phyto Schema Element Paper Example Schema example Certificate name/model SPSExchanged. Document_Type. Code Export format
Electronic equivalent of a certified copy • It is the responsibility of trade to store and provide certified copies for re-export certification. • A certified copy can be: – a decrypted version of the original certificate: contents or the authenticity of the certificate cannot be changed. – a print out of the certificate data which is stamped, dated and countersigned by an NPPO • either in a format similar to phytosanitary certificates • or as a straight print out of a XML message
• • • • • • • • • xml version="1. 0" encoding="utf-8" ? >
WG 2 – example of code lists
EPPO codes: a few general principles For plant pests and pathogens: 6 letters = 4 (genus) + 2 (species) B E M I T A The species Bemisia tabaci: BEMITA An unspecified species of the genus Bemisia: BEMISP Genus Bemisia: 1 BEMIG Aleyrodidae Family: 1 ALEYF Sternorrhyncha Suborder: 1 STERS Hemiptera Order: 1 HEMIO Insecta Class: 1 INSEC Animal Kingdom: 1 ANIMK Courtesy: EPPO, 2012
EPPO codes: a few general principles (cont. ) For cultivated and wild species (including weeds) 5 letters = 3 (genus) + 2 (species) S O L T U Solanum tuberosum: SOLTU An unspecified species of Solanum: SOLSS Genus Solanum: 1 SOLG Solanaceae Family: 1 SOLF Polemoniales Order: 1 POMO Dicotyledons Group: 1 DICS Magnoliophyta Division : 1 MAGP Plant Kingdom: 1 PLAK Courtesy: EPPO, 2012
EPPO codes: a few general principles (cont. ) 1 biological entity = 1 unique code Change of preferred scientific name: Gnorimoschema absoluta = Tuta absoluta => The code GNORAB remains the same Newly described species: Phytophthora pinifolia => PHYTPF is newly created New subspecies: additional codes Xylella fastidiosa = XYLEFA Xylella fastidiosa subsp. multiplex => XYLEFM Xylella fastidiosa subsp. pauca => XYLEFP Xylella fastidiosa subsp. sandyi => XYLEFS Courtesy: EPPO, 2012
Special form on the web to request new codes Courtesy: EPPO, 2012
WG 3 (transmission protocol) • Message transmission is between two NPPOs. • To authenticate security SSL certificate – use X 509 certificate (provides secure method for recognition of two parties) – it’s part of the envelope and will go with each message, like a fingerprint. – So, no user name or password; no certifying officer • XMLDSIG exists for digital signatures. • Discussion on Web Service Definition Language (WSDL) – Definition: it’s the language you can use to talk to the exporting country, what questions to ask to get the answer you want.
Observations • Existing bilateral exchanges are based on Web services • Functionality more or less the same • Implementation differs (slightly) • Standardisation of the implementation will reduce cost of IT solutions • Conclusion : Create a best practice WSDL that can be used by newcomers • Existing applications can migrate in their own timeline Courtesy: A. J. Moret, 2012
Functionality • Find certificates issued by the exporting NPPO • Get (Download) certificates from the exporting NPPO • Report the status of a downloaded certificate to the exporting NPPO • Monitor the status of a certificate • Detect if the network and services at the exporting country are available (Hart beat) Courtesy: A. J. Moret, 2012
Exchange mechanism Electronic certificates issued in Exporting country 28
Electronic certificates received in Importing country
Example of Communication Protocol Action Service Description 2. 1 Find a list of certificates Find_certificate Put the request to the NECS to return all certificate numbers that meet the input criteria. Immediately after this Request the NECS returns the list of numbers 2. 2 Download a list of certificates get_certificate Put the request to the NECS to return all certificates s that meet the input criteria. Immediately after this request the NECS returns all the certificates 2. 3 Change the status of a certificate Put_certificate_status Put the request to the NECS to change the status of a list of certificatesto the specified value. Immediately after this request the NECS returns the process result for every individual certificate (Succes or Failed with reason) 2. 4 Show the status of a certificate Show_certificate_status Put the request to the NECS to show the status of a list of. Immediately after this request the NECS returns the status for every individual certificate (Succes or Failed with reason) 2. 5 Show status of the NECA Hart_beat Put the request to the NECS to confirm that the NECS and the network between the NECS and NICS are operational. Immediately after this Request the NECS returns the message OK Courtesy: A. J. Moret, 2012
Communication Diagram Courtesy: A. J. Moret, 2012
Steps in the development of e. Phytos (reminder) • Current schedule: ü Country comments received until October 20 ü Revision of country comments and Appendix 1 at spring 2013 IPPC Standards Committee meeting ü Substantial concerns commenting process – to end of Sept 2013 and new draft to SC in Nov 2013 ü Included in agenda for approval during CPM 2014
Questions? Suggestions?


