Overview of small drafting group output on Interpretation documents

Slides:



Advertisements
Similar presentations
Halton Housing Trust Customer Scrutiny Panel An introduction to our Service Reviews.
Advertisements

Challenging Behaviour: a unified approach- refresh
EPICS Conceptual Review Template Notes:  Use the template as a guide to preparing your presentation….you may add, subtract, or rearrange as needed to.
WLTP GTR 15 WLTP-10-34e Report by Drafting Coordinator, Serge Dubuc
1 of 4 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
The University of Adelaide Poster Power: Meaning and Message Peter Murdoch March 2014 PREPARING GOOD LOOKING DOCUMENTS.
Lesson 4: Formatting the Worksheet
 Read through problems  Identify problems you think your team has the capacity and interest to solve  Prioritize the problems and indicate the.
M253 Team Work in Distributed Environments Week (3) By Dr. Dina Tbaishat.
IEEE P1603 reviewer’s guideline Wolfgang Roethig, WG chair.
The Essentials of Technical Communication Highlights from: Chapter 2: Writing for your readers Chapter 7: s, Memos, and Letters.
7 Adding Signatures to s Step 1 Click on ‘Tools’ option in the toolbar at the top of the page. Click on ‘Options’
Coordinators' day on FP7 Project Negotiation Description Of Work Annex I Griet Van Caenegem DG CNECT R5 Programme Operations May 28, 2013.
1 January 31, Documenting Software William Cohen NCSU CSC 591W January 31, 2008.
CMGT 430 Week 4 Learning Team Presentation Check this A+ tutorial guideline at Week-4-Learning-Team-Presentation.
process and procedures for assessments
Working in Groups in Canvas
DRM SIAC Paper Destruction Working Group 13 September 2011
REPORTING SDG INDICATORS USING NATIONAL REPORTING PLATFORMS
Safeguards- Feedback on Safeguards ED-2 and Task Force Proposals
Structure of the Code Don Thomson, Task Force Chair IESBA Meeting
Reviewing Documents Guided Lesson.
Structure of the Code Phase 1
Summaries due next week
Conducting the performance appraisal
Testing a Solution.
GCE Applied ICT G040: Lesson 08 Planning and Drafting Communications
Integrating Word, Excel, and Access
Outcome TFCS-07 // August NH Den Haag, NL
Outcome TFCS-11// February Washington DC
Software Word Processors.
EPICS Conceptual Review Template Notes:
Structure of the Code – Phase 2 TF Comments and Proposals
Conducting the performance appraisal
<month year> doc.: IEEE < e>
Microsoft Word Reviewing Documents.
Outcome TFCS-11// February Washington DC
Structure of the Code Phase 1
Outcome of TFCS-12 - summary slides - (detailed meeting minutes will be provided separately) April The Shilla Seoul, ROK.
GRSG-113 Agenda point 5 – Awareness of Vulnerable Road Users proximity
Informal document GRPE-74-20
Unit 01 –Website Development
Transmitted by the IWVTA Informal Group
Effective Introductions
November 18 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG4i September Closing Report Date Submitted:
Chapter 2 Building Health Skills and Character
Structure–Feedback on Structure ED-2 and Task Force Proposals
A few tricks to take you beyond the basics of Microsoft Office 2010
Our Procedures: The rules of the road
Improving assessment of GES Draft conclusions and Way forward
IESBA Meeting New York September 26-30, 2016
Informal document GRVA nd GRVA, 28 Jan Feb. 2019
How Effective are You? A study on how supervisory organizations in health care are concerned with the effectiveness of supervision Wouter Sparreboom.
Transmitted by the IWVTA Informal Group
Instructions Create a PowerPoint presentation as a group.
Overview US Paper C2-7.INF
Status report of TF-CS/OTA
Requirements Validation – I
Why a „test phase“? Overview
AICT5 – eProject Project Planning for ICT
The ETSI Standardisation Process
UK MoUs and Tier-1/A experiment shares
WG A ECOSTAT Intercalibration guidance : Annexes III, V, VI
Transmitted by the IWVTA Informal Group
Alignment of Part 4B with ISAE 3000
A few tips to help get you started
Inputs Regard to “Test Phase” to TFCS
Summary on initial findings
Overview of small drafting group output on Interpretation documents
EDR/DSSAD IWG Status Report
Presentation transcript:

Overview of small drafting group output on Interpretation documents

Small drafting group consisted of members from: Background Small drafting group consisted of members from: RDW, CLEPA, OICA Chaired by UK with OICA secretariat Task Reformat the interpretation documents to something more workable Approach adopted Agree rules for editting Agree an approach Initiate editting Suggest a way forward

Editting rules Content should not be added Text should be concise Text should not go beyond legislative requirement Highlight issues for wider task force if we cannot decide on how to edit them Try to adopt a similar style

Agreed style - three boxes Editting approach Agreed style - three boxes An explanation of the requirement. This may include (where needed): The aim of the outcome The expected outcome of the requirement Clarifications How to evidence the requirements What processes or information may be presented What standards might be used (if it is accepted to refer to standards) Points for the task force to consider These will be deleted when the test phase ends

Editting approach used UK suggested text used as a basis Text reviewed to check for: Grammar Readability Conciseness Duplication Content was discussed Some edits made to refine UK/RDW suggestions in order to make the entries concise and clear Points of note were highlighted Overall discussions on the content was deferred to the taskforce

Summary We have a process for editting We have a suggested format Editting the document is hard work Initial progress has been made, we want confirmation that this is okay before continuing A way forward was identified

Next steps Confirmation that the approach adopted is okay Suggested next steps for finishing re-formatting RDW and JS to reformat the CS and SU documents according to the agreed rules and styles SDG to confirm they are okay with the edits Task force to be provided with „clean“ and „dirty“ versions Options for further refining the content: SDG to refine the document then provide it to the task force to further refine and develop the document by August 18th (in time for its next meeting) Task force to take on the task of refining and developing the task force (with meetings scheduled to achieve this)