1 / 14

ISIC and CPC Maintenance and Revision Policies Expert Group Meeting May 18-20, 2011

ISIC and CPC Maintenance and Revision Policies Expert Group Meeting May 18-20, 2011. Terminology and Scope. - Basic Terms of UPDATE and REVISION Criteria for UPDATE Class in ISIC or subclass in CPC added or removed within existing structure

nani
Download Presentation

ISIC and CPC Maintenance and Revision Policies Expert Group Meeting May 18-20, 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISIC and CPC Maintenance and Revision PoliciesExpert Group Meeting May 18-20, 2011

  2. Terminology and Scope - Basic Terms of UPDATE and REVISION • Criteria for UPDATE • Class in ISIC or subclass in CPC added or removed within existing structure • Adjustment of activities between existing classes in ISIC or subclasses in CPC • Multiple classes or subclasses added or removed with no change to structure

  3. Terminology and Scope -Criteria for REVISION -Renumbering a substantial portion of the classification - Restructuring or regrounping a substantial portion of the classification (25%?, 50%?, other) - New concepts for classes in ISIC or subclasses in CPC

  4. Terminology and Scope Numbering and Version Control Update – use decimal increment Revision – use integer increment

  5. Periodicity of Changes Earlier EG Proposal: Update industry and product every 5 years, consider revision every 10 years Firm or flexible?? Applies to all members of the family??

  6. ISIC and CPC Maintenance and Revision Policies 2nd part

  7. Update or revision to ISIC and the CPC • 2 issues to consider: • Formal process of soliciting input from users • questionnaire for national statistical offices (ex: annex 2) • TSG to evaluate the responses and make formal recommendations to the Expert Group • Formal mechanisms to collect and act on implementation and interpretation questions and problems. • Collect information on the problems spotted by users during implementation of the classification. • Agree on a solution for each case! This requires a decision mechanism which includes an agreement on a date for implementation if significant changes. • Document all decisions! • Use the output of the correction/clarification as an input in the process of the next update/revision of the classification(s) concerned. Name of the presentation

  8. Collection of information on possible problems • Spontaneous request of help to UN from a country, by Email, letters, phone calls etc. • Organizing a web based discussion forum where users are able to express their concerns about issues related to the classification and receive feedback from other users. • Organizing a questionnaire to users where they are asked for comments on possible classifications related problems encountered. Name of the presentation

  9. Agreement on a common solution Wording errors Contradictions Translation errors Editorial amendments Errata Problems of codification/ boundaries between classes (no conceptual issue concealed within the clarification) Clarification beyond dispute Set of clarifications Name of the presentation

  10. Agreement on a common solution Rullings of interpretation New activities emerged Interpretation Classification should be revised Basic concepts become irrelevant Change Name of the presentation

  11. Agreement/implementation • In the discussion forum, convergence is not always evident and after some time of discussion the tendency often is that no common position seems to emerge. • In this case a decision should, whenever possible, be taken, taking into account the different positions, even though it can be just a convention. • Decision could be taken by the Technical Expert Group on classifications. • permanent item in their agenda meetings on "rulings", • Entry into force • just after each TEG meeting or • on the 1/1 of the year following the meeting. • This periodicity is nevertheless, not always frequent enough and in this case the members of the TEG group could be consulted via the web based UN classifications discussion forum. Name of the presentation

  12. Documentation • Errors • Inconsistencies • Problems related to interpretation of the definitions or explanatory notes • How? Should be traced! "rulings" data base Name of the presentation

  13. Use it in next revision • In next revision/update: • errors or inconsistencies detected should be corrected • clarifications should be included in the explanatory notes/definitions of the revised version. • For this reason is important to keep records of all in a centralized way • A coordinated approach to the timing of updates/revisions of classifications is crucial when concepts and definitions are linked with other classifications. Name of the presentation

  14. Thanks for your attention Questions? Comments? Name of the presentation

More Related