PARCC Item Development Technical Guide

PARCC Item Development Technical GuideV 0.652013-09-12Copyright © 2013, Partnership for Assessment of Readiness for College and CareersThis work is made available under the terms of the Creative Commons Attribution 3.0 Unported (CC BY 3.0)http://creativecommons.org/licenses/by/3.0/

PARCC Item Development Technical GuideThis is a draft of the PARCC Item Development Technical Guide. The document has not been finalized as PARCCpolicies and is subject to revision.Produced by: Partnership for Assessment of Readiness for College and Careers (PARCC)PARCC1400 16th Street NW, Suite 510Washington, DC 20036Phone +1 202-419-1571Fax +1 202-828-0911http://www.parcconline.org/Once completed the Guide will be available on the World Wide Web at:http://www.parcconline.org/technologyThe contents of the Guide were developed under a grant from the U.S. Department of Education. However, itscontents do not necessarily represent the policy of the U.S. Department of Education and the reader should notassume endorsement by the Federal government.ii V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideContentsList of Figures .........................................................................................................................................................viList of Tables ........................................................................................................................................................ viiCode Listings ..........................................................................................................................................................ixIntroduction ............................................................................................................................................................ 1Item Development Workflow ........................................................................................................................... 3Style .................................................................................................................................................................. 6Editorial and Language Guidelines ..................................................................................................................... 6Online Art Guidelines ......................................................................................................................................... 6Online Layout Guidelines ................................................................................................................................... 8Paper Art Guidelines .......................................................................................................................................... 8Paper Layout Guidelines .................................................................................................................................... 9Audio and Video Media Guidelines .................................................................................................................... 9Accessible Content Guidelines ........................................................................................................................... 9Accessibility .................................................................................................................................................... 11PARCC APIP Requirements ............................................................................................................................... 12PARCC APIP Embedded Supports, Accessibility Features and Accommodations ............................................ 13PARCC APIP Accessibility Item Companion Materials ...................................................................................... 15PARCC APIP Accessibility Item Accessibility Info and Access Elements ........................................................... 42PARCC APIP Accessibility Item Inclusion Order ................................................................................................ 43PARCC APIP Accessibility Metadata ................................................................................................................. 45PARCC APIP Accessibility Elements .................................................................................................................. 45Test Clients ..................................................................................................................................................... 49Device Descriptions .......................................................................................................................................... 49Student Toolbox ............................................................................................................................................... 50Federal Regulatory Compliance ...................................................................................................................... 52Item Encoding and Behavior ........................................................................................................................... 53PARCC APIP QTI Item Mapping ........................................................................................................................ 54QTI Items .......................................................................................................................................................... 57PARCC APIP QTI Interactions ............................................................................................................................ 57PARCC Interactions ........................................................................................................................................ 104PARCC APIP QTI Interaction Elements ........................................................................................................... 106PARCC APIP Custom Interactions and Technology-Enhanced Items .............................................................. 112PARCC APIP Portable Custom Interactions .................................................................................................... 112Composite Items ............................................................................................................................................ 113V 0.65: Public Draft 20130912iii

PARCC Item Development Technical GuidePARCC Content Elements ............................................................................................................................... 114PARCC Content Classes .................................................................................................................................. 114PARCC APIP QTI Cascading Style Sheets......................................................................................................... 114MathML .......................................................................................................................................................... 114PARCC APIP Item Fragments .......................................................................................................................... 116PARCC APIP QTI Rubric Blocks ........................................................................................................................ 117PARCC APIP QTI Response Processing ........................................................................................................... 118PARCC Response Processing Custom Operators ............................................................................................ 130Item Templates .............................................................................................................................................. 130Modal Feedback ............................................................................................................................................. 130Adaptive Items ............................................................................................................................................... 130Time Dependent Items ................................................................................................................................... 130LTI-Based Items and Resource ....................................................................................................................... 130Metadata ...................................................................................................................................................... 131Item-Level Metadata ...................................................................................................................................... 131Asset-Level Metadata .................................................................................................................................... 131Section-, Test- and Manifest-Level Metadata ................................................................................................ 131Metadata Element Summary ......................................................................................................................... 132File Metadata ................................................................................................................................................. 133AfA DRD Metadata ......................................................................................................................................... 133Metadata Element Details ............................................................................................................................. 133Metadata XML Document Structure .............................................................................................................. 183Exchange ....................................................................................................................................................... 184Package Structure .......................................................................................................................................... 184PARCC APIP Item Bank Package ..................................................................................................................... 187PARCC APIP Item Package .............................................................................................................................. 191PARCC APIP Section Package.......................................................................................................................... 191PARCC APIP Test Package ............................................................................................................................... 195Item Variants .................................................................................................................................................. 200Item Packaging ............................................................................................................................................... 201PARCC APIP Manifest Elements ..................................................................................................................... 203PARCC APIP Assessment Test Elements ......................................................................................................... 207PARCC APIP Assessment Section Elements .................................................................................................... 208PARCC Entity Naming Conventions ................................................................................................................ 209PARCC Versioning Conventions ...................................................................................................................... 211Validation ...................................................................................................................................................... 212PARCC APIP Validation ................................................................................................................................... 212iv V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideLanguage, Editorial and Style Validation ........................................................................................................ 216Rendering Validation ...................................................................................................................................... 216Behavior Validation ........................................................................................................................................ 217Response Processing Validation ..................................................................................................................... 217Accessibility Validation ................................................................................................................................... 217Glossary .............................................................................................................................................................. 218Acronyms ............................................................................................................................................................ 232References .......................................................................................................................................................... 234Schemata ............................................................................................................................................................ 240RTTA APIP Profile Schemata ........................................................................................................................... 240APIP Profile Schemata .................................................................................................................................... 240General Schemata .......................................................................................................................................... 241Annex: RTTA APIP Profile ................................................................................................................................... 243Profile Versioning ........................................................................................................................................... 243APIP Accessibility Profiling ............................................................................................................................. 243APIP QTI Profiling ........................................................................................................................................... 244Metadata Profiling ......................................................................................................................................... 245Packaging Profiling ......................................................................................................................................... 245Profile Vocabularies ....................................................................................................................................... 245Annex: Response Processing Templates ............................................................................................................ 254Standard Response Processing Templates ..................................................................................................... 254PARCC Response Processing Templates......................................................................................................... 255Annex: PARCC APIP Examples ............................................................................................................................ 256PARCC Item and Interaction Examples........................................................................................................... 256PARCC APIP Item Bank Package Example....................................................................................................... 256PARCC APIP Section Package Example ........................................................................................................... 256PARCC APIP Test Package Example ................................................................................................................ 256PARCC Response Processing Template Package Example ............................................................................. 256Change Log ......................................................................................................................................................... 257V 0.65: Public Draft 20130912v

PARCC Item Development Technical GuideList of FiguresFigure 0.1: Item Development Workflow .............................................................................................................. 4Figure 1.1: Sample Art Guidelines ......................................................................................................................... 7Figure 2.1: Accessibility Elements ........................................................................................................................ 11Figure 2.2: Accessibility Element Linking Structure ............................................................................................. 42Figure 5.1: Item Structure.................................................................................................................................... 53Figure 7.1: Sample Test Structure ..................................................................................................................... 184Figure 7.2: Sample Manifest and Files ............................................................................................................... 185Figure 7.3: Sample .zip and Folder Structure..................................................................................................... 185Figure 7.4: Package .zip File and Folder Structure for Sample Test Structure ................................................... 187Figure 7.5: Sample PARCC APIP Item Bank Exchange Structure ........................................................................ 188Figure 7.6: Sample PARCC APIP Item Bank Manifest Structure ......................................................................... 188Figure 7.7: Sample PARCC APIP Item Bank .zip File and Folder Structure ......................................................... 188Figure 7.8: Sample PARCC APIP Section ............................................................................................................ 191Figure 7.9: Sample PARCC APIP Section Manifest Structure ............................................................................. 192Figure 7.10: Sample PARCC APIP Section .zip File and Folder Structure ........................................................... 192Figure 7.11: Sample PARCC APIP Test ............................................................................................................... 196Figure 7.12: Sample PARCC APIP Test Manifest Structure ................................................................................ 196Figure 7.13: Sample PARCC APIP Test .zip File and Folder Structure ................................................................ 196Figure 7.14: Sample PARCC APIP Item ............................................................................................................... 201Figure 7.15: Sample PARCC APIP Item Manifest Structure ................................................................................ 201Figure 7.16: Sample PARCC APIP Item .zip File and Folder Structure ................................................................ 202vi V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideList of TablesTable 2.1: PARCC APIP Support ........................................................................................................................... 12Table 2.2: PARCC Embedded Supports, Accessibility Features and Accommodations ....................................... 13Table 2.3: PARCC Accessibility Item Companion Materials ................................................................................. 16Table 2.4: PARCC Accessibility Related Elements ................................................................................................ 42Table 2.5: PARCC Accessibility Inclusion Order Elements.................................................................................... 43Table 3.1: Operating System Characteristics ....................................................................................................... 49Table 3.2: Hardware Characteristics .................................................................................................................... 49Table 3.3: Network Connectivity ......................................................................................................................... 50Table 3.4: Software Characteristics ..................................................................................................................... 50Table 3.5: Student Toolbox Features ................................................................................................................... 50Table 5.1: Response Type to Interaction Type Mapping ..................................................................................... 54Table 5.2: Interaction Types ................................................................................................................................ 55Table 5.3: PARCC (Technology-Enhanced) Items ................................................................................................. 56Table 5.4: assessmentItem Element Required Attributes ................................................................................... 57Table 5.5: assessmentItem Element Required Attributes ................................................................................... 57Table 5.6: itemBody Element Attributes ............................................................................................................. 57Table 5.7: math Element Attributes .................................................................................................................. 115Table 5.9: Response Processing Templates ....................................................................................................... 123Table 6.1: Metadata Element Summary ............................................................................................................ 132Table 7.1: PARCC Naming Conventions ............................................................................................................. 210Table 8.1: PARCC APIP QTI Validation ............................................................................................................... 213Table 8.2: PARCC APIP Item Accessibility Support Feature Validation .............................................................. 214Table 8.3: PARCC APIP Test Client Accessibility Feature Validation .................................................................. 215Table 8.4: PARCC Embedded Support / Companion Materials Feature Validation ........................................... 215V 0.65: Public Draft 20130912vii

PARCC Item Development Technical GuideTable 8.5: PARCC APIP Metadata and Packaging Validation ............................................................................. 216Table P.1: RTTA APIP Profile LOM Vocabularies ................................................................................................ 246Table P.2: RTTA APIP Profile CCSS Vocabularies ................................................................................................ 246Table P.3: RTTA APIP Profile CEDS Vocabularies ............................................................................................... 246Table P.4: RTTA APIP Profile APIP Vocabularies ................................................................................................ 247Table P.5: RTTA APIP Profile RTTA Vocabularies ............................................................................................... 249Table P.6: PARCC APIP Profile PARCC Vocabularies .......................................................................................... 253viii V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideCode ListingsCode Listings 2.1: Accessibility Info Example....................................................................................................... 43Code Listings 2.2: Inclusion Order Example ......................................................................................................... 44Code Listings 5.1: Composite Item Example ...................................................................................................... 113Code Listings 5.2: MathML Namespace Example: Math Element ..................................................................... 114Code Listings 5.3: MathML Namespace Example: Assessment Item Element .................................................. 115Code Listings 5.4: MathML Example .................................................................................................................. 116Code Listings 5.5: Item Fragment Example ....................................................................................................... 117Code Listings 6.1: Nominal Ordering of Metadata in an XML Document .......................................................... 183Code Listings 7.1: Example PARCC APIP Item Bank Manifest XML Document .................................................. 188Code Listings 7.2: Example Partial PARCC APIP Section Manifest XML Document ........................................... 193Code Listings 7.3: Example PARCC Assessment Section XML Document .......................................................... 194Code Listings 7.4: Example Partial PARCC APIP Test Manifest XML Document ................................................ 197Code Listings 7.5: Example PARCC Assessment Test Element XML Document ................................................. 199Code Listings 7.6: Example PARCC Assessment Section Element XML Document ............................................ 199Code Listings 7.7: Example Variant XML Document Fragment ......................................................................... 200Code Listings RPT.1: Match Correct Response Processing Template XML Document ...................................... 254Code Listings RPT.2: Match Response Response Processing Template XML Document ................................... 254Code Listings RPT.3: Match Response Point Response Processing Template XML Document ......................... 255V 0.65: Public Draft 20130912ix

PARCC Item Development Technical GuideThis Page Intentionally Left Blankx V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideIntroductionIntroductionPARCC is committed to delivering innovative, performance-based assessments using state-of-the-art technologies.Requirements for PARCC assessments and assessment items include: Leading-Edge Assessment Technologies: Support the use of new, advanced assessment technologies. Accessibility: Support access for all students and staff based on universal design principles. Interoperability: Conform to applicable industry-recognized, open-licensed interoperability standardsincluding standards for assessment items, assessment and results data, accessibility, student data, and APIs. Internet Technologies: Utilize standard and emerging Internet and web technologies for all data models,interfaces and APIs, supporting the range of devices, platforms and applications defined by PARCC. Regulatory Compliance: Comply with all relevant state and Federal laws and regulations.To satisfy these requirements, PARCC has released the technical guidelines contained herein for item developers touse when preparing assessment items and delivering them to PARCC. These technical guidelines address itemstyle, accessibility, encoding, exchange, delivery, discovery, validation and compliance criteria. The guidelines areused within a nominal item development workflow. The guidelines enable multiple, independent item developers(both current and future) to create assessment items that can be combined into different assessments and can bedelivered across multiple assessment platforms, different test clients and diverse student devices while providingconsistent item behavior, performance data capture and results.This Guide does not describe the non-technical aspects of PARCC assessment item design and development, e.g.,evidence-based assessments design principles; model content frameworks; item generation models; item review andapproval processes. It also does not describe operational and policy aspects of PARCC assessments, e.g.,assessment delivery and administration; scoring; analytics and reporting; item research studies.While the Guide is meant to be inclusive for all item developers and includes references to all source documents andtechnologies, technologists developing interoperability solutions and software (e.g., test clients, authoring tools) mayneed to refer to the source materials. Similarly, item developers will need to be familiar with the appropriate nontechnicaldocuments describing PARCC assessments, models and educational standards.While the PARCC guidelines are rooted in industry best practices and current interoperability standards, satisfyingPARCC needs requires forward-looking practices and extensions to standards. PARCC work and experiences willbe used as input to update and revise standards to align them with PARCC guidelines.This Guide is organized into sections addressing each of the major item development criteria: Item Development Workflow – Steps in the item development process and guidelines for thecorresponding item data produced at each step. Style – Editorial and language guidelines; graphic and art guidelines; and page and screen layout guidelinesfor both computer-based and paper-based items and their corresponding media assets; accessible contentguidelines. Accessibility – Accessibility guidelines for items; embedded supports and other accommodations;representing accessibility item information and accessibility metadata. Test Clients – Technical descriptions of PARCC-supported devices constraining delivery; availablestudent toolbox features for use in items. Federal Regulatory Compliance – A short summary of the relevant Federal regulations applicable to itemdevelopment. Specific guidelines to support compliance are described in other parts of this Guide. Item Encoding and Behavior – Guidelines for selecting appropriate PARCC APIP item interaction types;XML encoding of different interactions; use of custom interactions; models of technology-enhanced items;models of portable custom interactions; encoding composite items; HTML/XHTML text and contentencoding; classes and stylesheets; using MathML; encoding item fragments; encoding rubric blocks,encoding response and outcome data and response processing, including available response processingtemplates. V 0.65: Public Draft 20130912 1

IntroductionPARCC Item Development Technical GuideMetadata – Metadata guidelines for all metadata elements (including description, vocabulary, XMLencoding) and use of metadata elements to describe items, assets, test, sections, packages, files andaccessibility; encoding of metadata in XML documents. Exchange – Packaging guidelines for item banks, tests, sections and variant resources; XML elements formanifests, sections and test; PARCC naming and versioning conventions. Validation – APIP and PARCC validation guidelines (item accessibility, client accessibility, embeddedsupports, content packaging, metadata); editorial and style validation; rendering validation; behaviorvalidation, response processing validation, accessibility validation. Glossary – Definitions of terms used, both technical and non technical.Acronyms – List of acronyms used.References – References to other documents, both technical and non technical.Schemata – Links to XML XSD schemata; RTTA profile schemata, APIP profile schemata and coreschemata.Annex: RTTA APIP Profile – An overview of the RTTA and PARCC APIP profiles including profilevocabulary listings. The complete RTTA and PARCC APIP profiles will be included in a subsequentversion of this Guide.Annex: Response Processing Templates – The listing of the XML of the available response processingtemplates, including standard QTI templates and custom PARCC templates.Annex: PARCC APIP Content Packaging Examples – Complete listings of exemplar PARCC APIPcontent packages, including: test, section and item exchange and associated metadata; response processingtemplate packaging.The order of presentation follows the nominal item development workflow .Each of the major guideline topics is numbered (e.g., ); these numbers are used both within the workflow and ascross-references within this Guide.Within the document, words in italics are typically described in the glossary.XML element names, attribute names and data values are presented in a san-serif font.When not indicated, a implies a features is required (and unless otherwise noted, only a single instance ispermitted), a implies a feature is optional and a implies a feature should not be used.Note: Unless indicated, XML examples have not been validated.2 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Development Workflow Item Development Workflow The process of developing, delivering and using an item goes through a sequence of steps performed either by theitem developer, PARCC or a third party. One or more of the item development guidelines described in this Guideare applicable to the steps in the item development process.A nominal workflow process is shown in Figure 0.1 and described below. Each step in the workflow is associatedwith one or more of the guidelines, indicated by the number of the corresponding guideline section. The specificsteps and governing guidelines are dependent on the actual tools (e.g., item bank, test client), scope of itemdevelopment and specific business and policy agreements between the participating parties.A. Item Development: Given the criteria for an item, the item is designed and authored. Item design is based onnon-technical criteria, e.g., evidence-based assessments design principles; model content frameworks; itemgeneration models. The authored item and all media assets must conform to the: Style guides (including editorial style, art/media requirements and layout) Accessibility guidelines Device guidelines and constraintsAn item developer will typically uses a developer-specific template or other job aid to document and describe theitem under development, e.g., item ID, status, CCSS standards-alignment, associated evidence statements, art/mediaassets (files, file names), layout. This information will be used to create the metadata descriptions of the item andassociated assets.B. Item Approval: Once the item has been created and subjected to the developer’s internal QA/QC andvalidation , the item (or multiple items) is transmitted to PARCC for approval. At this stage, PARCC does notrequire a specific approach to transmit the item for approval. PARCC prefers that the item be encoded andexchanged as a PARCC APIP Content Package that includes: The item encoded in QTI with associated media assets suitable for rendering (source media assets notrequired) The descriptive item template An image showing item renderingFull metadata is not required for initial approval.PARCC will either approve the item, or indicated required changes. The item developer and PARCC will iterateuntil the item is accepted. This Guide does not currently detail: The transmittal method of the item, e.g., email, file transfer via FTP, deposit into the PARCC item bank. Approval policies, communications and procedures between the item developer and PARCC.C. Item Transmittal: Once the item has been approved, the final version of the item will be transmitted toPARCC. Note, any subsequent change to the item results in a new version of the item being created. The item mustbe transmitted to PARCC as part of a PARCC APIP Content Package that includes: The item encoded in QTI with all associated media assets (media assets and layout for both online andpaper rendering and all associated source media) The descriptive item template An image showing item rendering Item-level metadata Asset/Resource metadata for each media asset or file Package-level metadata Section- and Test-level metadata when transmitting a section or testThis Guide does not currently detail: The transmittal method of the item, e.g., email, file transfer via FTP, deposit into the PARCC item bank.V 0.65: Public Draft 20130912 3

Item Development WorkflowPARCC Item Development Technical GuideSpecification of the scope and structure of a content package, e.g., one package per topic for each gradelevel versus multiple topic items for a single grade level within one package.Conformance Item Development PARCC Delivery8Validation1Style2AccessibilityItem DevelopmentAItem Development3QA/QCClient5Encoding7 PackagingTransmitExchangeBItem ApprovalRejectApprove5Encoding6MetadataPackagingTransmitCItem Transmission7ExchangeConformanceDItem Validationand Storage8RejectApproveValidation5Encoding3ClientETest DeliveryItem Bank6Metadata7ExchangePackagingTest ClientPaper FormsFigure 0.1: Item Development Workflow4 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Development Workflow D. Item Validation and Storage: PARCC may perform an independent (or use a 3 rd party) validation of the item.If the item fails to validate and comply with the guidelines described herein, PARCC will reject the item and requiremodifications. Accepted, validated items will be stored in the PARCC item bank for use. This Guide does notcurrently detail: Communications and approval mechanisms between the item developer and PARCC w.r.t. validationfailures. Processes for addressing validation failures.E. Test DeliveryOnline Test Delivery: For delivery to the test client , the blueprint will be used to extract items from the itembank to create a PARCC APIP Content Package containing the test form that includes: All items encoded in QTI with associated media assets required for rendering Item-level metadata Asset/Resource metadata Section- and Test-level metadata Package-level metadata This Guide does not detail online test delivery and administration.Paper Test Delivery: For paper delivery, the blueprint will be used to extract items from the item bank to createpaper forms. This Guide does not detail paper-based test creation, delivery and administration.V 0.65: Public Draft 20130912 5

StylePARCC Item Development Technical GuideStyle The Style guidelines detail: Editorial and language requirements for items Graphic and art requirements for item media assets Page and screen layout requirements, including navigation elements, fonts and sizes, color palettes foritems Media guidelines for item audio and video media assets Accessible content guidelinesThe Style guidelines are applicable to items used in both computer-based and paper-based tests.The Style guidelines are aligned with the Accessibility guidelines .All items and associated media assets must conform to all of the Style guidelines.Editorial and Language GuidelinesThe editorial and language guidelines specify style for English narrative text in items.The guidelines address: Grammar and usage Punctuation Abbreviations Spelling and distinctive treatment of words NumbersUnless otherwise specified, the default style follows the Chicago Manual of Style, 16 th Edition [Chicago].Unless otherwise specified, the default dictionaries are either: Webster's Third New International Dictionary [Webster’s International]. Merriam-Webster’s Collegiate Dictionary, 11 th Edition [Webster’s Collegiate].Specific guidelines follow.Content: See PARCC Style Guide, Version 1.1, Language Requirements Section, pp. 107—127 for specificguidelines [PARCC Style Guide].Online Art GuidelinesThe online art guidelines specify details of discrete graphic and artistic elements, i.e., item media assets, used withinan item that is created for online delivery.Graphic elements include: Graphs Tables Charts Photographs Maps Clocks6 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideStyle PlotsNumber LinesAn example of a set of art guidelines is shown in Figure 1.1.Figure 1.1: Sample Art GuidelinesThe guidelines address parts of elements including: Labels Keys Scale Grids Borders Titles Captions Data values Lines Legends Patterns ShapesThe guidelines specify requirements for graphics and art media assets used in items delivered online, including: Fonts Colors SizesV 0.65: Public Draft 20130912 7

StylePARCC Item Development Technical GuideSpacingEditorial styleAlignmentSpecific guidelines follow.Content: See PARCC Style Guide, Version 1.1, Online Art Requirements Section, pp. 15—85 for specificguidelines [PARCC Style Guide].Online Layout GuidelinesThe online layout guidelines specify details of the layout of the elements that make up an item that is created foronline delivery.Layout guidelines address: Onscreen item layout Item answer options Mathematics and formulae Color palettes Text blocks (e.g., lists, footnotes, quotations)Specific guidelines follow.Content: See PARCC Style Guide, Version 1.1, Online Layout Requirements Section, pp. 86—106 for specificguidelines [PARCC Style Guide].Paper Art GuidelinesThe paper art guidelines specify details of discrete graphic and artistic elements, i.e., item media assets, used withinan item that is created for paper delivery. They differ from the online art guidelines as all art elements for paperdelivery are limited to grayscale.Graphic elements include: Graphs Tables Charts Photographs Maps Clocks Plots Number LinesThe guidelines address parts of elements including: Labels Keys Scale Grids Borders Titles Captions8 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideStyle Data valuesLinesLegendsPatternsShapesThe guidelines specify requirements for graphics and art media assets used in items delivered in paper forms,including: Fonts Colors Sizes Spacing Editorial style AlignmentSpecific guidelines follow.Content: See PARCC Style Guide, Version 1.1, Paper Art Requirements Section, pp., 128—178 for specificguidelines [PARCC Style Guide].Paper Layout GuidelinesThe paper layout guidelines specify details of the layout of the elements that make up an item that is created forpaper delivery.Layout guidelines address: Paper item layout Item answer options Mathematics and formulae Text blocks (e.g., lists, footnotes, quotations)Specific guidelines follow.Content: See PARCC Style Guide, Version 1.1, Paper Layout Requirements Section, pp. 179—215 for specificguidelines [PARCC Style Guide].Audio and Video Media GuidelinesThe audio and video media guidelines specify details of audio and video media assets used within an item.Future Guide Version: Add audio and video media guidelines.Accessible Content GuidelinesThe accessible content guidelines specify details accessible content used for an item.The accessible content guidelines address: Text for text-to-speech content Braille contentV 0.65: Public Draft 20130912 9

StylePARCC Item Development Technical GuideTactile contentSigned contentAssociated audio and video media guidelinesFuture Guide Version: Add specific accessible content guidelines.10 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Accessibility PARCC is committed to providing all students with equitable access to high-quality next generation assessments.While external accommodations may be needed for some students to demonstrate what they know and can do,embedded support for accessibility options and procedures need to be addressed during item development tominimize the need for accommodations during testing. Embedded accessibility supports at the item level, that donot shift the construct being measured, become a feature of the assessment for potential use by all children.Accessibility support also addresses regulatory guidelines and industry best practices, e.g., web accessibilityguidelines [WCAG 2.0].Item-level accessibility embedded supports are specified using the Accessible Portable Item Protocol (APIP)standard [APIP]. The PARCC Assessment Delivery Platform is APIP compliant (PARCC APIP Profile). It canread an APIP Personal Needs and Preferences (PNP) profile for a student and the test client can present thespecified accessibility information contained in an item based on the student’s PNP. Accessibility features forindividual items, encoded within the item, are described in the Accessibility guidelines. Accessibility features andsupport tools for test clients are described as part of the test client guidelines . The relationship of these elementsis shown in Figure 2.1.APIP TestPackageStudentPNPTest ClientToolboxStudentThe Accessibility guidelines detail: PARCC APIP requirements Embedded Supports and Other AccommodationsFigure 2.1: Accessibility ElementsThe Accessibility guidelines do not address: Creating or exchanging a student PNP Using the PNP to control accessibility features in the test client Other behaviors of the test clientAll items and associated media data must conform to all of the Accessibility guidelines. Unless otherwise noted, allXML documents must use the RTTA APIP Profile Schemata specified in the Schemata section.V 0.65: Public Draft 20130912 11

AccessibilityPARCC Item Development Technical GuidePARCC APIP RequirementsAll items and associated assets and resources must adhere to the required components of the APIP Item Standard[APIP QTI 1.0], including the provision of accessibility information for the embedded supports listed in Table 2.1.All items must be encoded using APIP QTI [APIP QTI 1.0] and exchanged using APIP Content Packaging[APIP Tech 1.0].The item developer can assume that the test client supports the accessibility features indicated with a or inTable 2.1 (feature list derived from [APIP Conformance 1.0: § 3] with PARCC additions; alphanumeric codes in thefirst column align with APIP labels for accessibility features) and must develop items to support all of the listedaccessibility features. As indicated in the table, specific accessibility features must be specified as part of the itemencoding (). Other accessibility features are part of the test client () and do not need to be encoded in the itemQTI, but may require additional assets encoded as variant resources in the content package . In addition, the testclient allows students to interact with the test client using an adapted mouse, keyboard (standard and alternate),touch screen, or a tab-enter enabled device.Table 2.1: PARCC APIP SupportAccessibility FeatureSpecified inItemSpecified inPNPTest ClientSupportA1 Spoken: Text Only A2 Spoken: Text & Graphics A3 Spoken: Non-Visual A4 Spoken: Graphics OnlyA5 Spoken: Directions Only A6 Spoken: User Preferences A7 Spoken: Screen Reader Preferences A8 Braille (refreshable Braille display for English Language Arts – Literacy only in grades 3-11)Braille: ContractedBraille: UncontractedBraille: RefreshableA9 Braille: User PreferencesA10 Tactile Tactile: Spoken FileTactile: Spoken TextTactile: Braille TextA11 Signing: ASL A12 Signing: Signed English A13 Item TranslationA14 Keyword Translation A15 Simplified LanguageB1 Magnification B2 Magnification: User PreferencesIncreased White SpacingB3 Reverse Contrast B4 Alternative Text & Background Colors B5 Alternative Colors: User PreferencesInvert ColorB6 Color Overlay B7 Color Overlay: Color Preferences C1 Answer Masking 12 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Accessibility FeatureSpecified inItemSpecified inPNPTest ClientSupportC2 General Masking C3 Auditory CalmingC4 Additional Testing Time C5 BreaksC6 Keyword Emphasis C7 Line Reader C8 Line Reader: Color PreferencesC9 Language Learner GuidanceC10 Cognitive GuidanceSpeech to TextClosed CaptionsReduced AnswersNegatives RemovedChunkingScaffoldingHazardPARCC APIP Embedded Supports, Accessibility Features and AccommodationsItems may include any of the embedded supports (ES), accessibility features (AF) and accommodations (A) listed inTable 2.2.An embedded support is a tool, support, scaffold, or preference that is built into the assessment system that can beactivated by any student at his or her own discretion. Embedded supports are Universal Design features that areexpected to benefit a diversity of students and are available to all students, either onscreen, stored in the studenttoolbox or accessible through a menu or control panel, as needed. Examples of embedded supports are provided inTable 2.2.Like embedded supports, accessibility features are available to all students (i.e., not limited to students withIndividualized Education Program (IEP), 504 plans, or English Learner (EL) plans), but will be selected and “turnedon” by a school-based educator prior to the assessment, based on each student’s Personal Needs and Preferences(PNP) Profile. Accessibility features will be readily available on the computer-delivered testing platform. Anaccommodation is provided to a student as specified in an IEP, 504 plan or EL plan.Table 2.2 indicates if the support should be available to all students or if it is considered a PNP feature that isselected for the individual student ( indicated the feature is available, a blank table cell indicated the feature is notavailable). Accommodations may be built into the test client or may be provided by third-party devices andsoftware that offer accessibility features and accommodations to the student.Table 2.2: PARCC Embedded Supports, Accessibility Features and AccommodationsEmbedded Support, Accessibility Feature orAccommodationText-to-speech and the use of audio files (Spoken, TextOnly; Spoken; Spoken, Text & Graphics; Spoken, Non-Visual)Text to speech for directions only; Spoken, DirectionsOnlyType:ES, AF, AAll StudentsSelected NotesPNPFeature Note 1Screen readers Spoken, Non-Visual Note 2V 0.65: Public Draft 20130912 13

AccessibilityPARCC Item Development Technical GuideEmbedded Support, Accessibility Feature orAccommodationSpeech-to-text softwareType:ES, AF, AAll StudentsSelectedPNPFeatureNotesMagnification/Enlargement Device (Magnification ) Note 3Choice of background/text color background or text Note 4(Reverse Contrast; Alternative Text & BackgroundColors; Alternative Colors, User Preferences; ColorOverlay; Color Preferences)Highlight critical features Note 5Passage/item/response choice ?? ??Graphic organizersCustomized dictionary or other home languagesupports/tools (keyword translation)Embedded/pop-up glossary Details tobe providedMasking (Masking) General Masking (General Masking)Video of a Human Interpreter (Signing: ASL) Captions for Audio (as part of multimedia test items) Note 6Assistive Technology Note 7Extended time (Additional Testing Time)Braille printing and refreshable Braille devices (Braille;Braille user preferences)Answer Eliminator (N/ALine Reader (Line Reader; color preferences for linereader)Mark Items for ReviewSpeller CheckerWriting ToolsNote Pad (N/A)Word PredictionSpeech to TextNote 1: Text-to-Speech The interface must support text-to-speech software that includes the ability to highlight portions or all textand graphics of the screen to be read aloud.Note 2: Screen Reader A screen reader is a software application that attempts to identify and interpret what is being displayed onthe screen. This interpretation is then re-presented to the user with text-to-speech, sound icons, or a Brailleoutput device. Screen readers are a form of assistive technology (AT) potentially useful to people who areblind or visually impaired).Note 3: Magnification Visuals should be represented as vector graphics, e.g., using structured vector graphics (SVG) [SVG] toallow for high-quality resizing instead of image formats (e.g., PNG [PNG], JPEG [JPEG], GIF [GIF89]). When visuals cannot be represented as scalable vector graphics (SVG) (e.g., photographs, politicalcartoons), a resolution should be chosen such that the quality of the visual is not significantly degraded at400% magnification. This should be confirmed by evaluating the quality of all images at this magnification14 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility level. If pixilation or jaggies degrade the image, then a higher image resolution image should bedeveloped. In most cases, a resolution of twice the normal resolution should be adequate.Lossy compression (e.g., JPEG) must not degrade visual quality significantly.In cases where providing a higher resolution version of a visual is necessary and significantly increases filesize, images may be provided at multiple resolutions.Provide multiple images:o One image at normal screen resolutiono One at a higher resolution suitable for both higher screen resolutiono One for printing (unless the higher screen resolution image is suitable for printing)If possible and reasonable, bitmapped text within a visual should be replaced by text using outline fonts. Inall cases, text within visuals must be represented as alt text.Note 4: Text and Background Colors There must be effective color contrast. Shades of gray should not be used together either as graphic features or text. Color palettes are detailed in the Style guidelines .Note 5: Highlighting Color options must be available to users. Color palettes are detailed in the Style guidelines .Note 6: Audio Captions Test Clients support for closed captions include:o Synchronized Multimedia Integration Language (SMIL) [SMIL] for video, e.g., QuickTime(.mov) [MP4] and MPEG (.mpg) [MPEG]o Synchronized Accessible Media Interchange (SAMI) [SAMI] for audio, e.g., AVI (.avi) [AVI] orWave (.wav) [Wave]Note 7: Alternate Response Available alternate Response Options include: adapted keyboards, large keyboards, StickyKeys,MouseKeys, FilterKeys, adapted mouse, touch screen, head wand or other switches. Some alternate response options are considered assistive technology software or external devices.PARCC APIP Accessibility Item Companion MaterialsTable 2.3 lists the types of companion material. The APIP companionMaterialsInfo element [APIP QTI 1.0: § 3.2]is used to describe the set of companion materials should be made available to the student along with the item. Onlythe items indicated () are available in the PARCC test client.If any of the other companion materials are included with the item, the test client need not provide the material tothe student. Any companion material and tools not explicitly assigned to the item will never be presented to thestudent.PARCC items must always use the available tools built into the test client for all companion materials. Item-specificor alternative implementations of any tool are not permitted; new tools or changes in tool functionality must beapproved by PARCC and added to the list of companion materials. Additionally, digital companions / digitalmaterials cannot be used as a replacement for any available tool.V 0.65: Public Draft 20130912 15

AccessibilityPARCC Item Development Technical GuideTable 2.3: PARCC Accessibility Item Companion MaterialsItem Companion MaterialsCalculatorRulerProtractorCompassStraight EdgeReading PassageDigital Companion / Digital MaterialPhysical Companion / Physical MaterialNote PaperGraph PaperWord Processing Functions / Word Processing ToolGraphic OrganizerNote PadDictionaryGlossaryThesaurusEquation EditorText AnnotationSpell CheckerWord PredictionVisual DictionaryPopup GlossaryDrawing ToolFormula ChartPARCC RequirementA summary of each of the available companion materials follows, including a part of an example XML encoding ofthe specification of the material. For each companion material: Definition: A narrative description of the companion material. Name: Element name for the companion material. Multiplicity: Is only one instance of the companion material available permitted or are multiple instanceswith different data available. Test Client: indicates if the companion material is currently supported by the PARCC Test Client.Unsupported companion materials () should not be specified; the material request will be ignored.Specification of banned materials () may result in an error. Elements: The list of elements for the companion material (any element not listed is permitted unlessformally excluded elsewhere). Within the companion material description, the elements must appear in theorder listed. For each element:o if the element is optional or if the element is required.o Name of the element.o Type of the element.o Acceptable element values.o Default element value if the element is not present.o Notes about the element. Usage Notes: Usage notes and guidance for describing the companion material. Example XML: An illustrative example of the XML for an item using the companion material. XML Validation: Validated (), partially validated—no known issues (), invalid or not validated ().Includes details on XML, Schema, Rendering, Behavior, Response Processing and Accessibility validation. Example Description: A description of the example.16 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material CalculatorDefinition A calculator. Four PARCC types are available: four function, scientific, graphing, full function.NamecalculatorMultiplicity [0..1]Test Client ElementsElement Type Value Default Notes(ordered) calculatorType vocabulary Type none PARCC Extended VocabularyBasicFour Function onlyStandardPARCC Four Function with ScientificGraphingFullFunctionPARCC Full Function description string any none calculatorInfo href any noneUsage Notes Location (calculatorInfo) should not be provided; PARCC calculator options are part of thePARCC test client.ExampleXMLExampleDescription0001020304050607080910 ... ...Standard4 function calculator with square root ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: The example shows the declaration of a PARCC four function calculator as a companion material.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the calculatoro Line 05: Calculator typeo Line 06: Calculator descriptionV 0.65: Public Draft 20130912 17

AccessibilityPARCC Item Development Technical GuideMaterial RulerDefinition A ruler. SI or US units.NameruleMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any none ruleSystemSI element SI and US are exclusive ruleSystemUS element SI and US are exclusive minimumLength integer positive none minorIncrement element Pair of values value float non negative none unit vocabulary Unit none APIP Standard VocabulariesmillimeterFor SI onlycentimeterFor SI onlymeterFor SI onlykilometerFor SI onlyinchFor US onlyfootFor US onlyyardFor US onlymileFor US only majorIncrement element Pair of values value float non negative none unit vocabulary Unit none APIP Standard VocabulariesmillimeterFor SI onlycentimeterFor SI onlymeterFor SI onlykilometerFor SI onlyinchFor US onlyfootFor US onlyyardFor US onlymileFor US onlyUsage Notes Use appropriate attribute values to specify the 1/8 th inch and 1/4 th inch rulers.ExampleXML000102030405060708091011121314 ... ...Six inch ruler, 1/8th inch increments6 0.1251.0 ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 18 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility MaterialExampleDescriptionRulerThe example shows the declaration of a 1/8 th inch ruler as a companion material.In the example: Lines 00-03, 12-14: Accessibility element wrappers for the companion material info Lines 04-11: Declaration of the rulero Line 05: Ruler descriptiono Line 06: Ruler is US unitso Line 07: Lengtho Line 08: Minor marks at 1/8 th incho Line 09: Major marks at 1 inchV 0.65: Public Draft 20130912 19

AccessibilityPARCC Item Development Technical GuideMaterial ProtractorDefinition A protractor. Degrees, minutes, seconds or radians.NameprotractorMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any none incrementSI element SI and US are exclusive incrementUS element SI and US are exclusive minorIncrement element Pair of values value float non negative none unit vocabulary Unit none APIP Standard VocabulariesradianFor SI onlydegreeFor US onlyminuteFor US onlysecondFor US only majorIncrement element Pair of values value float non negative none unit vocabulary Unit none APIP Standard VocabulariesradianFor SI onlydegreeFor US onlyminuteFor US onlysecondFor US onlyUsage NotesExample 00XML 01020304050607080910111213ExampleDescription ... ...Protractor, 1/10th and 1 radian marks1.00.10 ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: The example shows the declaration of protractor with major marks at each radian and minormarks at each 1/10 th radian as a companion material.In the example: Lines 00-03, 11-13: Accessibility element wrappers for the companion material info Lines 04-10: Declaration of the protractoro Line 05: Protractor descriptiono Line 06: Protractor is in radianso Line 07: Minor marks at 1/10 th radiano Line 08: Major marks at 1 radian20 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material CompassDefinition A compass.NamecompassMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the compasso Line 05: Compass descriptiono Line 06: …V 0.65: Public Draft 20130912 21

AccessibilityPARCC Item Development Technical GuideMaterial Straight EdgeDefinition A straight edge.NamestraighEdgeMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the straight edgeo Line 05: Straight edge descriptiono Line 06: …22 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Reading PassageDefinition A reading passage.NamereadingPassageMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any none PARCC addition fileHref href any none [0..*]Usage Notes The companion reading materials are included in the manifest as separate resources. The fileHrefpoints to the resource.PARCC materials should be placed in the companionmaterials folder for the item.ExampleXMLExampleDescription000102030405060708091011 ... ...Two reading passages are availablecompanionmaterials/companionfile001.extcompanionmaterials/companionfile002.ext ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: The example shows two files as companion reading materials.In the example: Lines 00-03, 09-11: Accessibility element wrappers for the companion material info Lines 04-08: Declaration of the reading passageo Line 05: Reading passage descriptiono Lines 06-07: File references to the digital materialsV 0.65: Public Draft 20130912 23

AccessibilityPARCC Item Development Technical GuideMaterial Digital Companion / Digital MaterialDefinition Generic companion materials in a digital file.NamedigitalMaterialMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any none PARCC addition fileHref href any none [0..*]Usage Notes The companion digital materials are included in the manifest as separate resources. The fileHrefpoints to the resource.PARCC materials should be placed in the companionmaterials folder for the item.Digital companion materials may not be used as a replacement or substitute for any available testclient supported toolDigital ompanion materials may not be used to add tool or type of companion material notavailable in the test client. Any new tool must be PARCC approved and added as a new entry tothe list of companion materials.ExampleXMLExampleDescription000102030405060708091011 ... ...Two files are availablecompanionmaterials/companionfile001.extcompanionmaterials/companionfile002.ext ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: The example shows two files as companion digital materials.In the example: Lines 00-03, 09-11: Accessibility element wrappers for the companion material info Lines 04-08: Declaration of the digital materialo Line 05: Digital material descriptiono Lines 06-07: File references to the digital materials24 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Physical Companion / Physical MaterialDefinition Generic companion physical material.NamephysicalMaterialMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered)NoneUsage Notes The description of the material is included with the main element. There are no additionalattributes.ExampleXMLExampleDescription00010203040506070809 ... ...Supply a pencil, 12" ruler and a piece of plain 8 ½ x 11" white paper ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: The example describes the physical materials to be provided to the student.In the example: Lines 00-03, 07-09: Accessibility element wrappers for the companion material info Lines 04-06: Declaration of the physical materialo Line 05: The description of the physical materials to be provide to the studentV 0.65: Public Draft 20130912 25

AccessibilityPARCC Item Development Technical GuideMaterial Note PaperDefinition Note Paper.NamenotePaperMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the note papero Line 05: Note paper descriptiono Line 06: …26 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Graph PaperDefinition Graph Paper.NamegraphPaperMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the graph papero Line 05: Graph paper descriptiono Line 06: …V 0.65: Public Draft 20130912 27

AccessibilityPARCC Item Development Technical GuideMaterial Word Processing ToolDefinition Word Processing Tool. Features include: text selection; cut/copy/paste; font size, style, color,format (bold, italics, underline); inserting lists, images, symbols and special characters;undo/redo.NamewordProcessingToolMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the word processing toolo Line 05: Word processing tool descriptiono Line 06: …28 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Graphic OrganizerDefinition A graphic organizer. Types include: Venn diagram, t-chart, story map, concept map, flow map.NamegraphicOrganizerMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any none organizerType vocabulary Type noneVennDiagramTChartStoryMapConceptMapFlowMap organizerInfo href any noneAdditional attributes TBDUsage Notes Location (organizerInfo) should not be provided; PARCC graphic organizer options are part ofthe PARCC test client.ExampleXMLExampleDescription000102030405060708091011 ... ...Concept MapConceptMap... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed. The example shows the declaration of a concept map as a companionmaterial.In the example: Lines 00-03, 09-11: Accessibility element wrappers for the companion material info Lines 04-08: Declaration of the graphic organizero Line 05: Graphic organizer descriptiono Line 06: Graphic organizer typeo Line 07: …V 0.65: Public Draft 20130912 29

AccessibilityPARCC Item Development Technical GuideMaterial Note PadDefinition A note pad.NamenotePadMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the note pado Line 05: Note pad descriptiono Line 06: …30 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material DictionaryDefinition A dictionary.NamedictionaryMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx… …Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the dictionaryo Line 05: Dictionary descriptiono Line 06: …V 0.65: Public Draft 20130912 31

AccessibilityPARCC Item Development Technical GuideMaterial GlossaryDefinition A glossary.NameglossaryMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the glossaryo Line 05: Glossary descriptiono Line 06: …32 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material ThesaurusDefinition A thesaurus.NamethesaurusMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the thesauruso Line 05: Thesaurus descriptiono Line 06: …V 0.65: Public Draft 20130912 33

AccessibilityPARCC Item Development Technical GuideMaterial Equation EditorDefinition An equation editor.NameequationEditorMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the equation editoro Line 05: Equation editor descriptiono Line 06: …34 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Text AnnotationDefinition A text annotation tool.NametextAnnotationMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage Notes Text annotation should only be provided for ELA-L items.ExampleXMLExampleDescription0001020304050607080910 ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the text annotation toolo Line 05: Text annotation descriptiono Line 06: …V 0.65: Public Draft 20130912 35

AccessibilityPARCC Item Development Technical GuideMaterial Spell CheckerDefinition A spell checker.NamespellCheckerMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the spell checkero Line 05: Spell checker descriptiono Line 06: …36 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Word PredictionDefinition A word prediction tool.NamewordPredictionMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the word prediction toolo Line 05: Word prediction descriptiono Line 06: …V 0.65: Public Draft 20130912 37

AccessibilityPARCC Item Development Technical GuideMaterial Visual DictionaryDefinition A visual dictionary.NamevisualDictionaryMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the visual dictionaryo Line 05: Visual dictionary descriptiono Line 06: …38 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Popup GlossaryDefinition A popup glossary.NamepopupGlossaryMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the popup glossaryo Line 05: Popup glossary descriptiono Line 06: …V 0.65: Public Draft 20130912 39

AccessibilityPARCC Item Development Technical GuideMaterial Drawing ToolDefinition A drawing tool.NamedrawingToolMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the drawing toolo Line 05: Drawing tool descriptiono Line 06: …40 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Material Formula ChartDefinition A formula chart.NameFormula ChartMultiplicity [0..*]Test Client ElementsElement Type Value Default Notes(ordered) description string any noneAdditional attributes TBDUsage NotesExample 00XML 01020304050607080910ExampleDescription ... ...xxx... ...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: Example to be completed.In the example: Lines 00-03, 08-10: Accessibility element wrappers for the companion material info Lines 04-07: Declaration of the formula charto Line 05: Formula chart descriptiono Line 06: …To Do: Complete details of each companion material: attributes, example.V 0.65: Public Draft 20130912 41

AccessibilityPARCC Item Development Technical GuidePARCC APIP Accessibility Item Accessibility Info and Access ElementsItem developers may use any of the APIP info elements [APIP QTI 1.0: §3.6] (accessibilityInfo, accessElement) without any restrictions to provideaccessible content alternatives (access elements) for item content. Thereare no PARCC-specific profile constraints or extensions for XMLaccessibility features (elements, attributes) for accessibility info andaccessibility content.Any of the accessible content elements and their corresponding attributesmay be used to describe the accessible content features(relatedElementInfo values are listed in Table 2.4). The PARCCAccessibility Guidelines [PARCC Accessibility Guide] specify details ofthe accessible content features.The order of the accessible content (accessElement) should follow the orderof the corresponding parts of the item. There is no preferred ordering of theactual content features (relatedElementInfo), but the same order should bemaintained across all items.Each accessElement requires an identifier, which is referenced by theidentifierRef attribute of the elementOrder in the inclusion order. Thereare no PARCC constraints on the form of the identifier.The accessible content also requires a contentLinkIdentifier. There are noPARCC constraints on the form of the contentLinkIdentifier.itemBodyAssessmentItemapip:apipAccessibilityapip:companionMaterialsInfoapip:inclusionOrderapip:accessibiltyInfo...

PARCC Item Development Technical GuideAccessibility Related ElementchunkanswerReductionkeyWordEmphasisPARCC RequirementCode Listing 2.1 illustrates a sample of accessibility info showing a single accessibility element with twoaccessibility features (spoken and Braille). The details of the accessibility feature content are omitted.Code Listing 2.1: Accessibility Info Example01020304050607080910111213141516….......Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 02-16: The access element identifier as accessElementID01 for cross referencing to the inclusionordero Lines 03-05: The link from the access element to the QTI item content itemID01o Lines 06-14: The access feature content• Lines 07-10: Spoken content feature (two content elements omitted)• Lines 11-13: Braille content feature (content omitted)PARCC APIP Accessibility Item Inclusion OrderItem developers may use any of the APIP inclusion order information elements [APIP QTI 1.0: § 3.5](inclusionOrder) listed in Table 2.5 without any restrictions to control accessible content availability. There are noPARCC-specific profile constraints or extensions for XML accessibility features (elements, attributes) for inclusionorder.Table 2.5: PARCC Accessibility Inclusion Order ElementsInclusion Order ElementbrailleDefaultOrdertextOnlyDefaultOrdertextOnlyOnDemandOrdertextGraphicsDefaultOrdertextGraphicsOnDemandOrdergraphicsOnlyOnDemandOrderPARCC RequirementV 0.65: Public Draft 20130912 43

AccessibilityPARCC Item Development Technical GuideInclusion Order ElementnonVisualDefaultOrderaslDefaultOrderaslOnDemandOrdersignedEnglishDefaultOrdersignedEnglishOnDemandOrderPARCC RequirementWithin the inclusion order information, there is no preferred ordering of the different inclusion order lists; the listsmay appear in any order. The PARCC Accessibility Guidelines [PARCC Accessibility Guide] determine which listsneed be present. If there is no accessibility content for a particular type for an item, the entire list should be omitted;empty order lists without elementOrder elements are not permitted.Within an individual list, the elementOrder elements should appear in the XML document in order based on thevalue of the corresponding order subelement, but the value of order determines the actual presentation order (thecorresponding content elements are presented in the numerical ascending order based on order). The values oforder should be contiguous, but gaps are inconsequential.The cross references linking to the ordered content element need to reference an accessible content element withinthe same XML document, i.e., the value of identifierRef should match the value of identifier for an accessElement.The linking of inclusion order and accessibility elements is shown in Figure 2.2.Code Listing 2.2 illustrates a sample of inclusion order with two order lists.Code Listing 2.2: Inclusion Order Example0102030405060708091011121314151617181920212223< apip:nonVisualDefaultOrder>123123Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 02-12: The ordered content elements for default non visual ordero Lines 03-05: The first non visual content element identified as accessElementID01o Lines 06-08: The second non visual content element identified as accessElementID0244 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility o Lines 09-11: The third non visual content element identified as accessElementID03Lines 13-22: The ordered content elements for the default Braille ordero Lines 14-16: The first Braille content element identified as accessElementID01o Lines 17-19: The second Braille content element identified as accessElementID02o Lines 20-22: The third Braille content element identified as accessElementID03PARCC APIP Accessibility MetadataIn addition to accessibility information used when the item is presented to the student, all PARCC items require a setof accessibility metadata. These attributes are used to discover items with particular accessibility characteristicsfrom the PARCC item bank and are included with the other metadata elements used to describe an item. Theindividual accessibility metadata elements for an item (included/exclude accessibility display features,included/excluded accessibility support features and companion materials) are fully described with the othermetadata .PARCC APIP Accessibility ElementsAn assessement item contains the APIPAccessibility element. Elements used with PARCC APIP accessibilityinclude: APIPAccessibility [APIP QTI 1.0: § 3.1] companionMaterialsInfo [APIP QTI 1.0: § 3.2] inclusionOrder [APIP QTI 1.0: § 3.5] accessibilityInfo [APIP QTI 1.0: § 3.6] Accessibility order elements: Table 2.5 (individual elements are not currently detailed, see [APIP QTI 1.0:§ 3.5]) accessElement [APIP QTI 1.0: § 3.6.2] contentLinkInfo [APIP QTI 1.0: § 3.6.3] elementOrder [APIP QTI 1.0: § 3.5.14] Related elements: Table 2.4 (individual elements are not currently detailed, [APIP QTI 1.0: § 3.6.6]) relatedElementInfo [APIP QTI 1.0: § 3.6.4] textLink [APIP QTI 1.0: § 3.6.4]A summary of each of the elements follows. For each element: Definition: A narrative description of the element. Type: The type of the element (APIP, PARCC APIP Profile, RTTA APIP Profile). Components: The components that use the element. Attributes: The list of element attributes (any attribute not listed is permitted unless formally excludedelsewhere, e.g., template attributes). For each attribute:o if the attribute is optional or if the attribute is required.o Name of the attribute.o Type of the attribute.o Acceptable attribute values.o Default attribute value if the attribute is not present.o Notes about the attribute Elements: The list of subelements included in the element (any element not listed is permitted unlessformally excluded elsewhere). Within the element, the subelements must appear in the order listed. Theelements, their attributes and any contained subelements are detailed elsewhere in the list. For eachelement:o if the element is optional, if the element is required or if PARCC guidelines exclude useof the element.o Name of the element.V 0.65: Public Draft 20130912 45

AccessibilityPARCC Item Development Technical Guideo Number of times the element can occur. If empty, only one occurrence is permitted.o Ordering of the elements when there are multiple instances. If empty, the elements are notordered.o Notes about the subelement.Notes: Notes about the element.Element APIPAccessibilityDefinition The accessibility information for an item.Type APIP [APIP QTI 1.0: § 3.1]Components assessmentItemAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) companionMaterialsInfo inclusionOrder accessibilityInfoNotesElement companionMaterialsInfoDefinition The list and definitions of the available companion materials for an item.Type PARCC Profile (extensioned from [APIP QTI 1.0: § 3.2])Components APIPAccessibilityAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(unordered) Any of the companion materials listed in Table 2.3 may be used.NotesThe definitions of the elements used to describe the companion materials are shown above foreach individual companion material.Element inclusionOrderDefinition The ordering of the accessibility elements for an item.Type APIP [APIP QTI 1.0: § 3.5]Components APIPAccessibilityAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(unordered) Any of the accessibility inclusion order elements listed in Table 2.5 may be used.NotesThe definitions of the elements used to describe the inclusion order are not included. See [APIPQTI 1.0: § 3.5].All of the elements have the same subelement as described in the accessibility order elementdescription.46 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAccessibility Element accessibilityInfoDefinition The description of accessibility information for an itemType APIP [APIP QTI 1.0: § 3.6]Components APIPAccessibilityAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) accessElement [1..*]NotesElement Accessibility Order ElementsDefinition The ordering within any of the accessibility elements listed in Table 2.5.Type APIP [APIP QTI 1.0: § 3.5]Components inclusionOrderAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(unordered) elementOrder [1..*]NotesElement accessElementDefinition Description of a single accessibility element for an item.Type APIP [APIP QTI 1.0: § 3.6.2]Components accessibilityInfoAttributes Attribute Type Value Default Notes identifier identifier any noneElementsElement Number Order Notes(ordered) contentLinkInfo [1..*] relatedElementInfoNotesElement contentLinkInfoDefinition Description of a single accessibility element for an item.Type APIP [APIP QTI 1.0: § 3.6.3]Components accessElementAttributes Attribute Type Value Default Notes apipLinkIdentifierRef identifier any none qtiLinkIdentifierRef identifier any noneElementsElement Number Order Notes(ordered) textLink objectLinkxsd.anyTypeNotesV 0.65: Public Draft 20130912 47

AccessibilityPARCC Item Development Technical GuideElement elementOrderDefinition The list of accessibility element orders.Type APIP [APIP QTI 1.0: § 3.5.14]Components Any of the accessibility inclusion order elements listed in Table 2.5.Attributes Attribute Type Value Default Notes identifierRef identifier any noneNoneElementsElement Number Order Notes(unordered) orderElement value is an integerNotesElement Related ElementsDefinition The details of any of the related elements listed in Table 2.4.Type APIP [APIP QTI 1.0: § 3.6.6]Components relatedElementInfAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) Element specificNotesSee APIP [[APIP QTI 1.0: § 3.6.6] for the details of each element.Element relatedElementInfoDefinition Description of the related element for a single accessibility element for an item.Type APIP [APIP QTI 1.0: § 3.6.4]Components accessElementAttributes Attribute Type Value Default Notes identifier identifier any noneElementsElement Number Order Notes(unordered) Any of the related accessibility elements listed in Table 2.4 may be used.NotesThe definitions of the related accessibility elements are not included.See [APIP QTI 1.0: § 3.6.6].All of the elements have element-specific subelements.Element textLinkDefinition Identification of the object in the original content replaced by the accessibility content.Type APIP [APIP QTI 1.0: § 3.6.4]Components contentLinkInfoAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) fullStringxsd.anyTypewordLinkxsd.integercharacterLinkxsd.integercharacterStringLinkordered startCharacterxsd.integer stopCharacterxsd.integerNotes48 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideTest Clients Test Clients All items, assets and associated embedded supports, scaffolding and user interfaces must follow high standards forusability and accessibility design, meet Federal guidelines and regulations and follow Universal Design Principles[Universal Design]. Items are delivered through a test client that supports accessibility across the range of PARCCsupported devices and systems.The Test Client guidelines address: Characteristics of the test client devices (hardware, software, networking) Student toolbox featuresDevice DescriptionsThe test client used to render items must be compatible with a range of common devices (desktops, laptops,netbooks, tablets), operating systems (Windows, Mac, Linux, iOS, Chrome, Android), and browsers (includingInternet Explorer, Firefox, Chrome, Safari). The Technology Guidelines for PARCC Assessments [PARCC TechGuide] provides a full description of PARCC supported devices and systems. Item developers must design items toalign with the capabilities and limitations of the PARCC supported devices and systems. A summary of thecharacteristics include: Operating System Characteristics – Table 3.1 Hardware Characteristics – Table 3.2 Network Connectivity – Table 3.3 Software Characteristics – Table 3.4All items developed for the PARCC Field Test and First Operation Year must work on devices that meet only theminimum characteristics. Items developed for subsequent use may be developed to only use devices that meet therecommended characteristic.Table 3.1: Operating System CharacteristicsOperating System Minimum Version Recommended VersionDesktop, Laptop, Netbook, and Thin Client/VDI ComputersWindows Windows XP SP3 Windows 7 or laterApple Mac OS Mac OS 10.5 Mac OS 10.7 or laterLinux Ubuntu 9-10Fedora 6Ubuntu 11.10 or laterFedora 16 or laterChrome OS Chrome OS 19 Chrome OS 19 or laterTabletAndroid Android 4.0 Android 4.0 or laterApple iOS iPad 2 with iOS 6 iPad 2 or later with iOS 6 or laterWindows Windows 8 Windows 8 or laterTable 3.2: Hardware CharacteristicsHardware Characteristic Minimum Requirement RecommendedMemory 512KB RAM 1MB RAM or larger(512KB or larger for iPad2)Display Size 9.5 inch 9.5 inch or largerDisplay Resolution 768 x 1024 768 x 1024 or largerNetwork Connectivity Wired or Wireless Connectivity Wired or Wireless ConnectivityI/O Devices Keyboard KeyboardTouch Screen or MouseTouch Screen or MouseV 0.65: Public Draft 20130912 49

Test ClientsPARCC Item Development Technical GuideHardware Characteristic Minimum Requirement RecommendedHeadphone/EarphoneHeadphone/EarphoneMicrophoneMicrophoneTable 3.3: Network ConnectivityNetwork Bandwidth Minimum Bandwidth Recommended BandwidthExternal Internet Connectivity Forthcoming October 2013 100kbs per device or fasterIn-School LAN Forthcoming October 2013 1000kbs per device or fasterTo Do: Add specific software characteristics.Table 3.4: Software CharacteristicsSoftware Feature Minimum RecommendedStudent ToolboxTest client embedded supports and the student toolbox contain the features listed in Table 3.5 (alphanumeric codesin the first column align with APIP labels for accessibility features). A indicates that support for the feature isrequired in the student toolbox, a indicates that support the feature is optional and a blank table cell indicates thefeature is not applicable. As shown in the table, the PARCC student toolbox includes several tools or features thatare not part of the APIP [APIP QTI 1.0: § 3.2]. Item developers may specify any of the supported tools be availablewith the item; all of the required tools and features are available to the student.Table 3.5: Student Toolbox FeaturesStudent Toolbox Features APIP Feature PARCC RequirementD1 Calculator Four-function calculator with square root capabilitiesScientific calculatorGraphing calculatorFull function calculatorD2 Ruler (cm/in) Ruler: 1/8 th inchRuler: 1/4 th inchD3 Protractor CompassStraight EdgeD4 Reading Passage D5 Digital Companion / Digital Material D6 Physical Companion / Physical Material Note PaperGraph PaperWord Processing Functions / Word Processing ToolCut and PasteText SelectFont Style, Font Size, Font ColorUnderline, Bold, ItalicsInsert Bullets50 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideTest Clients Student Toolbox Features APIP Feature PARCC RequirementInsert ImagesUndo/RedoSuperscripts/SubscriptsInsert SymbolsSpell CheckGraphic OrganizerVenn DiagramT-ChartStory MapConcept MapFlow MapNote PadDictionaryGlossaryThesaurusEquation EditorText AnnotationSpell CheckerWord PredictionVisual DictionaryPopup GlossaryDrawing ToolFormula ChartV 0.65: Public Draft 20130912 51

Federal Regulatory Compliance Items and assessments must meet all applicable local and Federal regulations. Relevant Federal regulationsapplicable to all PARCC assessments, policies and processes include: Elementary and Secondary Education Act, 2001 (ESEA) [ESEA] Individuals with Disabilities Education Act, 2004 (IDEA) [IDEA] Rehabilitation Act of 1973, Section 504 [Section 504] Rehabilitation Act of 1973, Section 508 [Section 508] Family Education Rights and Privacy Act (FERPA) [FERPA] Children’s Online Privacy Protection Act (COPPA) [COPPA] Children’s Internet Protection Act (CIPA) [CIPA]For item development, the Style Guidelines and Accessibility Guidelines address IDEA and Section 508compliance. Other regulations, while applicable to assessment policies, are not directly applicable to itemdevelopment.52 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Item Encoding and Behavior To support item interoperability, PARCC uses APIP [APIP] to describe assessment items and define how to encodethem in XML. API and QTI further define the behavior of the item in the test client. Item descriptions, encoded inXML including accessibility information , are augmented with metadata and are exchanged using contentpackages .Given the design of an item, encoding is a multi-step process: Select Interaction Type: Each response type is implemented usingone of the available interaction types, specified by the CEDSAssessment Item Interaction Type element [CEDS 3.0] (anddocumented as the PARCC Interaction Type metadata element ).One of the available interaction types (listed in Table 5.2) is selectedfor the item. While there may be multiple applicable interactiontypes for a given response type, to maximize interoperability,PARCC recommends that the each response type is mapped to one ofthe five APIP/QTI “Core” interaction types [APIP 1.0 Conformance:§ 3.1] as shown in Table 5.2. XML Encoding: The interaction type choice defines part of thestructure of the QTI XML for encoding the item. XML encoding forAssessmentItemresponseDeclarationoutcomeDeclarationitemBodyresponseProcessingstylesheetsapip:apipAccessibilityeach interaction type is shown below. The full XML encoding forapip:companionMaterialsInfothe item includes (Item structure shown in Figure 5.1):o Encoding the Interaction type conforming to APIPincluding selecting item behavior options.apip:inclusionOrdero Encoding the text of the item, using XHTML [XHTML]apip:accessibiltyInfoand stylesheets [CSS]o Encoding the response processingo Adding APIP accessibility data Metadata Tagging: Once complete, the item and all associatedFigure 5.1: Item Structureresources are tagged with metadata . Exchange: The item and its media resources are packaged into a content package for exchange .Guidelines for encoding items in PARCC APIP/QTI XML include: Mapping PARCC items to APIP QTI Encoding items:o Encoding common interaction attributeso Encoding items that use the APIP Required QTI item interactionso Encoding items that use the APIP Optional QTI item interactionso Encoding items that use the PARCC item interactionso Encoding QTI elements within an item interactiono Encoding technology-enhanced items that require test-client specific QTI custom interactionso Encoding custom interactions using Portable Custom Interactions [PCI]o Encoding composite items Using XHTML content elements Using PARCC classes Using APIP QTI style sheets for item layout and rendering Including mathematics markup in items Using rubric blocks Encoding QTI item response and outcome data Disallowed features in PARCC items:o Item Templateso Modal Feedbacko Time Dependent Itemso LTI-Based ItemsV 0.65: Public Draft 20130912 53

Item Encoding and BehaviorPARCC Item Development Technical GuideDetails of encoding APIP accessibility are described in the Accessibility section of the Guide .The interaction types do not fully specify the item layout and behavior but focus on the overall requirements ofpresenting the stimulus and gathering the student response. While XHTML, class attributes and CSS are used todescribe the item, content may be produced in Java or HTML or other rendering formats to precisely control itemlayout in the test client. Rendering technology choices are limited by PARCC requirements , e.g., Flash is notacceptable. Test clients will have one widget per interaction type that controls layout and behavior. Thus someaspects of item presentation may be test-client specific and cannot be controlled by the item developer or arecontrolled by the item developer in a test-client specific way.Additional guidelines describe how to use test-client specific custom interactions for Technology-Enhanced Items(TEIs) and the use of Portable Custom Interactions [PCI] to create interoperable custom interactions.The Item Encoding guidelines are aligned with the Accessibility guidelines , Metadata guidelines andExchange guidelines . All items must have the appropriate accessibility data, be classified with metadata andpackaged and exchanged as indicated.All items and associated media data must conform to all of the Item Encoding and Behavior guidelines. Unlessotherwise noted, all XML documents must use the RTTA APIP Profile Schemata specified in the Schemata section.PARCC APIP QTI Item MappingTables 5.1, 5.2 and 5.3 describe the available PARCC items and are used to determine what interaction type to usefor a particular response type. The choice of interaction type is used to determine how to encode the item; details ofencoding for each interaction type and for Technology-Enhanced Items (TEIs) follow in subsequent sections.Each item must be assigned a PARCC Response Type metadata attribute, and must be implemented using one of theAPIP/QTI Interaction Types (or as a composite item combining different interactions). Table 5.1 maps eachPARCC Response Type to a suggested APIP/QTI Core Interaction Type. The table includes examples of possibleimplementations of an item that requires a custom interaction.Table 5.1: Response Type to Interaction Type MappingResponse TypeMultiple ChoiceFill In The BlankTrue FalseEssayMatchingShort AnswerLabelingVisual representationShow your workOther constructed responsePerformance taskOther extended responseInnovativeReorderingSuggested Interaction TypechoiceInteractiontextInteractionchoiceInteractionextendedTextInteractionmatchInteractiontextInteractiontextInteraction (E.g., blank labels underneath an image)customInteraction (E.g., an HTML 5 drawing canvas)compositeInteraction: one interaction for the main answer, another for the ShowYour Work response. Any combination of types is possible.extendedTextInteractioncustomInteraction (E.g., an HTML file upload form for task evidence. The files areto be evaluated manually.)customInteraction (E.g., an HTML file upload form for task evidence. The files areto be evaluated manually.)customInteraction (E.g., a JavaScript + HTML object that performs real timecalculations on answer input fields.)customInteraction (E.g., a JavaScript + HTML object that allows different items tobe ordered by drag and drop.)54 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Response TypeSubstitutionOtherSuggested Interaction TypetextInteraction (E.g., blank labels underneath an object).customInteractionThe different item interaction types are listed in Table 5.2 (alphanumeric codes in the first column align with APIPlabels for interaction types). The table indicates (via a ) if the interaction type is: Required by the APIP Core Profile Optional in the APIP Core Profile Used by PARCC Implemented as a TEI using a test-client specific implementation of a QTI custom interaction Implemented as a TEI using Portable Custom Interactions (all blank for now)Table 5.2: Interaction TypesInteraction TypeAPIPRequiredAPIPOptionalPARCCTypeCustomTEIQ1 Associate Interaction Q2 Choice Interaction Q3 Custom Interaction Q4 Drawing Interaction Q5 End Attempt Interaction Q6 Extended Text Interaction Q7 Gap Match Interaction Q8 Graphic Associate Interaction Q9 Graphic Gap Match Interaction Q10 Graphic Order Interaction Q11 Hotspot Interaction Q12 Hottext Interaction Q13 Inline Choice Interaction Q14 Match Interaction Q15 Media Interaction Q16 Order Interaction Q17 Position Object Interaction Q18 Selection Point Interaction Q19 Slider Interaction Q20 Text Entry Interaction Q21 Upload Interaction Scale InteractionPortableTEIAll of the PARCC item types (including TEIs) are listed in Table 5.3. The table indicates (via a ) how the TEI isimplemented: Implemented as standard QTI interaction Implemented as an extension of a standard QTI interaction Implemented as a new RTTA QTI interaction Implemented as a TEI using a test-client specific implementation of a QTI custom interaction Implemented as a TEI using Portable Custom Interactions (PCIs) (all blank for now; omitted from table)PARCC recommends that all items be developed using the most standard interaction type possible, e.g., standardQTI is preferred, followed by extended QTI, RTTA QTI, custom interactions and finally PCIs. Test-client specificcustom interactions and PCIs may only be used if they fully support all PARCC accessibility requirements.V 0.65: Public Draft 20130912 55

Item Encoding and BehaviorPARCC Item Development Technical GuideTable 5.3: PARCC (Technology-Enhanced) ItemsPARCC TEIItem TypeCategory 0 – Non TEI (Machine Scoring)Selected Response (MC)Gridded Response (GR)Multiple Select (MS)Constructed Response (CR/PCR)Category 1 – Non TEI (Human Scoring)Constructed Response with Equation EditorFill in the Blank (FIB)-Specific character setFill in the Blank (FIB)-Unconstrainedcharacter setFill in the Blank (FIB) with Equation EditorCategory 3 – TEI BasicDrag and Drop (DD)Hot Spot (HS)Multiple Choice Technology Enhanced(MCTE)Inline Choice (IC)/Drop downCategory 4 – TEI InnovativeComplex Drag and DropComplex Hot SpotText Extraction (EXT)/HighlightingLine Graph (LG)Bar Graph (BG)Fraction ModelText FlaggingText AnnotationItem-Specific WidgetFunction Graph (FG)Interactive Number line (NL)Composite Graph (CMG)Composite Graph with shapesGeometric TransformationZoom Number LineSolution Set GraphingPolygon Graph (PG)ScaleCategory 5 – TEI WowSimulationPresentation EditorWeb-searchFree-Form Graphic OrganizerStandardQTIExtendedQTIRTTAQTICustomInteraction56 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior QTI ItemsAs illustrated in Figure 5.1, a PARCC assessment item contains the XML elements listed below in Table 5.4. Eachof the elements is described in more detail below. As noted, elements are required () optional () or should notbe used (). Elements not listed (e.g., templates, feedback) are not used in PARCC items.Table 5.4: assessmentItem ElementsElementNotes responseDeclaration [0..*] outputDeclaration [0..*] styleSheet Not used for PARCC items itemBody Contains one or more rubric blocks (rubricBlock), iteminteractions or XHTML content blocks responseProcessing Use a template apip:accessibilityRequired attributes for the assessmentItem element are listed in Table 5.5. Any of the other attributes for theassessmentItem element are permitted.Table 5.5: assessmentItem Element Required AttributesAttribute Type Value Notesidentifier string Any Must match with the value in the identifier element in the metadatatitle string Any Must match with the value in the identifier element in the metadataadaptive boolean false Recommended optional attribute with default value falsetimeDependent boolean false The PARCC Profile may make this required attribute optional withdefault value falseCore attributes for the itemBody element are listed in Table 5.6. The class attribute (which can also be associatedwith any element in the interaction) can be used to specify a PARCC-specific rendering style. The id attribute(which can also be associated with any element in the interaction) is needed to link the element to accessibilityinformation . Any of the other attributes for the itemBody element are permitted.Table 5.6: itemBody Element AttributesAttribute Type Value Notesid string Any Must uniquely identify the element within the assessmentItemclass string Must be one of the PARCC rendering classesAttributed for the other elements are included in the description of the element.PARCC APIP QTI InteractionsAs shown in Table 5.2, the APIP profile defines five QTI interactions that are required in all APIP implementationsand 16 additional QTI interactions that are optional in an APIP implementation [APIP 1.0 Conformance: § 3.1](alphanumeric codes with each interaction type align with APIP labels for interaction types).A summary of each of the interactions follows, including a part of an example XML encoding of an item using theinteraction. The numbers following the name (e.g., Q2) refers to the interaction numbering used in APIP and thepresentation follows the order of interactions in the table.V 0.65: Public Draft 20130912 57

Item Encoding and BehaviorPARCC Item Development Technical GuideFor each interaction: Definition: A narrative description of the item. Type: The type of the interaction (APIP required, APIP optional, PARCC interaction). Test Client: indicates if the interaction is currently supported by the PARCC Test Client. Unsupportedinteractions () should not be used. Attributes: The list of attributes for the interaction (any attribute not listed is permitted unless formallyexcluded elsewhere, e.g., template attributes). For each attribute:o if the attribute is optional or if the attribute is required.o Name of the attribute.o Type of the attribute.o Acceptable PARCC attribute values.o Default attribute value if the attribute is not present.o Notes about the attribute. Elements: The list of elements included in the interaction (any element not listed is permitted unlessformally excluded elsewhere). Within an interaction, the elements must appear in the order listed. Theelements, their attributes and any contained subelements are detailed following the description of all of theinteractions. For each element:o if the element is optional, if the element is required or if PARCC guidelines exclude useof the element.o Name of the element.o Number of times the element can occur. If empty, only one occurrence is permitted.o Ordering of the elements when there are multiple instances. If empty, the elements are notordered.o Notes about the element. Response Declaration: The type of response declaration that can be used with the item, includingo Cardinality of the response variable.o Base Type of the response variable. Response Processing Template: The available response processing templates that can be used with the itemor an indication that the item must be human scored. Response Type: Response type metadata value. Scoring: Scoring mode metadata value. Example XML: An illustrative example of the XML for an item using the interaction. XML Validation: Validated (), partially validated—no known issues (), invalid or not validated ().Includes details on XML, Schema, Rendering, Behavior, Response Processing and Accessibility validation.No validation has been performed for Behavior, Response Processing and Accessibility. Example Description: A description of the example.Note: The example XML is for a QTI assessment item not an APIP QTI item and uses the IMS/QTI namespace.The item examples do not include accessibility features .58 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction choiceInteractionDefinition The choice interaction presents a set of choices to the student. The student task is to select one ormore of the choices, up to a maximum of maxChoices. The interaction is always initialized withno choices selected.Type APIP Required (Q2) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable shuffle boolean false false Must be false maxChoices integer any 0 QTI is , default 1 minChoices integer any 0 orientation orientation any noneElementsElement Number Order Notes(ordered) prompt Use inside itemBody simpleChoice [1..*] ordered See element detailsResponse Cardinality Base Type NotessingleidentifiermultipleidentifierResponse PT match_correctResponse TypeScoringExampleXML000102030405060708091011121314151617181920212223242526ChoiceA0Pick the right answer.This is the correct answer.This might be the correct answer.I don't know the correct answer.Example Validated: 20130614 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 59

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderingchoiceInteractionExampleDescriptionThe example shows a prompt and three choices. The example includes response processing usinga standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-10: Response variable RESPONSE definitiono Lines 07-09: Value for correctResponse Lines 11-15: Outcome variable SCORE definitiono Lines 12-14: Default value for SCORE Lines 16-23: The itemBody as a choiceInteractiono Line 17: Prompt for the answero Line 18: Choice Interaction indicating 1 choice can be madeo Lines 19-21: Each of the choice alternatives Lines 21-22: Declaration for the match_correct response processing template60 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction extendedTextInteractionDefinition An extended text interaction allows the student to enter a large block of text.Type APIP Required (Q6) [QTI Info 2.1: § 7.2]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable base integer any 10 stringIdentifier identifier any none expectedLength integer any none patternMatch string any none Regular expression placeholderText string any none maxStrings integer any none minStrings integer any 0 expectedLines integer any none format format any plainElementsElement Number Order Notes(ordered) promptUse inside itemBodyResponse Cardinality Base Type Notessinglestringsingleintegersinglefloatmultiple string Up to maxStringsordered string Up to maxStringsResponse PT None – Human ScoringResponse TypeScoring Human ScoringExampleXML00010203040506070809101112131415Translate the following paragraph into Klingon.Lorem ipsum dolor sit amet, consectetur adipiscing elit.Sed commodo orci nec elit imperdiet interdum. In sed nibh neque.Example Validated: 20130614 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 61

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderingextendedTextInteractionExampleDescriptionThe example shows a prompt and block of text along with corresponding extended text entry.In the example: Lines 00-05: The assessmentItem definition and its attributes Line 06: Response variable RESPONSE definition Line 07: Outcome variable SCORE definition Lines 08-14: The itemBodyo Line 09: Prompt for the answero Lines 10-11: An extended block of text; it could include XHTML markup andmediao Lines 12-13: The extendedTextInteraction; attributes of element provide hintsfor the size of the text input formThe extendedTextInteraction type does not support automated marking via response processing;no response processing is included. The response is stored for a human marker to evaluate.62 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionDefinitionhotspotInteractionA hotspot interaction presents the student with a corresponding set of choices that are defined asareas of the graphic image. The student task is to select one or more of the areas (hotspots). Thehotspot interaction should only be used when the spatial relationship of the choices with respectto each other (as represented by the graphic image) is important to the needs of the item.Otherwise, choiceInteraction should be used instead with separate material for each option.The test client must clearly indicate the selected area(s) of the image and may also indicate theunselected areas as well. Interactions with hidden hotspots are achieved with theselectPointInteraction.Type APIP Required (Q11) [QTI Info 2.1: § 7.2]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable maxChoices integer any 0 QTI is , default 1 minChoices integer any 0ElementsElement Number Order Notes(ordered) promptUse inside itemBody object 1 See element details hotSpotChoice [1..*] orderedResponse Cardinality Base Type NotessingleidentifiermultipleidentifierResponse PT match_responseResponse TypeScoringExampleXML00010203040506070809101112131415161718192021222324BIdentify the quadrant wherex is positive and y is negative.V 0.65: Public Draft 20130912 63

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderinghotspotInteractionExample Validated: 20130618 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: ExampleDescriptionThe example shows a prompt with an image with hot spots for selection. The example includesresponse processing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-10: Response variable RESPONSE definitiono Lines 07-09: Correct response Line: 11 Outcome variable SCORE definition Lines 12-21: The itemBodyo Line 13: Prompt for the answero Lines 14-20: The graphicAssociateInteractiono Line 15: The canvas for matchingo Lines 16-19: The hot spots for selection Lines 22-23: Declaration for the match_response response processing template64 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction matchInteractionDefinition A match interaction presents the student with two sets of choices and allows the student to createassociates between pairs of choices in the two sets, but not between pairs of choices in the sameset. Restrictions can still be placed on the allowable associations using the matchMax attributeof the choices.Type APIP Required (Q14) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable shuffle boolean false false Must be false maxAssociations integer any 1 minAssociations integer any 0ElementsElement Number Order Notes(ordered) promptUse inside itemBody simpleMatchSet [2] See element details (containssimpleAssociableChoice); first issource, second is targetResponse Cardinality Base Type NotessingledirectedPairsingledirectedPairResponse PT match_correctResponse TypeScoringV 0.65: Public Draft 20130912 65

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleXMLExampleRendering0001020304050607080910111213141516171819202122232425262728293031323334matchInteractionRB AIRA ANYB LAPA ACMatch the element with its classification.RbRaYbPaAlkaliAlkalineLanthanideActinideExample Validated: 20130616 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks requires the shuffle attribute on the matchInteraction.66 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleDescriptionmatchInteractionThe example shows a prompt with a 2-D grid of pairs to be matched. The example includesresponse processing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-13: Response variable RESPONSE definitiono Lines 08-10: Matching pairs Lines 14: Outcome variable SCORE definition Lines 15-31: The itemBodyo Line 16: Prompt for the answero Lines 17-30: The matchInteractiono Lines 18-23: The first match seto Lines 24-29: The second match set Lines 32-33: Declaration for the match_correct response processing templateV 0.65: Public Draft 20130912 67

Item Encoding and BehaviorPARCC Item Development Technical GuideInteraction textEntryInteractionDefinition A text Entry interaction is used to obtain a simple piece of text from the student. The test clientmust let the student review their choice within the context of the surrounding text.Type APIP Required (Q20) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable base integer any 10 stringIdentifier identifier any none expectedLength integer any none patternMatch string any none Regular expression placeholderText string any noneElementsElement Number Order Notes(ordered) prompt Use inside itemBodyResponse Cardinality Base Type NotessinglestringsingleintegersinglefloatResponse PT match_responseResponse TypeScoringExampleXML00010203040506070809101112131415161718192021222324betaWhat is the second letter in the Greek alphabet?Example Validated: 20130616 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: 68 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleRenderingtextEntryInteractionExampleDescriptionThe example shows a prompt with corresponding text entry for a short answer. The text entryinteraction is similar to the extended text interaction. The example includes response processingusing a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-14: Response variable RESPONSE definitiono Lines 07-09: Correct response Line 15: Outcome variable SCORE definition Lines 16-21: The itemBodyo Line 17: Prompt for the answero Line 19: The textEntryInteraction; attributes of element provide hints for thesize of the text input form Lines 22-23: Declaration for the match_response response processing templateThe text entry interaction is marked via machine response processing. The value bound to theRESPONSE variable is compared to correct and incorrect values stored in the responseDeclarationsection. In this example, the responseDeclaration contains a mapping for multiple spelling of theresponse.V 0.65: Public Draft 20130912 69

Item Encoding and BehaviorPARCC Item Development Technical GuideInteraction associateInteractionDefinition An associate interaction presents the student with a number of choices and allows the student tocreate associations between the choices.Type APIP Optional (Q1) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a responsevariable shuffle boolean false false Must be false maxAssociations integer any 1 minAssociations integer any 0ElementsElement Number Order Notes(ordered) promptUse inside itemBody simpleAssociableChoice [1..*] ordered See element detailsResponse Cardinality Base Type NotessinglepairmultiplepairResponse PT match_responseResponse TypeScoring70 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleXMLExampleRendering00010203040506070809101112131415161718192021222324252627282930313233343536associateInteractionEMAJOR G1GMINOR G2FMAJOR G3FMINOR G4Match the key and movements in Vivaldi’s "The Four Seasons"G minorF minorE majorF majorLa primaveraL'estateL'autunnoL'invernoExample Validated: 20130617 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 71

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleDescriptionassociateInteractionThe example shows a prompt with a set of tags to be matched. The example includes responseprocessing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-14: Response variable RESPONSE definitiono Lines 07-12: Correct responseso Lines 13-18: Response mappings Line 20: Outcome variable SCORE definition Lines 21-33: The itemBodyo Line 22: Prompt for the answero Lines 23-32: The associateInteractiono Lines 24-31: Items for the association Lines 34-35: Declaration for the match_response response processing template72 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction customInteractionDefinition The custom interaction provides the mechanism to support other types of interactions.Type APIP Optional (Q3) [QTI Info 2.1: § 7.4]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable extension extension any none Extension pointElementsElement Number Order Notes(ordered) promptUse inside itemBody ##otherExtension pointResponse Cardinality Base Type NotesResponse PTResponse TypeScoringExample 00XML 01020304050607080910111213ExampleRenderingBased on custom interactionExample Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: ExampleDescriptionThe example shows a template of a custom interaction. The full example is not included.In the example: Lines 00-05: The assessmentItem definition and its attributes Line 06: Response variable RESPONSE definition Line 07: Outcome variable SCORE definitiono Lines 08-12: The itemBodyo Lines 09-11: The customInteractiono Line 10: A placeholder for the content of the custom interactionV 0.65: Public Draft 20130912 73

Item Encoding and BehaviorPARCC Item Development Technical GuideInteraction drawingInteractionDefinition The drawing interaction lets the student use a common set of drawing tools to modify an image.Type APIP Optional (Q4) [QTI Info 2.1: § 7.4]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variableElementsElement Number Order Notes(ordered) promptUse inside itemBody object 1 See element detailsResponse Cardinality Base Type Notessingle file Same mime type as source imageResponse PT None – Human ScoringResponse TypeScoring Human ScoringExampleXMLExampleRendering00010203040506070809101112131415Starting in the upper left hand quadrant and working clockwise,color the quadrants using CMYK ink colors.ImageExample Validated: 20130617 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks does not support rendering of the drawingInteraction.74 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleDescriptiondrawingInteractionThe example shows a prompt for interactions and a base canvas for drawing.In the example: Lines 00-05: The assessmentItem definition and its attributes Line 06: Response variable RESPONSE definition Line 07: Outcome variable SCORE definition Lines 08-14: The itemBodyo Lines 09-10: Prompt for the answero Lines 11-13: The drawingInteractiono Line 12: The base canvas for the drawingV 0.65: Public Draft 20130912 75

Item Encoding and BehaviorPARCC Item Development Technical GuideInteraction endAttemptInteractionDefinition The end attempt interaction provides the student a way to terminate an attempt. It is used to addan interaction to the item. The responseIdentifier is set to true if the endAttemptInteraction isinvoked; this can be used in response processing to control the item’s behavior.Type APIP Optional (Q5) [QTI Info 2.1: § 7.5]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable title string any none countAttempt boolean any none APIP addition, not in QTIElementsElement Number Order Notes(ordered) promptUse inside itemBodyResponse Cardinality Base Type NotessinglebooleanResponse PT NoneResponse TypeScoringExampleXMLExampleRendering0001020304050607080910111213141516171819Translate the following paragraph into Klingon.Lorem ipsum dolor sit amet, consectetur adipiscing elit.Sed commodo orci nec elit imperdiet interdum. In sed nibh neque.Example Validated: 20130618 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: 76 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleDescriptionendAttemptInteractionThe example adds an end attempt interaction to an extended text entry item. The example showsa prompt and block of text along with corresponding extended text entry and exit button.In the example: Lines 00-05: The assessmentItem definition and its attributes Line 06: Response variable RESPONSE definition for the text entry Line 07: Response variable RESPONSE definition for the end attempt interaction Line 08: Outcome variable SCORE definition Lines 09-18: The itemBodyo Line 10: Prompt for the answero Lines 11-12: An extended block of text; it could include XHTML markup andmediao Lines 13-14: The extendedTextInteraction; attributes of element provide hintsfor the size of the text input formo Lines 15-17: The endAttemptInteraction; attributes control what is displayedV 0.65: Public Draft 20130912 77

Item Encoding and BehaviorPARCC Item Development Technical GuideInteraction gapMatchInteractionDefinition A gap match interaction contains a number of gaps that the student can fill from an associated setof choices. Each gap can have one choice pairing a gap and target. The student must be able toreview the content with the gaps filled in context, as indicated by their choices.Type APIP Optional (Q7) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable shuffle boolean false false Must be falseElementsElement Number Order Notes(ordered) promptUse inside itemBody gapText [1..*] ordered See element details gapImggapText and gapImg are exclusive gap [1..*] ordered See element detailsResponse Cardinality Base Type NotessingledirectedPairsingledirectedPairResponse PT match_responseResponse TypeScoring78 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleXMLExampleRendering000102030405060708091011121314151617181920212223242526272829303132333435363738gapMatchInteractionEMAJOR G1GMINOR G2FMAJOR G3FMINOR G4Identify the key for each of the four movements of Vivaldi’s "The Four Seasons"G minorF minorE majorF majorConcerto No. 1 in , Op. 8, RV 269, "La primavera" (Spring)Concerto No. 2 in , Op. 8, RV 315, "L'estate" (Summer)Concerto No. 3 in , Op. 8, RV 293, "L'autunno" (Autumn)Concerto No. 4 in , Op. 8, RV 297, "L'inverno" (Winter)Example Validated: 20130616 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks requires the shuffle attribute on the gapMatchInteraction.V 0.65: Public Draft 20130912 79

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleDescriptiongapMatchInteractionThe example, using gap text, shows a prompt with four items containing gaps and a set ofalternatives for the gaps. The example includes response processing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-19: Response variable RESPONSE definitiono Lines 07-12: Correct responseso Lines 13-18: Response mappings Line 20: Outcome variable SCORE definition Lines 21-35: The itemBodyo Line 22: Prompt for the answero Lines 23-34: The gapMatchInteractiono Lines 24-27: The values that can go into the gapso Lines 29-32: The item content containing the gaps Lines 36-37: Declaration for the match_response response processing template80 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionDefinitiongraphicAssociateInteractionA graphic associate interaction presents the student with a set of choices that are defined as areasof the graphic image. The student is to associate the areas (hotspots) with each other.The graphic associate interaction should only be used when the graphical relationship of thechoices with respect to each other (as represented by the graphic image) is important to the needsof the item. Otherwise, associateInteraction should be used.Type APIP Optional (Q8) [QTI Info 2.1: § 7.3]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable maxAssociations integer any 1 minAssociations integer any 0ElementsElement Number Order Notes(ordered) promptUse inside itemBody objectSee element details associableHotspot [1..*] ordered See element detailsResponse Cardinality Base Type NotessinglepairmultiplepairResponse PT match_responseResponse TypeScoringV 0.65: Public Draft 20130912 81

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleXMLExampleRendering000102030405060708091011121314151617181920212223242526272829303132333435graphicAssociateInteractionA BB CMake two connections:Both points have positive x coordinatesBoth points have positive y coordinatesExample Validated: 20130618 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: 82 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleDescriptiongraphicAssociateInteractionThe example shows a prompt with an image with hot spots for associations. The exampleincludes response processing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-19: Response variable RESPONSE definitiono Lines 07-10: Correct responseso Lines 11-18: Response mappings Line 20: Outcome variable SCORE definition Lines 21-32: The itemBodyo Lines 22-24: Prompt for the answero Lines 25-31: The graphicAssociateInteractiono Line 26: The canvas for matchingo Lines 27-30: The hot spots for association Lines 33-34: Declaration for the match_response response processing templateV 0.65: Public Draft 20130912 83

Item Encoding and BehaviorPARCC Item Development Technical GuideInteraction graphicGapMatchInteractionDefinition A graphic gap match interaction presents the student with a set of gaps that are defined as areas(hotspots) of the graphic image and an additional set of gap choices that are defined outside theimage. The student must associate the gap choices with the gaps in the image and be able toreview the image with the gaps filled in context, as indicated by their choices. It must be clear tothe student which hotspot each choice has been associated with.Type APIP Optional (Q9) [QTI Info 2.1: § 7.3]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variableElementsElement Number Order Notes(ordered) promptUse inside itemBody object 1 See element details gapImg [1..*] ordered See element details associableHotspot [1..*] ordered See element detailsResponse Cardinality Base Type NotessinglepairmultiplepairResponse PT match_responseResponse TypeScoring84 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleXML00010203040506070809101112131415161718192021222324252627282930313233343536373839404142434445graphicGapMatchInteractionFIRST ASECOND BTHIRD CFOURTH DLabel the quadrantsExample Validated: 20130618 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 85

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderinggraphicGapMatchInteractionExampleDescriptionThe example shows a prompt with four items containing gaps and a set of alternatives for thegaps. The example includes response processing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-19: Response variable RESPONSE definitiono Lines 07-12: Correct responseso Lines 13-18: Response mappings Line 20: Outcome variable SCORE definition Lines 21-42: The itemBodyo Line 22: Prompt for the answero Lines 23-41: The gapMatchInteractiono Line 24: The canvas for matchingo Lines 25-36: The images that can go into the gapso Lines 37-40: The targets for the content Lines 43-44: Declaration for the match_response response processing template86 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionDefinitiongraphicOrderInteractionA graphic order interaction presents the student with a set of choices that are defined as areas ofthe graphic image. The student is to impose an ordering on the areas (hotspots).The interaction should only be used when the spatial relationship of the choices with respect toeach other (as represented by the graphic image) is important. Otherwise, orderInteractionshould be used.Type APIP Optional (Q10) [QTI Info 2.1: § 7.3]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable minChoices integer any all Default: All choices to beordered maxChoices integer any all Default: All choices to beorderedElementsElement Number Order Notes(ordered) promptUse inside itemBody object 1 See element details hotSpotChoice [1..*] ordered See element detailsResponse Cardinality Base Type NotesorderedidentifierResponse PT match_correctResponse TypeScoringExampleXML00010203040506070809101112131415161718192021222324252627ABCDStarting in the upper left hand quadrant, label the center of the quadrants counterclockwise.ImageV 0.65: Public Draft 20130912 87

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderinggraphicOrderInteractionExample Validated: 20130617 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: ExampleDescriptionThe example shows a prompt, the image and a set of items to be ordered. The example includesresponse processing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-13: Response variable RESPONSE definitiono Lines 07-12: Values for correctResponse Line 14: Outcome variable SCORE definition Lines 15-24: The itemBody as a graphicOrderInteractiono Line 16: Prompt for the answero Lines 17-23: Hot Text Interaction indicating 1 choice can be madeo Lines 19-22: Each of the alternatives Lines 25-26: Declaration for the match_correct response processing template88 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction hottextInteractionDefinition The hot text interaction presents the student with a set of choices represented as selectable blocksof text embedded within a surrounding context. Like choiceInteraction, the student is to selectone or more of the choices, up to a maximum of maxChoices. The interaction is initialized fromthe defaultValue of the associated response variable, a NULL value indicating that no choices areselected.Type APIP Optional (Q12) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable maxChoices integer any 0 QTI is , default 1 minChoices integer any 0ElementsElement Number Order Notes(ordered) promptUse inside itemBody hottext [1..*] ordered See element detailsCan be within other XHTMLResponse Cardinality Base Type NotessingleidentifiermultipleidentifierResponse PT match_correctResponse TypeScoringV 0.65: Public Draft 20130912 89

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleXMLExampleRendering0001020304050607080910111213141516171819202122232425262728293031hottextInteractionAc0Which element is not a Lanthanide?CeGdAcTbLaNoneExample Validated: 20130617 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: ExampleDescriptionThe example shows a prompt and a set of choices. The example includes response processingusing a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-10: Response variable RESPONSE definitiono Lines 07-09: Value for correctResponse Lines 11-15: Outcome variable SCORE definitiono Lines 12-14: Default value for SCORE Lines 16-23: The itemBody as a hottextInteractiono Line 17: Prompt for the answero Lines 18-27: Hot Text Interaction indicating 1 choice can be madeo Lines 20-25: Each of the alternatives Lines 29-30: Declaration for the match_correct response processing template90 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction inlineChoiceInteractionDefinition An inline choice interaction presents the student with a set of choices, each of which is a simplepiece of text. The student is to select one of the choices. Unlike the choiceInteraction, the testclient must let the student review their choice within the context of the surrounding text.Type APIP Optional (Q13) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable shuffle boolean false false Must be false required boolean false falseElementsElement Number Order Notes(ordered) promptUse inside itemBody inlineChoice [1..*] ordered See element detailsCan be within other XHTMLResponse Cardinality Base Type NotessingleidentifierResponse PT match_correctResponse TypeScoringExampleXML0001020304050607080910111213141516171819202122232425262728B0What is the missing value in the ASCII sequence?# $*%^&amp; 'Example Validated: 20130616 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 91

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderinginlineChoiceInteractionExampleDescriptionThe example shows a prompt and three inline choices. The example includes responseprocessing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-10: Response variable RESPONSE definitiono Lines 07-09: Value for correctResponse Lines 11-15: Outcome variable SCORE definitiono Lines 12-14: Default value for SCORE Lines 16-25: The itemBody as a choiceInteractiono Line 17: Prompt for the answero Lines 19-23: Inline Choice Interaction bound to responseo Lines 20-21: Each of the choice alternatives Lines 26-27: Declaration for the match_correct response processing template92 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction mediaInteractionDefinition The media interaction lets the student control the interaction with a time-based media object andallows the number of times the media object was experienced to be reported in the value of theassociated response variable.Type APIP Optional (Q15) [QTI Info 2.1: § 7.4]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable autostart boolean any none minPlays integer any 0 maxPlays integer any 0 loop boolean any falseElementsElement Number Order Notes(ordered) promptUse inside itemBody object 1 See element detailsResponse Cardinality Base Type Notessingle integer Number of media interactionsResponse PT None – Human ScoringResponse TypeScoring Human ScoringExampleXMLExampleRendering0001020304050607080910111213AudioExample Validated: 20130617 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks does not support rendering of the mediaInteraction.V 0.65: Public Draft 20130912 93

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleDescriptionmediaInteractionThe example shows a media interaction.In the example: Lines 00-05: The assessmentItem definition and its attributes Line 06: Response variable RESPONSE definition Line 07: Outcome variable SCORE definition Lines 08-12: The itemBodyo Lines 09-11: The mediaInteractiono Line 10: The media object94 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction orderInteractionDefinition The order interaction presents an ordered set of choices. The student task is to reorder thechoices. By default the task is to order all of the choices, but a subset of the choices can bespecified using the maxChoices and minChoices attributes.Type APIP Optional (Q16) [QTI Info 2.1: § 7.1]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string any none See list of PARCC classes responseIdentifier identifier any none Must match a response variable shuffle boolean false false Must be false minChoices integer any all Default: All choices to beordered maxChoices integer any all Default: All choices to beordered orientation orientation anyElementsElement Number Order Notes(ordered) promptUse inside itemBody simpleChoice [1..*] ordered See element detailsResponse Cardinality Base Type Notesordered identifier Default value overridesResponse PT match_correctResponse TypeScoringExampleXML00010203040506070809101112131415161718192021222324OrderAOrderBOrderCOrder these.Put me in the middle.I'm last.Me first.Example Validated: 20130614 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks requires the shuffle attribute on the orderInteraction.QTIWorks fails validating the response processing template.V 0.65: Public Draft 20130912 95

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderingorderInteractionExampleDescriptionThe example shows a prompt and three items to be ordered. The example includes responseprocessing using a standard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-12: Response variable RESPONSE definitiono Lines 07-11: Values for correctResponse Line 13: Outcome variable SCORE definition Lines 14-21: The itemBody as an orderInteractiono Line 15: Prompt for the answero Line 16: Order Interactiono Lines 17-19: Each of the items to be ordered Lines 22-23: Declaration for the match_correct response processing template96 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction positionObjectInteractionDefinition The position object interaction presents a single image which must be positioned on anotherimage by the student. The actual positions selected by the student are indicated by the test client.Type APIP Optional (Q17) [QTI Info 2.1: § 7.3]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable centerPointintegerpairany imagecenter[0..2] – two values. APIP spellingis centrePoint maxChoices integer any 0 QTI is , default 1 minChoices integer any none Other interactions have default 0ElementsElement Number Order Notes(ordered) object 1 See element details positionObjectStage 1 Object and interaction containerResponse Cardinality Base Type Notessingle point May have areaMappingmultiplepointResponse PT map_response_pointResponse TypeScoringExampleXML0001020304050607080910111213141516171819202122232425262728150 15050 50Position the targets in the center of the upper right and lower left quadrants.ImageExample Validated: 20130614 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks does not render the target.V 0.65: Public Draft 20130912 97

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderingpositionObjectInteractionExampleDescriptionThe example shows a prompt and an image. The example includes response processing using astandard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-15: Response variable RESPONSE definitiono Lines 07-10: Values for correctResponseo Lines 11-14: The values for the mapping area Line 16: Outcome variable SCORE definition Lines 17-25: The itemBody as a selectPointInteractiono Line 18: Prompt for the answero Lines 19-24: The “stage” for positioning the objects.o Lines 21-23: The position object interactiono Line 22: The target object to be positioned on the stage Lines 26-27: Declaration for the map_response_point response processing template98 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction selectPointInteractionDefinition The select point interaction presents a single image. The student must select one or more pointson the image. The actual positions selected by the student shall be indicated by the test client.Type APIP Optional (Q18) [QTI Info 2.1: § 7.3]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable maxChoices integer any 0 QTI is , default 1 minChoices integer any 0ElementsElement Number Order Notes(ordered) promptUse inside itemBody object 1 See element detailsResponse Cardinality Base Type Notessingle point May use areaMappingmultiplepointResponse PT map_response_pointResponse TypeScoringExampleXML0001020304050607080910111213141516171819202122232450 50Pick the center of the lower-left quadrant.

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderingselectPointInteractionExampleDescriptionThe example shows a prompt and an image. The example includes response processing using astandard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-13: Response variable RESPONSE definitiono Lines 07-09: Value for correctResponseo Lines 10-12: The value mapping area Line 14: Outcome variable SCORE definition Lines 15-20: The itemBody as a selectPointInteractiono Line 16: Prompt for the answero Line 17: The select point interactiono Line 18: The image object for the interaction Lines 21-22: Declaration for the map_response_point response processing template100 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction sliderInteractionDefinition The slider interaction presents the student with a control for selecting a numeric value between alower and upper bound.Type APIP Optional (Q19) [QTI Info 2.1: § 7.4]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable lowerBound double any none QTI is float upperBound double any none QTI is float step double any 1.0 QTI is float stepLabel boolean any false orientation orientation any none reverse boolean any noneElementsElement Number Order Notes(ordered) promptUse inside itemBodyResponse Cardinality Base Type NotessingleintegersinglefloatResponse PT map_responseResponse TypeScoringExampleXML0001020304050607080910111213141516171819202122232450How percentage of people will pick the right answer?Example Validated: 20130617 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks ignores the stepLabel attribute.V 0.65: Public Draft 20130912 101

Item Encoding and BehaviorPARCC Item Development Technical GuideInteractionExampleRenderingsliderInteractionExampleDescriptionThe example shows a prompt and a slider. The example includes response processing using astandard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-15: Response variables RESPONSE definitiono Lines 07-09: Value for correctResponseo Lines 11-13: The value mapping areas Line 16: Outcome variable SCORE definition Lines 17-21: The itemBody as a selectPointInteractiono Line 18: Prompt for the answero Lines 19-20: The slider interaction Lines 22-23: Declaration for the map_respons response processing template102 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Interaction uploadInteractionDefinition The upload interaction allows the student to upload a file representing their response.Type APIP Optional (Q21) [QTI Info 2.1: § 7.4]Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable type mime Type any noneElementsElement Number Order Notes(ordered) promptUse inside itemBodyResponse Cardinality Base Type NotessinglefileResponse PT None – Human ScoringResponse TypeScoring Human ScoringExampleXMLExampleRendering00010203040506070809101112Create a PowerPoint presentation and upload the file....Example Validated: 20130616 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: QTIWorks does not accept the mimeType attribute.ExampleDescriptionThe example shows a prompt and an upload.In the example: Lines 00-05: The assessmentItem definition and its attributes Line 06: Response variable RESPONSE definition; single response of type file requiredfor an upload interaction Line 07: Outcome variable SCORE definition Lines 08-14: The itemBodyo Line 09: Prompt for the answero Line 10: The upload interaction; the mimeType attribute specifies aPowerpoint fileV 0.65: Public Draft 20130912 103

Item Encoding and BehaviorPARCC Item Development Technical GuidePARCC InteractionsPARCC has defined additional interaction types as listed in Table 5.2. A summary of each interaction follows usingthe same format used to describe the APIP interactions.InteractionDefinitionscaleInteractionThe scale interaction presents the student with a control for selecting a numeric value between alower and upper bound on a specific scale shape. The scale may be horizontal, vertical,semicircular or circular.Scale is an extension of sliderInteraction. The test client must support the different scale shapesand the reverse attribute. The orientation attribute is dropped from the slider interaction.scaleShapes values are:o horizontal – default orientation is left to right. The reverse attribute labels the scalefrom right to left.o vertical – default orientation is bottom to top. The reverse attribute labels the scalefrom top to bottom.o semiCircle – default orientation is clockwise starting at the left midline and thesemicircle above the baseline (positive hemisphere). The reverse attribute labels thesemicircle from the right end counter clockwise.o circle – default orientation is clockwise with 0 at the left midline. The reverse attributelabels the circle clockwise with 0 at the right midline.Other shapes (e.g., negative hemisphere, left/right hemisphere) are not supported.TypePARCC defined interaction, extension of sliderInteraction.Test Client Attributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classes responseIdentifier identifier any none Must match a response variable lowerBound double any none upperBound double any none step double any 1.0 stepLabel boolean any false scaleShape scaleShape any horizontal Added to sliderInteraction reverse boolean any false orientation orientation any none Deleted from sliderInteractionElementsElement Number Order Notes(ordered) promptUse inside itemBodyResponse Cardinality Base Type NotessingleintegersinglefloatResponse PT map_responseResponse TypeScoring104 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior InteractionExampleXMLExampleRenderingMockup00010203040506070809101112131415161718192021222324scaleInteraction55What is the speed limit?Example Validated: not validatedXML: QTI Schema: Rendering: Behavior: Response: Accessibility: ExampleDescriptionThe example shows a prompt and a scale. The example includes response processing using astandard template.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-15: Response variables RESPONSE definitiono Lines 07-09: Value for correctResponseo Lines 11-13: The value mapping areas Line 16: Outcome variable SCORE definition Lines 17-21: The itemBody as a scaleInteractiono Line 18: Prompt for the answero Lines 19-20: The scale interactiono Lines 22-23: Declaration for the map_response response processing templateV 0.65: Public Draft 20130912 105

Item Encoding and BehaviorPARCC Item Development Technical GuidePARCC APIP QTI Interaction ElementsInteractions may include interaction-specific elements. Elements used with PARCC interactions include: associableHotSpot [QTI Info 2.1: § 7.3] gap [QTI Info 2.1: § 7.1] gapImg [QTI Info 2.1: § 7.1] gapText [QTI Info 2.1: § 7.1] hotspotChoice [QTI Info 2.1: § 7.3] hotText [QTI Info 2.1: § 7.2] inlineChoice [QTI Info 2.1: § 7.2] prompt [QTI Info 2.1: § 7] positionObjectStage [QTI Info 2.1: § 7.3] simpleAssociableChoice [QTI Info 2.1: § 7.1] simpleChoice [QTI Info 2.1: § 7.1] simpleMatchSet [QTI Info 2.1: § 7.1] object [QTI Info 2.1: § 6.2.3]Any interaction element not listed is permitted unless formally excluded elsewhere.A summary of each of the elements follows. For each element: Definition: A narrative description of the element. Type: The type of the element (APIP QTI, PARCC APIP Profile, RTTA APIP Profile). Interactions: The interactions that use the element. Attributes: The list of element attributes (any attribute not listed is permitted unless formally excludedelsewhere, e.g., template attributes). For each attribute:o if the attribute is optional or if the attribute is required.o Name of the attribute.o Type of the attribute.o Acceptable attribute values.o Default attribute value if the attribute is not present.o Notes about the attribute Elements: The list of subelements included in the element (any element not listed is permitted unlessformally excluded elsewhere). Within the element, the subelements must appear in the order listed. Theelements, their attributes and any contained subelements are detailed elsewhere in the list. For eachelement:o if the element is optional, if the element is required or if PARCC guidelines exclude useof the element.o Name of the element.o Number of times the element can occur. If empty, only one occurrence is permitted.o Ordering of the elements when there are multiple instances. If empty, the elements are notordered.o Notes about the subelement. Notes: Notes about the element.106 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Element associableHotSpotDefinition Hot spot area for an image in image interaction.Type APIP QTI [QTI Info 2.1: § 7.3]Interactions graphicAssociateInteractiongraphicGapMatchInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none Must match a response variable class string none See list of PARCC classes fixed boolean any false showHide showhide any show matchGroup identifier any none Deprecated in APIP shape shape any none coords coords any none string of values hotSpotLabel string any none matchMax integer any none if matchMin is 0, unrestricted matchMin integer any 0ElementsElement Number Order Notes(ordered)NoneNotesElement gapDefinition Description of a gap placeholder in a gap match interaction.Type APIP QTI [QTI Info 2.1: § 7.1]Interactions gapMatchInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean any false showHide showhide any show matchGroup identifier any none Deprecated in APIP required boolean any falseElementsElement Number Order Notes(ordered)NoneNotesV 0.65: Public Draft 20130912 107

Item Encoding and BehaviorPARCC Item Development Technical GuideElement gapImgDefinition An image that is used to fill in a gap in a graphic gap match interaction or gap match interaction.Type APIP QTI [QTI Info 2.1: § 7.1]Interactions gapMatchInteractiongraphicGapMatchInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean any false showHide showhide any show matchGroup identifier any none Deprecated in APIP matchMax integer any none matchMin integer any 0 objectLabel String Any NoneElementsElement Number Order Notes(ordered) object 1 See element detailsNotesElement gapTextDefinition A choice that is used to fill a gap in a gap match interaction.Type APIP QTI [QTI Info 2.1: § 7.1]Interactions gapMatchInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string any none See list of PARCC classes fixed boolean any false showHide showhide any show matchGroup identifier any none Deprecated in APIP matchMax integer any none if matchMin is 0, unrestricted matchMin integer any 0ElementsElement Number Order Notes(ordered)NoneNotes108 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Element hotspotChoiceDefinition A container for a hot spot choice.Type APIP QTI [QTI Info 2.1: § 7.3]Interactions graphicOrderInteractionhotspotInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean any false showHide showhide any show shape shape any none coords coords any none string of values hotSpotLabel string any noneElementsElement Number Order Notes(ordered)NoneNotesElement hotTextDefinition A block of text in a hot text interaction that provides a choice.Type APIP QTI [QTI Info 2.1: § 7.2]Interactions hottextInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean any false showHide showhide any showElementsElement Number Order Notes(ordered) gapContains either a block of hottexttext or a gapNoteshotText may not contain any nested interactions of hot text areas.Element inlineChoiceDefinition A container for item choice interaction content.Type APIP QTI [QTI Info 2.1: § 7.2]Interactions inlineChoiceInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean any false showHide showhide any showElementsElement Number Order Notes(ordered)XHTMLNotesV 0.65: Public Draft 20130912 109

Item Encoding and BehaviorPARCC Item Development Technical GuideElement promptDefinition A container for item choice interaction content.Type APIP QTI [QTI Info 2.1: § 7]Interactions MostAttributes Attribute Type Value Default Notes id identifier any none class string none See list of PARCC classesElementsElement Number Order Notes(ordered)XHTMLNotesCannot contain any nested interactions.PARCC recommendation is to use instead. But must appear outside the interactionin the itemBody.Element positionObjectStageDefinition A container for an object and a position object interactions.Type APIP QTI [QTI Info 2.1: § 7.3]Interactions positionObjectInteractionAttributes Attribute Type Value Default NotesNone – just a containerElementsElement Number Order Notes(ordered) object 1 See element details positionObjectInteraction [0..*] ordered See interactionNotesElement simpleAssociableChoiceDefinition A container for item choice interaction content. It cannot include nested interactions.Type APIP QTI [QTI Info 2.1: § 7.1]Interactions associateInteractionmatchInteraction via simplematchsetAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean any none No default showHide showhide any none matchGroup identifier any none Deprecated in APIP matchMax integer any none if matchMin is 0, unrestricted matchMin integer any 0ElementsElement Number Order Notes(ordered)XHTMLNotes110 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Element simpleChoiceDefinition A container for item choice interaction content. It cannot include nested interactions.Type APIP QTI [QTI Info 2.1: § 7.1]Interactions choiceInteractionorderInteractionAttributes Attribute Type Value Default Notes id identifier any none identifier identifier any none class string none See list of PARCC classes fixed boolean false false showHide showhide any showElementsElement Number Order Notes(ordered)XHTMLNotesElement simpleMatchSetDefinition An ordered set of choices used for source and target in a match interaction.Type APIP QTI [QTI Info 2.1: § 7.1]Interactions matchInteractionAttributes Attribute Type Value Default NotesNone – just a containerElementsElement Number Order Notes(ordered) simpleAssociableChoice [0..*] ordered See element detailsNotesElement objectDefinition A media (graphic/image, audio, video) element used within an interaction.Type APIP QTI [QTI Info 2.1: § 6.2.3]Interactions drawingInteractiongapImggraphicAssociateInteractiongraphicGapMatchInteractiongraphicOrderInteractionhotspotInteractionmediaInteractionpositionObjectInteractionpositionObjectStageselectPointInteractionAttributes Attribute Type Value Default Notes id identifier any none class string any none See list of PARCC classes data string any none type mime Type any none width length any none Pattern [0-9]+%? height length any none Pattern [0-9]+%?ElementsElement Number Order Notes(ordered)NoneNotesV 0.65: Public Draft 20130912 111

Item Encoding and BehaviorPARCC Item Development Technical GuidePARCC APIP Custom Interactions and Technology-Enhanced ItemsAs shown in Table 5.1, some of the PARCC items cannot be realized using the available APIP/QTI interactions.Custom Interactions [QTI Info 2.1: § 7.4] provide an extension mechanism to define additional interaction types thatcan be used to describe items. By their nature, custom interaction implementations are specific to a test client(APIP/QTI implementation guidelines for custom interactions are not specified) and thus they are not interoperableacross test clients.A PARCC Technology-Enhance Item (TEI) includes any item that has more media interactions and behaviors thanstatic text or images. TEIs are independent of item response type. A TEI using a custom interaction could bedeveloped for any of the response types (see Table 5.1), e.g., a simple choiceInteraction could be developed as a TEIusing a custom interaction.Guidelines for creating test-client specific TEIs and using custom interactions for the current PARCC test clients aredescribed below.TEIs must function on all PARCC test clients and devices . TEIs may use a combination of Java, HTML,JavaScript (ECMAScript) [ECMAScript], JavaScript Object Notation (JSON) [JSON], and Cascading Style Sheets(CSS) [CSS]. TEIs may not use technologies not supported on all devices, e.g., Flash.To Do: Fill in TEI custom interaction guidelines from current Pearson and ETS guides for TEIs.PARCC APIP Portable Custom InteractionsTo support interoperability, PARCC encourages TEIs that use the customInteraction type to use Portable CustomInteractions (PCI). Portable Custom Interactions provides a standardized communications interface [PCI] between arendering engine/test client and an item. It allows an item’s behavior to be programmed using a combination ofHTML5 [HTML], Cascading Style Sheets (CSS) [CSS] JavaScript (ECMAScript) [ECMAScript] and JavaScriptObject Notation (JSON) [JSON], using the PCI API interface to obtain item attributes that control item renderingand passing results back to the test client. PCI uses a JavaScript object (or some other media object capable ofcommunicating with JavaScript calls) in the test client to manage the student's interaction with the item, and passback responses to be processed through the API.The PCI specification addresses general features of the interoperability solution, the communications API andpackaging of items that use PCI. Specifics of how to implement each TEI behavior and item rendering throughHTML, JavaScript and JSON are not defined in the PCI specification and may be item specific.Subsequent versions of this Guide will provide guidelines that describe how to implement PARCC TEIs and custominteractions using HTML5, CSS, JavaScript and JSON in combination with a PARCC open-source library ofJavaScript functions and style sheets. Using these standard TEI PCI templates, code libraries, style sheets andcoding guidelines reduces item development effort and improves interoperability.Future Guide Version: Provide general guidelines on rendering and behavior, packaging, shared libraries, HTML5,style sheets, …Future Guide Version: Provide an example or template for each TEI to be implemented using PCIs.112 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Composite ItemsComposite items contain multiple interactions within the assessment item. Composite items may be created withoutrestrictions. No special encoding of the item is required. The item metadata should indicate that the item is acomposite item using the composite item metadata element. Code listing 5.1 illustrates a composite item.Code Listing 5.1: Composite Item Example00010203040506070809101112131415161718192021222324252627282930313210002.50The side of a cube is 10 inches.What is the volume of the cube?The side of a square right prism is 20 inches.It has the same volume as the cube.What is the length of the square prism?Example Validated: 20130615 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-10: Response variable RESPONSE_1 definition for the first responseV 0.65: Public Draft 20130912 113

Item Encoding and BehaviorPARCC Item Development Technical Guideo Lines 07-09: Value for correctResponseLines 11-15: Response variable RESPONSE_2 definition for the second responseo Lines 12-14: Value for correctResponseLines 16-20: Outcome variable SCORE definitiono Lines 17-19: Default value for SCORELines 21-31: The itemBody for a pair of text interactionso Line 24: The first text entryo Line 29: The second text entryPARCC Content ElementsPARCC items may use any of the QTI XHTML content elements [QTI Info 2.1: § 6.2] for structured content.PARCC items should not use the prompt element. Item prompts should be encoded within XHTML div tags.PARCC Content ClassesFuture Guide Version: Provide list of all classes that can be used with items.PARCC APIP QTI Cascading Style SheetsQTI item descriptions [QTI Info 2.1: § 6.5] may include cascading style sheets [CSS]. Item CSS (stylesheetelement) should not be included in PARCC items and will not be validated. Item CSS will be ignored by thePARCC Test Client and may be deleted from the item when it is imported into the PARCC item bank.MathMLQTI items may include mathematical markup using MathML [MathML]. MathML content may be used throughoutan item wherever content text item can occur.Items that include MathML require the appropriate namespace declaration be included with the item. Code Listing5.1 illustrates a typical namespace declaration for MathML added to the math element in the assessment item.Code Listing 5.2: MathML Namespace Example: Math Element010203040506...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Line 01: Namespace declaration for MathML Line 02: Namespace declaration for XML Schema Lines 03-04: Schema location for MathML as a pair of values114 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior o Line 03: MathML namespace URIo Line 04: Location of the MathML schema that corresponds to the namespace in line 03Alternatively, the namespace declaration may be included in the assessment element as illustrated in Code Listing5.2.Code Listing 5.3: MathML Namespace Example: Assessment Item Element0102030405060708...Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Line 03: Namespace declaration for MathML Line 04: Namespace declaration for XML Schema Lines 05-06: Schema location for MathML as a pair of valueso Line 05: MathML namespace URIo Line 06: Location of the MathML schema that corresponds to the namespace in line 05The top-level math element supports several attributes [MathML: §2.2], including those listed in Table 5.6. Foreach attribute: Attribute: The attribute name. Use: Details if the attribute is required (), optional () or should not be used () with the math element. Default: The default value for the attribute. PARCC Value: The value that PARCC requires if different than the default value. Notes: Usage notes for the attribute.Any of the other attributes for the math element are permitted.Table 5.7: math Element AttributesAttribute Use Default PARCC Value Notesid none Element id for cross referencingdisplay inline inline Use inline for inline renderingUse block for a separate blockoverflow linebreak scroll Attribute must …dir ltr lrt Layout is left-to-rightmathcolor Page foreground color Foreground colormathbackground Page background color Background colormaxwidth ?? Available width Width for line breaksaltimg ?? Nonealtimg-width ?? Width of altimagealtimg-height ?? Height of altimagealtimg-valign ?? 0exalttext ?? nonecdgroup ?? noneV 0.65: Public Draft 20130912 115

Item Encoding and BehaviorPARCC Item Development Technical GuideCode Listing 5.3 illustrates an example of MathML markup of the quadratic formula [MathML: §1.4].010203040506070809101112131415161718192021222324252627282930313233343536Code Listing 5.4: MathML Examplex=-b&#xB1;b2-4&#x2062;a&#x2062;c2&#x2062;a Example Validated: 20130614 Firefox 21.0XML: Rendering: PARCC APIP Item FragmentsItem fragments [QTI Info 2.1: § 16] may be used throughout an item where permitted by QTI if the item contentdoes not include an interactive element, i.e., static content. PARCC practice is that all interactive elements must beencoded inline in XML in the item and not in an item fragment. For example, a shared stimulus passage withinteractive content would be encoded inline, while a passage without interactive content should be encoded as arubric block in a separate resource file.Shared items without interactions can be created, encoded and packaged as separate resources (with correspondingasset-level metadata ). These shared item fragments are included in the item through XInclude [XInclude]. Item116 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior fragments are treated as XML and the xinclude element should include the parse="xml" attribute and should notinclude an xpointer attribute, i.e., the included file must contain only a single fragment as a complete XMLdocument. All other attributes may be used. Item fragments should not be nested, e.g., a fragment should notinclude a reference to another nested fragment.Code listing 5.5 illustrates an item fragment.Code Listing 5.5: Item Fragment Example01020304Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Line 02: Namespace declaration for XInclude Line 03: Include reference to the file something.xml as if the file is media type application/xmlNote: Add item fragment / XInclude example.PARCC APIP QTI Rubric BlocksPARCC items may use all features of Rubric Blocks [QTI Info 2.1: § 6.4] except template elements. A summary ofthe rubric block element follows. The summary follows using the same format used to describe the APIPinteractions elements.Element rubricBlockDefinition Instructions for an item.Type APIP QTI [QTI Info 2.1: § 6.4]Interactions In any itemBodyAttributes Attribute Type Value Default Notes id identifier any none class string any none See list of PARCC classes use string any none view view any none One block per view valueElements Element Number Order NotesXHTMLNotesAn interaction may not be contained within the rubric block.There should be only one instance of a rubric block for each value of view.V 0.65: Public Draft 20130912 117

Item Encoding and BehaviorPARCC Item Development Technical GuidePARCC APIP QTI Response ProcessingItem descriptions include: response variables (responseDeclaration element) [QTI Info 2.1: § 5.1] outcome variables (outcomeDeclaration element) [QTI Info 2.1: § 5.2] response processing instructions (responseProcessing element) [QTI Info 2.1: § 8] All PARCC items must include declarations of both response variables and outcome variables. Any machine gradeditem must include response processing instructions. Human graded items must not include any response processinginstructions. The inclusion/exclusion of response processing instructions must be consistent with the Scoring Modemetadata element.PARCC items may any of the QTI features for response and outcome variables. A summary of theresponseDeclaration and outcomeDeclaration elements and response-specific subelements follows. Elements usedwith PARCC response processing include: responseDeclaration [QTI Info 2.1: § 5.1] outcomeDeclaration [QTI Info 2.1: § 5.2] areaMapEntry [QTI Info 2.1: § 5.1] areaMapping [QTI Info 2.1: § 5.1] correctResponse [QTI Info 2.1: § 5.1] defaultValue [QTI Info 2.1: § 5] interpolationTable [QTI Info 2.1: § 5.2] interpolationTableEntry [QTI Info 2.1: § 5.2] mapEntry [QTI Info 2.1: § 5] mapping [QTI Info 2.1: § 5] matchTable [QTI Info 2.1: §5.2] matchTableEntry [QTI Info 2.1: §5.2] value [QTI Info 2.1: § 5]Any response processing element not listed is permitted unless formally excluded elsewhere.Summaries follow using the same format used to describe the APIP interactions elements.118 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Element responseDeclarationDefinition The definition of a response variable.Type APIP QTI [QTI Info 2.1: § 5.1]Container In any itemBodyAttributes Attribute Type Value Default Notes identifier identifier any none Matches interaction cardinality cardinality any none baseType baseType any noneElementsElement Number Order Notes(ordered) defaultValueSee element details correctResponseSee element details mappingSee element details areaMappingSee element detailsNotesElement outcomeDeclarationDefinition The definition of an outcome variable.Type APIP QTI [QTI Info 2.1: § 5.2]Container In any itemBodyAttributes Attribute Type Value Default Notes identifier identifier any none Matches interaction cardinality cardinality any none baseType baseType any none view view any none interpretation string any none longInterpretation url any none normalMaximum double any none QTI is float normalMinimum double any none QTI is float masteryValue double any none QTI is floatElements Element Number Order Notes(ordered) matchTable Contains either a interpolationTablematchTable or aninterpolationTableNotesElement areaMapEntryDefinition The definition of an area.Type APIP QTI [QTI Info 2.1: § 5.1]Container responseDeclaration.areaMappingAttributes Attribute Type Value Default Notes shape shape any none coords coords any none string of values mappedValue double any none QTI is floatElementsElement Number Order Notes(ordered)NoneNotesV 0.65: Public Draft 20130912 119

Item Encoding and BehaviorPARCC Item Development Technical GuideElement areaMappingDefinition The definition of an area.Type APIP QTI [QTI Info 2.1: § 5.1]Container responseDeclarationAttributes Attribute Type Value Default Notes lowerBound double any none QTI is float upperBound double any none QTI is float defaultValue double any 0 QTI is , floatElementsElement Number Order Notes(ordered) areaMapEntry [1..*] ordered See element detailsNotesElement correctResponseDefinition The definition of a correct response(s) for an interaction.Type APIP QTI [QTI Info 2.1: § 5.1]Container responseDeclarationAttributes Attribute Type Value Default Notes interpretation string any noneElementsElement Number Order Notes(ordered) value [1..*] ordered Ordered only whencardinality is orderedSee element detailsNotesElement defaultValueDefinition The definition of a default value response(s) for an interaction.Type APIP QTI [QTI Info 2.1: § 5]Container responseDeclarationAttributes Attribute Type Value Default Notes interpretation string any noneElementsElement Number Order Notes(ordered) value [1..*] ordered Ordered only whencardinality is orderedSee element detailsNotesElement interpolationTableDefinition The definition of mapping of outcome values.Type APIP QTI [QTI Info 2.1: § 5.2]Container outcomeDeclarationAttributes Attribute Type Value Default Notes defaultValue string any NULLElementsElement Number Order Notes(ordered) interpolationTableEntry [1..*] ordered See element detailsNotes120 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Element interpolationTableEntryDefinition The definition of mapping of outcome values.Type APIP QTI [QTI Info 2.1: § 5.2]Container outcomeDeclarationAttributes Attribute Type Value Default Notes sourceValue double any none QTI is float includeBoundary boolean any true targetValue string any none QTI type is valueTypeElementsElement Number Order Notes(ordered)NoneNotesElement mapEntryDefinition The definition of an area.Type APIP QTI [QTI Info 2.1: § 5]Container responseDeclaration.mappingAttributes Attribute Type Value Default Notes mapKey string any none mappedValue double any none QTI is float caseSensitive boolean any noneElementsElement Number Order Notes(ordered)NoneNotesElement mappingDefinition The definition of an area.Type APIP QTI [QTI Info 2.1: § 5]Container responseDeclarationAttributes Attribute Type Value Default Notes lowerBound double any none QTI is float upperBound double any none QTI is float defaultValue double any 0 QTI is , floatElementsElement Number Order Notes(ordered) areaMapEntry [1..*] ordered See element detailsNotesElement matchTableDefinition The definition of matching of outcome values.Type APIP QTI [QTI Info 2.1: § 5.2]Container outcomeDeclarationAttributes Attribute Type Value Default Notes defaultValue string any NULLElementsElement Number Order Notes(ordered) matchTableEntry [1..*] ordered See element detailsNotesV 0.65: Public Draft 20130912 121

Item Encoding and BehaviorPARCC Item Development Technical GuideElement matchTableEntryDefinition The definition of matching of outcome values.Type APIP QTI [QTI Info 2.1: § 5.2]Container outcomeDeclarationAttributes Attribute Type Value Default Notes sourceValue integer any none QTI is float targetValue string any none QTI type is valueTypeElementsElement Number Order Notes(ordered)NoneNotesElement valueDefinition The definition of a value.Type APIP QTI [QTI Info 2.1: § 5]Container responseDeclaration.defaultValue, responseDeclaration.correctResponse,outcomeDeclaration.defaultValueAttributes Attribute Type Value Default Notes fieldIdentifier identifier any none baseType baseType any noneElementsElement Number Order Notes(ordered)NoneNotesElement contains the value of corresponding base typePARCC items should use one of the available response processing templates instead of inline response processinginstructions.Items should not use custom response processing with an item-specific customOperator [QTI Info 2.1: § 15.3].PARCC-specific custom operators are described below. If none of the available custom operators are suitable, anew custom operator may be created, documented and submitted to PARCC to be included in the set of PARCCspecificcustom operators. This Guide does not currently describe how to submit a new custom operator forinclusion in the PARCC Custom Operator set.If none of available templates are suitable, a new response template may be created, documented and submitted toPARCC to be included in the library of response processing templates. This Guide does not currently describe howto submit a new template for inclusion in the PARCC Response Template Library.The template is referenced in the item through the responseProcessing element with the template attributereferencing the full name of the template. For a standard QTI or PARCC template, the templateLocation attributeshould be omitted.Until the template is added to the PARCC Response Template Library, the template should be included with theitem as a resource in the content package. The item responseProcessing element should include both the templateattribute (indicating the template name) and templateLocation attribute (indicating the location of the templatewithin the package folder structure). The template should be stored in the template-specific folder within the toplevelrptemplates folder in the package.Within the package manifest, metadata for the template resource is required. The following LOM [LOM 2002]metadata elements must be provided (any other LOM metadata element may be included): Entity ID: The developer’s unique identifier assigned to the template (LOM General.identifier) Author: The developer’s name (LOM General.contributor) Title: The title of the template, including the version (LOM General.title)122 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Description: A narrative description of the template (LOM General.description) Version: The version number of the template (LOM LifeCycle.version) Status: The status of the template version (LOM LifeCycle.status with LOMv1.0 vocabulary values of draftor final) MIME Type: Must be the value application/xml (LOM Technical.format)PARCC may augment this metadata with additional information when the template is stored in the PARCCResponse Template Library.For PARCC templates, the title should include the name of the template concatenated with the version via a period(.), e.g., xyztemplate.1.0. The name should be the same as the name of the file holding the template XMLdocument. Any substantial (non editorial) change in a template requires a new version and title to ensure that thechange does not impact any items that use the template.Available templates are listed in Table 5.8.Table 5.8: Response Processing TemplatesTemplate Template Name TypeMatch Correct match_correct Standard QTI templateMap Response map_response Standard QTI templateMap Response Point map_response_point Standard QTI templatePARCC templateIndividual response processing templates are described below. For each: Description: A narrative description of the template. Location: The location of the template XML document. If the template has not been stored in the PARCCResponse Template Library, use “Package Manifest Folder: rptemplates/.xml”, substituting the titleof the template (including the concatenated version) for . Metadata: The values for the template Title, ID, Version, and Status elements. Variables: The list of variables used in the template. For each, its type, ID/name, acceptable cardinality,acceptable baseType. Usage Guidance: Specific notes about use of the template. Example XML: An illustrative example of the XML for an item using the response processing template. XML Validation: Validated (), partially validated—no known issues (), invalid or not validated ().Includes details on XML, Schema, Rendering, Behavior, Response Processing and Accessibility validation.No validation has been performed for Behavior, Response Processing and Accessibility. Example Description: A description of the example.The full XML for each of the response processing templates is included in the QTI Response Processing TemplatesAnnex.V 0.65: Public Draft 20130912 123

Item Encoding and BehaviorPARCC Item Development Technical GuideMatch Correct Response Processing TemplateDescription The template uses the match operator [QTI Info 2.1: § 15.3] to match the value of a responsevariable RESPONSE to its correct value. A response variable named RESPONSE must have beendeclared and have the correct value. The template sets the value of the declared outcomevariable SCORE to either 0.0 (incorrect) or 1.0 (correct). If no RESPONSE is given, the templatesets the value of SCORE to 0.0.Location http://www.imsglobal.org/question/qtiv2p1/rptemplates/match_correct.xmlMetadata Element ValueTitlematch_correctIDDeveloperIMSVersion 1.0StatusfinalMIME Typeapplication/xmlVariables Type ID Cardinality baseTyperesponseDeclaration RESPONSE any integer, boolean, string, pair,directedPair, point, file,duration, URI, identifier,intOrIdentifieroutcomeDeclaration SCORE single FloatUsage GuidanceExampleXML000102030405060708091011121314151617181920212223242526ChoiceA0Pick the right answer.This is the correct answer.This might be the correct answer.I don't know the correct answer.Example Validated: 20130614 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: 124 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Match Correct Response Processing TemplateExampleRenderingExampleDescriptionThe example shows a choice interaction that uses the match correct response processingtemplate.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-10: Response variable RESPONSE definitiono Lines 07-09: Value for correctResponse Lines 11-15: Outcome variable SCORE definitiono Lines 12-14: Default value for SCORE Lines 16-23: The itemBody as a choiceInteraction Lines 21-22: Declaration for the match_correct response processing templateV 0.65: Public Draft 20130912 125

Item Encoding and BehaviorPARCC Item Development Technical GuideMap Response Response Processing TemplateDescription The template uses the mapResponse operator [QTI Info 2.1: § 15.1] to map the value of aresponse variable RESPONSE to a value for the declared outcome variable SCORE of type float.A response variable named RESPONSE must have an associated mapping [QTI Info 2.1: § 5]. IfRESPONSE is NULL, the template sets the value of SCORE to 0.0.Location http://www.imsglobal.org/question/qtiv2p1/rptemplates/map_response.xmlMetadata Element ValueTitlemap_responseIDDeveloperIMSVersion 1.0StatusfinalMIME Typeapplication/xmlVariables Type ID Cardinality baseTyperesponseDeclaration RESPONSE any integer, boolean, float, string,pair, directedPair, point, file,duration, URI, identifier,intOrIdentifieroutcomeDeclaration SCORE single FloatUsage GuidanceExampleXML0001020304050607080910111213141516171819202122232425262728293031HCHydrocarbons are composed of which of the following elements?HydrogenHeliumCarbonOxygenNitrogenSiliconExample Validated: 20130614 QTIWorks 1.0-M4 (QTI, not APIP)XML: QTI Schema: Rendering: Behavior: Response: Accessibility: 126 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideItem Encoding and Behavior Map Response Response Processing TemplateExampleRenderingExampleDescriptionThe example shows a choice interaction that uses the map response response processingtemplate.In the example: Lines 00-05: The assessmentItem definition and its attributes Lines 06-16: Response variable RESPONSE definitiono Lines 07-10: Values for correctResponseo Lines 11-15: The value mappings Line 17: Outcome variable SCORE definition Lines 18-28: The itemBody as a choiceInteraction Lines 29-30: Declaration for the map_response response processing templateV 0.65: Public Draft 20130912 127

Item Encoding and BehaviorPARCC Item Development Technical GuideMap Response Point Response Processing TemplateDescription The template uses the mapResponsePoint operator [QTI Info 2.1: § 15.3] to map the value of aresponse variable RESPONSE to a value for the declared outcome variable SCORE of type float.A response variable named RESPONSE must be of baseType point [QTI Info 2.1: § 5]. IfRESPONSE is NULL, the template sets the value of SCORE to 0.0.Location http://www.imsglobal.org/question/qtiv2p1/rptemplates/map_response_point.xmlMetadata Element ValueTitlemap_response_pointIDDeveloperIMSVersion 1.0StatusfinalMIME Typeapplication/xmlVariables Type ID Cardinality baseTyperesponseDeclaration RESPONSE any pointoutcomeDeclaration SCORE single FloatUsage GuidanceExampleXML0001020304050607080910111213141516171819202122232450 50Pick the center of the lower-left quadrant.

PARCC Item Development Technical GuideItem Encoding and Behavior Map Response Point Response Processing TemplateExampleRenderingExampleDescriptionThe example shows a select point interaction that uses the map response point responseprocessing template.In the example: Lines 00-06: The assessmentItem definition and its attributes Lines 07-14: Response variable RESPONSE definitiono Lines 08-10: Value for correctResponseo Lines 11-13: The value mapping area Line 15: Outcome variable SCORE definition Lines 16-21: The itemBody as a selectPointInteraction Lines 22-23: Declaration for the map_response_point response processing templateV 0.65: Public Draft 20130912 129

Item Encoding and BehaviorPARCC Item Development Technical GuidePARCC Response Processing Custom OperatorsFuture Guide Version: Provide list of all PARCC response processing custom operators.Item TemplatesPARCC items may not use Item Templates [QTI Info 2.1: § 10].Modal FeedbackPARCC items may not use Modal Feedback [QTI Info 2.1: § 9].Adaptive ItemsAll PARCC items are non adaptive.Time Dependent ItemsAll PARCC items are time independent.LTI-Based Items and ResourcePARCC has not developed guidelines for using Leaning Tool Interoperability (LTI resources) [LTI, CCImplementation: § 4.8] in items.Future Guide Version: Provide LTI guidelines.130 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata To aid in the discovery of items and assets, and in the management and exchange of sections, tests and the packages,metadata must be associated with each of these entities.The metadata guidelines describe the metadata elements used for an: Item Asset Section Test Package ManifestThe description of each metadata element includes: Metadata usage for the element Allowable valid values or the controlled vocabulary entries for the element XML representation of the metadata element Sample XML encoding of the metadata element in a content packageAdditional guidelines address file and accessibility metadata and encoding metadata in manifests and packages.Metadata for all items, assets, sections, tests and packages must conform to all of the Metadata guidelines. Unlessotherwise noted, all XML documents must use the RTTA APIP Profile Schemata specified in the Schemata Annex.Item-Level MetadataItem-level metadata describe an individual item. RTTA and PARCC-specific metadata attributes for an item areshown in Table 6.1. The metadata values are encoded in the metadata associated with a resource in the manifest .The main resource will reference the APIP/QTI item in the XML document and it will have a number ofdependencies that each reference/link to an asset for the item, e.g., media resources (including alternative mediaobject), stylesheets, templates, each of which is described with asset-level metadata.Asset-Level MetadataItem asset-level metadata describe the various properties of a media resource (file) that is associated with an item.RTTA and PARCC-specific metadata attributes for an asset are shown in Table 6.1.Section-, Test- and Manifest-Level MetadataSection-, test- and package-level metadata describe a section (resources that reference/link to an APIP/QTI section),test (resources that reference/link to an APIP/QTI test XML document), or the manifest (metadata attributes thatdescribe the manifest as a whole and are placed at the top of the manifest) respectively. Required elements are takendirectly from the APIP 1.0 metadata profile [APIP Tech 1.0: § A9.2]. Metadata attributes for a section, test ormanifest are shown in Table 6.1.V 0.65: Public Draft 20130912 131

MetadataPARCC Item Development Technical GuideMetadata Element SummaryThe core metadata elements are shown in Table 6.1, grouped by major category. Each row indicates if the metadataelement is required (), optional () or should not be used () to describe an item, asset, section, test or manifest.Full details of each metadata element follow the table.Table 6.1: Metadata Element SummaryMetadata Element Item Asset Section Test ManifestAdministrative ElementsEntity ID Title Description Author Common Core Subject Grade Level ?? Academic Course ?? ?? Assessment Type ?? Assessment ?? Life Cycle ElementsStatus Status Date Version Description ElementsFile Size PARCC Item Type Response Type Interaction Type Composite Item Technology-Enhanced Item Type Task Type Delivery Mode Estimated Time Required Text Complexity Cognitive Complexity PARCC Performance Level Alignment ElementsCommon Core State Standards ID PARCC Evidence Statement PARCC SubClaim PARCC Task Model Scoring ElementsScoring Mode PARCC Score Points Rights ElementsLicense ID Copyright Media ElementsMedia Type Package Type MIME Type 132 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata Element Item Asset Section Test ManifestMaster to Version Relation Item to Preview Relation Accessibility ElementsAccessibility Display Feature Excluded Accessibility Display Feature Accessibility Support Feature Excluded Accessibility Support Feature Companion Material In addition to the metadata elements show in Table 6.1, any other LOM metadata element [LOM 2002],Accessibility metadata [Accessibility Metadata], QTI metadata [QTI Metadata 2.1: § 3] or Curriculum standardsmetadata [CC Implementation 1.2: § 4.5.3] may be included in the metadata for the resource or package.Future Guide Version: Describe disposition of other LOM, QTI and CSM elements based on Item Bank behavior,e.g., stored, ignored.Future Guide Version: Describe test form metadata requirements.File MetadataIndividual files in the manifest may also include LOM [LOM 2002] metadata. Except as noted elsewhere, filemetadata is not required, but is recommended for all files. If provided, the following metadata elements should beincluded in the metadata for the file (elements with are highly recommended, elements with a are desirable): Entity ID: The developer’s unique identifier assigned to the file (LOM General.identifier) Title: The title of the file (LOM General.title) Description: A brief description of the file (LOM General.description) Author: The developer’s name (LOM General.contribute) Version: The version number of the file (LOM LifeCycle.version) Status: The status of the file version (LOM LifeCycle.status with LOMv1.0 vocabulary values) MIME Type: The MIME type of the file (LOM Technical.format) License: The license for the file (LOM Rights.description) PARCC may augment this metadata with additional information when the file is stored in the PARCC item bank.Any other LOM metadata elements may be included in the metadata for the file.Future Guide Version: Describe disposition of file metadata based on Item Bank behavior, e.g., stored, ignored.AfA DRD MetadataItem variants [CP Info 1.2: § 6.8] may include Access for All Digital Resource Description metadata [AfA DRD09]. All AfA DRD metadata [AfA DRD 09: § 6.2] may be used with an item variant.Metadata Element DetailsIndividual metadata elements are described below. For each: Use: Details if the metadata element is required (), optional () or should not be used () to describe anitem, asset, section, test or manifest. An asterisk (*) in conjunction with a required indicator (*) impliesthat while the element is required, the item developer may omit the element when transmitting the item toPARCC; PARCC will subsequently add the metadata value.V 0.65: Public Draft 20130912 133

MetadataPARCC Item Development Technical GuideCategory: The PARCC category of metadata element: Administrative, Descriptive, Life Cycle, Alignment,Scoring, Rights, Media, Accessibility. The PARCC category value it is not included in the metadata; thecategory is used only to group metadata elements for presentation.Field: The metadata element name.Field Description: A narrative description of the metadata element.Multiplicity: Is only one value permitted or are multiple values permitted.Valid Values / Controlled Vocabulary: The constraints on the value(s) of the metadata element. For anelement that is not from a controlled vocabulary, the type of value is indicated. For a controlledvocabulary, the vocabulary source (e.g., PARCC, LOM [LOM 2002], CEDS [CEDS 3.0]) is indicated. Ifthere are two columns for a controlled vocabulary, the first column is the vocabulary value and the secondcolumn is a narrative description of the vocabulary item.Usage Guidance: Informative notes on creating an instance of the metadata element.Binding: How to bind the metadata value to an XML element in a manifest.Example XML: An illustrative example of the XML for the metadata.o The example indicates the type of metadata – manifest or resource. When the metadata binding isdifferent or confusing between the manifest or resourc, there are two examples. When themetadata binding is the same, only one example is show – the metadata for the other use is similarwith a different namespace. In all cases the example is labeled as [manifest] or [resource] toindicate the alternative shown.o In the examples, the namespace prefixes refer to the following specifications:• lomr – the IMS APIP 1.0 entry profile [APIP Tech 1.0: § A9.1] of the IEEE LearningObject Metadata standard [LOM 2002] for use at resource level.• lomm – the IMS APIP 1.0 entry profile [APIP Tech 1.0: § A9.2] of the IEEE LearningObject Metadata standard [LOM 2002] for use at manifest level.• ccmd – IMS Common Cartridge 1.2 curriculum standards specification [APIP Tech 1.0: §A9.4] of Common Cartridge [CC Implementation 1.2: § 4.5.3].• qtim – the APIP 1.0 entry profile of the IMS QTI 2.1 profile [APIP Tech 1.0: § A9.3] ofthe IEEE Learning Object Metadata standard [LOM 2002] for use with QTI resources.• afamd – the RTTA accessibility metadata schema [Accessibility Metadata].XML Validation: Validated (), partially validated—no known issues (), invalid or not validated ().Includes details on XML, Schema, Rendering, Behavior, Response Processing and Accessibility validation.Note: The namespace prefixes descriptions will change when the RTTA APIP profile is completed to reference theRTTA profile.Note: PARCC XML documents using the XML binding will not validate against the current APIP Profile.134 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementEntity IDUse Item Asset Section Test Manifest CategoryAdministrativeFieldEntity IDField DescriptionUnique identifier as it exists in the developer’s authoring system.MultiplicityMultiple values permittedThe APIP Profile only permits a single valueValid Values /Controlled VocabularyCatalog: Character string (ISO/IEC 10646-1:2000 [UCS])Entry: Character string (ISO/IEC 10646-1:2000 [UCS])Usage GuidanceThe developer's ID will be used during development. Additional PARCC IDs willbe assigned to items and assets upon import into the PARCC Item Bank.One of the IDs must match the identifier attribute of the assessmentItem.The catalog value is optional. It should represent the developer’s name orcataloguing system. Catalog element and value will be added by PARCC if notprovided by the developer.BindingIEEE LOM General.identifier element in the manifest.ExampleXML[resource]01020304050607080910111213141516...............Developer NameVE_IP_02...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 135

MetadataPARCC Item Development Technical GuideMetadata ElementTitleUse Item Asset Section Test Manifest* CategoryAdministrativeFieldTitleField DescriptionTitle of the item, asset, section, test or manifest.MultiplicitySingle value onlyValid Values /LOM Language string.Controlled Vocabulary The language of the title (optional) as a character string (ISO/IEC 10646-1:2000 [UCS]) The title as a character string (ISO/IEC 10646-1:2000 [UCS])Usage GuidanceTitle element and value will be added by PARCC if not provided by the developer.The title value should match the title attribute of the assessmentItem.The language value comes from RFC 5646 [Lang Tag]. If the language value isnot provided, the value is defined in the Meta-Metadata.language element. If thiselement is not present, the language is assumed to be en-US and will be added byPARCC if not provided by the developer. This default language overrides theIEEE LOM specification that the language is undefined.BindingItem, Asset: IEEE LOM General.title element in the resource section of themanifest.Section, Test, Manifest: IEEE LOM General.title element in the manifest.ExampleXMLItem, Asset[resource]ExampleXMLSection, Test, Manifest[manifest]0102030405060708091011121314150102030405060708091011..................Text to speech recording…............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: .........PARCC example test package.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 136 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementDescriptionUse Item Asset Section Test Manifest* * CategoryAdministrativeFieldDescriptionField DescriptionA human readable description of the item, asset, section, test or manifest.MultiplicityMultiple values permittedValid Values /LOM Language string.Controlled Vocabulary The language of the description (optional) as a character string (ISO/IEC10646-1:2000 [UCS]) The description as a character string (ISO/IEC 10646-1:2000 [UCS])Usage GuidanceDescription element and value will be added by PARCC if not provided by thedeveloper. The description is optional for sections.The language value comes from RFC 5646 [Lang Tag]. If the language value isnot provided, the value is defined in the Meta-Metadata.language element. If thiselement is not present, the language is assumed to be en-US and will be added byPARCC if not provided by the developer. This default language overrides theIEEE LOM specification that the language is undefined.BindingItem, Asset: IEEE LOM General.description element in the resource section of themanifest.Section, Test, Manifest: IEEE LOM General.description element in the manifest.ExampleXMLItem, Asset[resource]ExampleXMLSection, Test, Manifest[manifest]010203040506070809101112131415010203040506070809101112..................An illustrative test item…............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: .........An illustrative package that includes one test, one section and twoitems.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 137

MetadataPARCC Item Development Technical GuideMetadata ElementAuthorUse Item Asset Section Test Manifest CategoryAdministrativeFieldAuthorField DescriptionThe entity responsible for creating the item, asset, section, test or manifest.MultiplicityMultiple values permitted for an item, asset, section or testSingle value only for a manifestValid Values /Controlled VocabularyRole: LOM Contribute.role vocabulary [LOM 2002]authorEntity: vCARD [VCARD, VCARD Profile]Usage GuidanceDuring development, the author’s identity should be used. Once submitted andapproved by PARCC, the value will be PARCC.BindingIEEE LOM Contribute element in the manifest.ExampleXML[manifest]01020304050607080910............authorBEGIN:VCARD\nORG:PARCC\nEND:VCARD\n......Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 138 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementCommon Core SubjectUse Item Asset Section Test Manifest CategoryAdministrativeFieldCommon Core SubjectField DescriptionSubject area being assessed as defined by the Common Core State Standards.MultiplicitySingle value onlyValid Values /Curriculum Standards Metadata [CC Implementation 1.2: § 4.5.3]Controlled Vocabulary Provider Label URIMetadata providerID Value: CCSSOCommon Core Subject Label Vocabulary: Source CCSSOMathematicsEnglish Language Arts - LiteracyCommon Core URI Vocabulary: Source CCSSOhttp://www.corestandards.org/math.xmlhttp://www.corestandards.org/ELA-Literacy.xmlUsage GuidanceAlthough the Subject field should generally align to the instructional context,PARCC is defining Common Core Subject since the Common Core defines therelationship of assessment item to the subjects being assessed.BindingCommon Core derived identifiers in IMS Common Cartridge CurriculumStandards Metadata structures in the manifest.The RTTA binding requires both a human readable label and a URI. The label isoptional in APIP.ExampleXML[resource]010203040506070809101112131415161718............English Language Arts - Literacyhttp://www.corestandards.org/ELA-Literacy.xml....................Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 139

MetadataPARCC Item Development Technical GuideMetadata ElementGrade LevelUse Item Asset Section Test Manifest *?? ?? CategoryAdministrativeFieldGrade LevelField DescriptionGrade level or grade level range at which the item is assessing the knowledge andskills as defined by the Common Core State Standards.MultiplicityMultiple values permittedValid Values /Grade Level Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptionKGKindergarten01 First Grade02 Second Grade03 Third Grade04 Fourth Grade05 Fifth Grade06 Sixth Grade07 Seventh Grade08 Eight Grade09 Ninth Grade10 Tenth Grade11 Eleventh Grade12 Twelfth GradeHS High School (09-12)Usage GuidanceRecommended practice for PARCC items is to use a single grade level or multiplegrade level elements for all ELA and for Math through 8th grade. Math itemsbeyond the middle school level should be assigned “High School” as the gradelevel rather than a single grade level or a list of multiple grade levels.BindingIEEE LOM Educational.context element in the manifest with RTTAv1.0 as thevalue of taxon source in the manifest.ExampleXML[resource]0102030405060708091011121314151617181920..................RTTAv1.0KGRTTAv1.001............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 140 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementAcademic CourseUse Item Asset Section Test Manifest ?? ?? CategoryAdministrativeFieldAcademic CourseField DescriptionEquivalent academic course for which the assessment item content is generallyaddressed.MultiplicityMultiple values permittedValid Values /Controlled VocabularyAcademic Course Vocabulary: Source RTTAAlgebra 1Algebra 2GeometryMath 1Math 2Math 3Not ApplicableUsage GuidanceCurrently in PARCC, the course distinction is only applicable to Mathematics. Use Not Applicable for an ELA-Literacy item. Do not use Not Applicable for a Mathematics item.BindingIEEE LOM Classification element in the manifest with AcademicCourse as thevalue of taxon source in the manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............AcademicCourseMath 1...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 141

MetadataPARCC Item Development Technical GuideMetadata ElementAssessment TypeUse Item Asset Section Test Manifest ?? CategoryAdministrativeFieldAssessment TypeField DescriptionHigh-level definition of the assessment type for which the item is intended,reflecting the purpose of the assessment and how the resulting data will be used.MultiplicityMultiple values permittedValid Values /Controlled VocabularyAssessment Type Vocabulary: Source RTTASummativeNon-SummativeDiagnosticMid-YearPerformance AssessmentUsage GuidanceDefine based on PARCC usage context.BindingIEEE LOM Classification element in the manifest with Assessment Type as thevalue of taxon source in the manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............Assessment TypePerformance Assessment...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 142 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementAssessmentUse Item Asset Section Test Manifest ?? CategoryAdministrativeFieldAssessmentField DescriptionPARCC Assessment for which the item was designed/intended.MultiplicityMultiple values permittedValid Values /Controlled VocabularyRTTA Assessment Vocabulary: Source RTTAEnd of YearPerformance BasedMid-YearNarrative WritingResearch SimulationSpeaking and ListeningLiterary AnalysisDiagnosticUsage GuidanceDefine based on PARCC usage context.BindingIEEE LOM Classification element with Assessment as the value of taxon source inthe manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............AssessmentDiagnostic...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 143

MetadataPARCC Item Development Technical GuideMetadata ElementStatusUse Item Asset Section Test Manifest CategoryLife CycleFieldStatusField DescriptionThe status or the condition of the item, asset, section, test or manifest indevelopment or deployment.MultiplicitySingle value onlyValid Values /Controlled VocabularyStatus Vocabulary: Source RTTAIn DevelopmentIn ReviewRejectedApproved for Field TestApproved for OperationalDeployed to OperationalReleasedUsage GuidanceThe controlled vocabulary set provides terms for the complete entity Life Cycle.However, developers will not need to utilize all the available terms. Developersshould update the Status field at each step of the item's life cycle.BindingIEEE LOM LifeCycle.status element with RTTAv1.0 as the value of vocabularysource in the manifest.ExampleXML[resource]01020304050607080910111213141516...............RTTAv1.0In Development...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 144 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementStatus DateUse Item Asset Section Test Manifest *?? CategoryLife CycleFieldStatus DateField DescriptionDate associated with the most recent status assignment.MultiplicitySingle value onlyValid Values /Subset of LOM Datetime [LOM 2002]. Provide only the date, not a time of day.Controlled VocabularyUsage GuidanceWhen the value of the Status field changes, the Status Date field should beupdated accordingly. Only the most recent date is recorded.Format for Status Date is YYYY-MM-DDBinding IEEE LOM LifeCycle.contribute.date element. The value is an xsd:date [XSD 2](timezone is omitted).ExampleXML[resource]0102030405060708091011121314151617...............2013-10-26............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 145

MetadataPARCC Item Development Technical GuideMetadata ElementVersionUse Item Asset Section Test Manifest* * CategoryLife CycleFieldVersionField DescriptionItem, asset, section, test or manifest version label.MultiplicitySingle value onlyValid Values /A maximum of three non negative integers separated by periods.Controlled VocabularyUsage GuidanceA locally assigned value is acceptable until formal submission. After submission aPARCC defined version number will be assigned.Once an item or asset is “approved”, any change requires a new version number.BindingIEEE LOM LifeCycle.version element in the manifest.ExampleXML[manifest]0102030405060708091011.........1.0.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 146 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementFile SizeUse Item Asset Section Test Manifest CategoryDescriptionFieldFile SizeField DescriptionItem: File size range including associated assets, in bytes (octets) for an item.Asset: File size in bytes (octets) for an asset.MultiplicitySingle value onlyValid Values /Non negative integer.Controlled VocabularyUsage GuidanceUsed to estimate form size for an item. Use the size of the assets to be deliveredto the student. Archive versions of assets, such as high definition video referencefiles from which lower resolution versions are derived for use with an item, shouldnot be included in file size totals.BindingIEEE LOM Technical.size element in the manifest.ExampleXML[resource]01020304050607080910111213...............18445............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 147

MetadataPARCC Item Development Technical GuideMetadata ElementPARCC Item TypeUse Item Asset Section Test Manifest CategoryDescriptionFieldPARCC Item TypeField DescriptionHigh-level definition of the item type as referenced in the PARCC assessmentdevelopment blueprints.MultiplicityMultiple values permittedValid Values /Controlled VocabularyPARCC Item Type Vocabulary: Source PARCCReading - EBSRReading - TECRELA - PCRMath - Type IMath - Type IIMath - Type IIIUsage GuidanceBindingIEEE LOM Classification element with ItemType as the value of taxon source inthe manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............ItemTypeReading - TECR...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 148 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementResponse TypeUse Item Asset Section Test Manifest CategoryDescriptionFieldResponse TypeField DescriptionThe nature of the question framed as the type of response the test-taker isprompted to provide.MultiplicityMultiple values permittedValid Values /Assessment Item Type Vocabulary: Source CEDS [CEDS 3.0]Controlled Vocabulary Vocabulary ValueDescriptionMultipleChoiceMultiple-choiceFillInTheBlankFill-in-the-BlankTrueFalseTrue/FalseEssayEssayMatchingMatchingShortAnswerShort answerLabelingLabelingVisualRepresentationVisual representationShowYourWorkShow your workOtherConstructedResponse Other constructed responsePerformanceTaskPerformance taskOtherExtendedResponse Other extended responseInnovativeInnovativeReorderingReorderingSubstitutionSubstitutionOtherOtherUsage GuidanceThe response type value is defined by the Assessment Item Type field as definedby the CEDS interoperability standards [CEDS 3.0].BindingIEEE LOM Classification element with ResponseType as the value of taxon sourcein the manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............ResponseTypeMatching...............V 0.65: Public Draft 20130912 149

MetadataPARCC Item Development Technical GuideMetadata ElementResponse TypeExample Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 150 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementInteraction TypeUse Item Asset Section Test Manifest CategoryDescriptionFieldInteraction TypeField DescriptionDefinition for the nature of the test taker interaction with the item.MultiplicityMultiple values permittedValid Values /Controlled VocabularyAssessment Interaction Type Vocabulary: Source APIP [APIP Tech 1.0] and CEDS[CEDS 3.0]Vocabulary ValueDescriptioncustomInteractionCustom InteractiondrawingInteractionDrawing InteractiongapMatchInteractionGap Match InteractionmatchInteractionMatch InteractiongraphicGapMatchInteraction Graphic Gap Match InteractionhotspotInteractionHotspot InteractiongraphicOrderInteraction Graphic Order InteractionselectionPointInteraction Select Point InteractiongraphicAssociateInteraction Graphic Associate InteractionsliderInteractionSlider InteractionchoiceInteractionChoice InteractioninlineChoiceInteraction Inline Choice InteractionmediaInteractionMedia InteractionhottextInteractionHottext InteractionorderInteractionOrder InteractionpositionObjectInteraction Position Object InteractionextendedTextInteraction Extended Text InteractiontextEntryInteractionText Entry InteractionuploadInteractionUpload InteractionassociateInteractionAssociate InteractionUsage GuidanceThe interaction type vocabulary is defined by the QTI interactionType. The Interaction Type vocabulary terms (InlineChoiceInteraction,TextEntryInteraction) are defined in the APIP binding but not in APIP[APIP Tech 1.0] APIP [APIP Tech 1.0] uses positionObjectStage, the binding usespositionObjectInteraction.The vocabulary is partially standardized in CEDS: Terms sliderInteraction and selectionPointInteraction are not included inCEDS.Values may overlap with the PARCC-defined terms for equivalent interactionsassigned as the Technology-Enhanced Item Type.BindingIMS QTI Metadata interactionType element in the manifest. The field spellingsare constrained by the XSD [APIP Tech 1.0: § A2.2].The IMS APIP binding omits mediaInteraction.The binding contains an error, it uses selectionPointInteraction instead ofselectPointInteraction. The XSD value is used to avoid changing the XSD.positionObjectInteraction is the name of the QTI interaction type,which is part ofpositionObjectStage.The vocabulary use lower camel case; CEDS 3.0 uses upper camel case.V 0.65: Public Draft 20130912 151

MetadataPARCC Item Development Technical GuideMetadata ElementExampleXML[resource]0102030405060708091011Interaction Type............choiceInteraction.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 152 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementComposite ItemUse Item Asset Section Test Manifest CategoryDescriptionFieldComposite ItemField DescriptionDefines if the item is composite or simple.MultiplicitySingle value onlyValid Values /Controlled VocabularyBoolean value: xsd:boolean [XSD 2]truefalse10Usage GuidanceBindingExampleXML[resource]0102030405060708091011A composite element contains more than one interaction. This element indicates ifthe item is a composite item or a simple (non composite) element. Default value ifthe element is omitted that the item is simple (false). The element must be presentfor all composite items.IMS QTI Metadata composite element in the manifest. The field value forms aredefined by the XSD.............false.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 153

MetadataPARCC Item Development Technical GuideMetadata ElementTechnology-Enhanced Item TypeUse Item Asset Section Test Manifest CategoryDescriptionFieldTechnology-Enhanced Item TypeField DescriptionDefinition of technology-enhanced functionalities of the item, using notation fromthe PARCC Technology-Enhanced Item Definitions [PARCC TEI].MultiplicityMultiple values permittedValid Values /Technology-Enhanced Item Type Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptionSelectedResponseSelected Response (MC)GriddedResponseGridded Response (GR)MultipleSelectMultiple Select (MS)ConstructedResponseConstructed Response (CR/PCR)ConstructedResponseEquationEditor Constructed Response with EquationEditorFillInTheBlankSpecificCharacterSet Fill in the Blank (FIB) -Specificcharacter setFillInTheBlankUnconstrainedCharacterSet Fill in the Blank (FIB) -unconstrainedcharactersFillInTheBlankEquationEditorFIB with Equation EditorDragandDropDrag and Drop (DD)HotSpotHot Spot (HS)MultipleChoiceTechnologyEnhanced Non TE response with TEfunctionality (MCTE)InlineChoiceInline Choice (IC)/Drop downComplexDragandDropComplex Drag and DropComplexHotSpotComplex Hot SpotTextExtractionText Extraction (EXT)/highlightingLineGraphLine Graph (LG)BarGraphBar Graph (BG)FractionModelFraction ModelTextFlaggingText FlaggingTextAnnotationText AnnotationItemSpecificWidgetItem-Specific WidgetsFunctionGraphFunction Graph (FG)InteractiveNumberLineInteractive Number line (NL)CompositeGraphComposite Graphs (CMG)CompositeGraphwithShapeComposite Graphs with shapesGeometricTransformationGeometric TransformationsZoomNumberLineZoom Number LineSolutionSetGraphSolution Set graphingPolygonGraphPolygon Graph (PG)ScaleScaleSimulationSimulationsPresentationEditorPresentation EditorWebSearchWeb-searchesFreeFormGraphicOrganizerFree-form Graphic OrganizersUsage Guidance154 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementBindingExampleXML[resource]01020304050607080910111213141516171819202122Technology-Enhanced Item TypeIEEE LOM Classification element with TechnologyEnhancedItemType as the valueof taxon source in the manifest................TechnologyEnhancedItemTypeGraphic Organizer...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 155

MetadataPARCC Item Development Technical GuideMetadata ElementTask TypeUse Item Asset Section Test Manifest CategoryDescriptionFieldTask TypeField DescriptionInformation about the degree of interactivity of the learning object. Interactivityin this context refers to the degree to which the learner can influence the aspect orbehavior of the learning object. Inherently, this scale is meaningful within thecontext of a community of practice.MultiplicitySingle value onlyValid Values /Controlled VocabularyTask Type Vocabulary: Source RTTAResearch Simulation TaskLiterary Analysis TaskNarrative Writing TaskNot ApplicableUsage GuidanceCurrently in PARCC, the Task Types is only applicable to ELA-Literacy. Use NotApplicable for a Mathematics item.BindingIEEE LOM InteractivityType element with RTTAv1.0 as the value of vocabularysource in the manifest.ExampleXML[resource]01020304050607080910111213141516...............RTTAv1.0Research Simulation Task...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 156 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementDelivery ModeUse Item Asset Section Test Manifest CategoryDescriptionFieldDelivery ModeField DescriptionIntended delivery mode as designed for PARCC assessments.MultiplicityMultiple values permittedValid Values /Controlled VocabularyDelivery Mode Vocabulary: Source RTTAComputer Based DeliveryPaper and Pencil DeliveryUsage GuidanceItems can be designated as either Computer Based, Paper and Pencil, or both.BindingIEEE LOM Classification element with DeliveryMode as the value of taxon sourcein the manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............DeliveryModeComputer Based Delivery...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 157

MetadataPARCC Item Development Technical GuideMetadata ElementEstimated Time RequiredUse Item Asset Section Test Manifest CategoryDescriptionFieldEstimated Time RequiredField DescriptionAverage time it might take an average student to complete the tasks.MultiplicitySingle value onlyValid Values /Controlled VocabularyA duration. The format for Estimated Time Required is HH:MM:SS (all partsrequired).Usage GuidanceFor Math: Calculate Estimated Time Required as the PARCC Number of Points(SCORING-2) value multiplied by 2.5 (00:02:30) minutes.FOR ELA-L: Assign Estimated Time Required using the following values. Eachmachine scored ELA-L item is estimated to take 2 (00:02:00) minutes. Each PCRin grade 3 is estimated to take 20 (00:20:00) minutes. Each PCR in grades 4-5 isestimated to take 30 (00:30:00) minutes. Each PCR in grades 6-11 is estimated totake 45 (00:45:00) minutes.BindingIEEE LOM Educational.typicalLearningTime element in the manifest.ExampleXML[resource]010203040506070809101112131415..................00:06:10............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 158 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementText ComplexityUse Item Asset Section Test Manifest CategoryDescriptionFieldText ComplexityField DescriptionRelative difficulty of the text contained within the item and its associated testpassages.MultiplicitySingle value onlyValid Values /Controlled VocabularyLOM Educational.semanticDensity Vocabulary: Source LOM [LOM 2002]very lowlowmediumhighvery highUsage GuidanceOnly low, medium and high should be used.BindingIEEE LOM Educational.semanticDensity element in the manifest.ExampleXML[resource]01020304050607080910111213141516..................LOMv1.0low............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 159

MetadataPARCC Item Development Technical GuideMetadata ElementCognitive ComplexityUse Item Asset Section Test Manifest CategoryDescriptionFieldCognitive ComplexityField DescriptionRelative difficulty of the item for the grade level.MultiplicitySingle value onlyValid Values /Controlled VocabularyCognitive Complexity Vocabulary: Source RTTAvery lowlowmediumhighvery highUsage GuidanceOnly low, medium and high should be used.BindingIEEE LOM Educational.difficulty element with RTTAv1.0 as the vocabulary sourcevalue in the manifest.ExampleXML[resource]01020304050607080910111213141516..................RTTAv1.0high............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 160 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementPARCC Performance LevelUse Item Asset Section Test Manifest CategoryDescriptionFieldPARCC Performance LevelField DescriptionMapping of the item to the PARCC Performance Level Descriptors.MultiplicitySingle value onlyValid Values /Controlled VocabularyPARCC Performance Level Vocabulary: Source PARCCLevel 1Level 2Level 3Level 4Level 5Usage GuidanceA Level 1 term is provided for definitional coherency, however, in practice onlyLevels 2-5 will be assigned to PARCC items.BindingIEEE LOM Classification element with PerformanceLevel as the taxon sourcevalue in the manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............PerformanceLevelLevel 2...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 161

MetadataPARCC Item Development Technical GuideMetadata ElementCommon Core State Standards IDUse Item Asset Section Test Manifest CategoryAlignmentFieldCommon Core State Standards IDField DescriptionMapping of the item to the relevant Common Core State Standards to the Domain,Practice Area, Standard, and Component level as defined by CCSSO/NGAdocumentation at http://www.corestandards.org/MultiplicityMultiple values permittedValid Values /Curriculum Standards Metadata [CC Implementation 1.2: § 4.5.3]Controlled Vocabulary Provider Label URIMetadata providerID Value: CCSSOCommon Core Subject Label Vocabulary: Source CCSSOCommon Core State StandardCommon Core URI Vocabulary: Source CCSSO Use valid dot notation versions of CCSSO/NGA IDs fromhttp://www.corestandards.org/common-core-state-standards-officialidentifiers-and-xml-representation Use valid dot notation versions of granular CCSSO/NGA IDs whenavailable (see http://www.setda.org/web/guest/Interoperability).Usage GuidanceEach alignment appears as a separate labelledGUID element.BindingCommon Core identifiers in IMS Common Cartridge Curriculum StandardsMetadata structures in the manifest.The binding requires both a human readable label and a URI. The label is optionalin APIP.ExampleXML[resource]010203040506070809101112131415161718............Common Core State StandardCCSS.ELA-Literacy.CCRA.R.3....................Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 162 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementPARCC Evidence StatementUse Item Asset Section Test Manifest CategoryAlignmentFieldPARCC Evidence StatementField DescriptionMapping of the item to the relevant PARCC-defined Evidence Statements[PARCC Evidence].MultiplicityMultiple values permittedValid Values /Curriculum Standards Metadata [CC Implementation 1.2: § 4.5.3]Controlled Vocabulary Provider Label URIMetadata providerID Value: PARCCPARCC Alignment Label Vocabulary: Source PARCCLabel Value: EvidenceStatementID Vocabulary Source: PARCCUse valid statement IDs in the form of [standard].[grade].[evidence statement 3].Example: RL.3.1Usage GuidanceEach alignment appears as a separate labelledGUID element.BindingPARCC-derived identifiers in IMS Common Cartridge Curriculum StandardsMetadata structures in the manifest.The binding requires both a human readable label and a URI. The label is optionalin APIP.ExampleXML[resource]010203040506070809101112131415161718............EvidenceStatementRL.3.1....................Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 163

MetadataPARCC Item Development Technical GuideMetadata ElementPARCC SubClaimUse Item Asset Section Test Manifest CategoryAlignmentFieldPARCC SubClaimField DescriptionMapping of the item to the relevant PARCC-defined SubClaims.MultiplicityMultiple values permittedValid Values /Curriculum Standards Metadata [CC Implementation 1.2: § 4.5.3]Controlled Vocabulary Provider Label URIMetadata providerID Value: PARCCPARCC Alignment Label Vocabulary: Source PARCCLabel Value: SubClaimPARCC Subclaim Vocabulary: Source PARCCMath SubClaim AMath SubClaim BMath SubClaim CMath SubClaim DMath SubClaim EReading - RLReading - RIReading - RVWriting - WEWriting - WKLResearchUsage GuidanceEach alignment appears as a separate labelledGUID element.BindingPARCC-derived identifiers in IMS Common Cartridge Curriculum StandardsMetadata structures in the manifest.The binding requires both a human readable label and a URI. The label is optionalin APIP.ExampleXML[resource]010203040506070809101112131415161718............SubClaimReading - RV....................Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 164 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementPARCC Task ModelUse Item Asset Section Test Manifest CategoryAlignmentFieldPARCC Task ModelField DescriptionMore specific alignment of item to PARCC-defined Task Models.MultiplicityMultiple values permittedValid Values /Curriculum Standards Metadata [CC Implementation 1.2: § 4.5.3]Controlled Vocabulary Provider Label URIMetadata providerID Value: PARCCPARCC Alignment Label Vocabulary: Source PARCCLabel Value: TaskModelID Vocabulary Source: PARCCPARCC Task Model IDs in the form of: [grade][type of task].[task model number] for ELA-Literacy(Example: 7A.1) [grade].[domain].[standard]-[part] for Mathematics(Example: 3.OA.1-1)Usage GuidanceEach alignment appears as a separate labelledGUID element.BindingPARCC-derived identifiers in IMS Common Cartridge Curriculum StandardsMetadata structures in the manifest.The binding requires both a human readable label and a URI. The label is optionalin APIP.ExampleXML[resource]010203040506070809101112131415161718............TaskModel7A.1....................Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 165

MetadataPARCC Item Development Technical GuideMetadata ElementScoring ModeUse Item Asset Section Test Manifest CategoryScoringFieldScoring ModeField DescriptionScoring mode for which item is designed/intended.MultiplicityMultiple values permittedValid Values /Controlled VocabularyScoring Model Vocabulary: Source RTTAHuman ScoringAutomated Machine ScoringKey-based ScoringRule-based ScoringUsage GuidanceThe value needs to be synchronized with the interactionType of the item; manyrequire one scoring mode or another.BindingIEEE LOM Classification element with ScoringMode as the taxon source value inthe manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............ScoringModeRule-based Scoring...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 166 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementPARCC Score PointsUse Item Asset Section Test Manifest CategoryScoringFieldPARCC Score PointsField DescriptionNumber of scoring points assigned to the item.MultiplicitySingle value onlyValid Values /Controlled VocabularyPARCC Score Points Vocabulary: Source PARCCType 1 - 1 pointType 1 - 2 pointsType 2 - 2 pointsType 2 - 3 pointsType 2 - 4 pointsType 3 - 3 pointsType 3 - 6 pointsEBSR - 2 pointsTECR - 2 pointsPCR Reading - 2 pointsPCR Reading - 3 pointsPCR Reading - 4 pointsUsage GuidanceMathematics is currently only using 1, 2, 3, 4, and 6 as possible point values.BindingIEEE LOM Classification element with ScorePoints as the taxon source value inthe manifest.ExampleXML[resource]01020304050607080910111213141516171819202122...............ScorePointsType 3 - 3 points...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 167

MetadataPARCC Item Development Technical GuideMetadata ElementLicense IDUse Item Asset Section Test Manifest* CategoryRightsFieldLicense IDField DescriptionIntellectual property rights and licensing information.MultiplicitySingle value onlyValid Values /LOM Language string.Controlled Vocabulary The language (omitted) as a character string (ISO/IEC 10646-1:2000[UCS]) The ID or URI as a character string (ISO/IEC 10646-1:2000 [UCS]). AURI should be encoded as a URI (URI).Usage GuidanceProvide the ID or URI to the rights statement or any specific licensing agreementsand permissions for use of the item, asset, section, test or manifest.The language should be omitted.BindingIEEE LOM Rights.description element in the manifest.ExampleXML[resource]010203040506070809101112131415...............http://creativecommons.org/licenses/by/3.0/............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 168 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementCopyrightUse Item Asset Section Test Manifest CategoryRightsFieldCopyrightField DescriptionIf copyright and other restrictions apply.MultiplicitySingle value onlyValid Values /Controlled VocabularyLOM Rights.copyrightAndOtherRestrictions Vocabulary: Source LOM [LOM2002]yesnoUsage GuidanceThis element is mandatory for manifests, and is recommended for items, assets,sections or test.BindingIEEE LOM rights.copyrightAndOtherRestrictions element in the manifest.ExampleXML[manifest]01020304050607080910111213.........LOMv1.0yes......Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 169

MetadataPARCC Item Development Technical GuideMetadata ElementMedia TypeUse Item Asset Section Test Manifest CategoryMediaFieldMedia TypeField DescriptionAsset media type.MultiplicitySingle value onlyValid Values /Controlled VocabularyMedia Type Vocabulary: Source RTTAText PassageImageTableVideoAudioInteractiveAnimationTranslationTranscriptUsage GuidanceBindingIEEE LOM Educational.learningResourceType element with RTTAv1.0 as thevocabulary source value in the manifest.ExampleXML[resource]01020304050607080910111213141516..................RTTAv1.0audio............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 170 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementPackage TypeUse Item Asset Section Test Manifest CategoryMediaFieldPackage TypeField DescriptionPackage media type.MultiplicitySingle value onlyValid Values /Controlled VocabularyPackage Type Vocabulary Source: RTTARTTA PackageUsage GuidanceElement required as given for package manifest metadata.BindingIEEE LOM Educational.learningResourceType element with RTTAv1.0 as thevocabulary source value in the manifest.ExampleXML[manifest]010203040506070809101112.........RTTAv1.0RTTAPackage.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 171

MetadataPARCC Item Development Technical GuideMetadata ElementMIME TypeUse Item Asset Section Test Manifest CategoryMediaFieldMIME TypeField DescriptionSpecific file MIME type of the asset (e.g., JPEG, MP3)MultiplicitySingle value onlyValid Values /Controlled VocabularyMIME Type Vocabulary: Source MIME media types and subtypes from the IANAregistry [IANA MIME].Usage GuidanceBindingIEEE LOM Technical.format element in the manifest.ExampleXML[resource]01020304050607080910111213..................audio/mp3...............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 172 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementMaster to Version RelationUse Item Asset Section Test Manifest CategoryMediaFieldMaster to Version RelationField DescriptionExpressing how an item asset is related to a source or master file.MultiplicitySingle value onlyValid Values /Controlled VocabularySubset of LOM Relation.kind Vocabulary: Source LOM [LOM 2002]hasversionisversionofUsage GuidanceThe entry for the master file must point to the version via the hasversion propertyand the ID of the version in the manifest. The version links back to the master viaisversionof and the master's ID.Only hasversion or isversionof are valid values from the vocabulary for expressingthe relationship between assets.BindingIEEE LOM Relation element in the manifest.ExampleXML[resource]0102030405060708091011121314151617181920...............hasversionVE_IP_02css............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 173

MetadataPARCC Item Development Technical GuideMetadata ElementItem to Preview RelationUse Item Asset Section Test Manifest CategoryMediaFieldItem to Preview RelationField DescriptionExpressing how an item preview is related to an item.MultiplicitySingle value onlyValid Values /Controlled VocabularyExtension of LOM Relation.kind Vocabulary: Source LOM [LOM 2002]haspreviewispreviewofUsage GuidanceThe entry for the item must point to the preview asset via the haspreview propertyand the ID of the preview in the manifest. The preview links back to the item viaispreviewof and the item’s ID.Only haspreview or ispreviewof are valid values from the vocabulary forexpressing the relationship between an item and its preview.BindingIEEE LOM Relation element in the manifest with RTTAv1.0 as the vocabularysource value in the manifest.ExampleXML[resource]0102030405060708091011121314151617181920...............RTTAv1.0ispreviewofitem-I01............Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 174 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementAccessibility Display FeatureUse Item Asset Section Test Manifest CategoryAccessibilityFieldAccessibility Display FeatureField DescriptionRelevant accessibility support features.MultiplicityMultiple values permittedValid Values /Accessibility Display Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptionMagnificationMagnification IncreasedWhiteSpacing Increased White Spacing ReverseContrastReverse Contrast AlternateBackgroundColor Alternate Background Color AlternateTextColorAlternate Text Color InvertColorInvert Color ColorOverlayColor Overlay AnswerMaskingAnswer Masking GeneralMaskingGeneral Masking AdditionalTestingTime Additional Testing Time KeywordEmphasisKeyword EmphasisLineReaderLine Reader SpeechtoTextSpeech to TextRefreshableBrailleBraille: RefreshableClosedCaptionsClosed CaptionsReducedAnswersReduced Answers NegativesRemovedNegatives Removed ChunkingChunking ScaffoldingScaffolding AuditoryCalmingAuditoryCalming HazardHazardBreaksBreaks Usage GuidanceThe same vocabulary is used for both the accessibility display features and theexcluded accessibility display features.Vocabulary terms marked with a in the Description column should not be usedin describing content; these are display features supported by the test client.Vocabulary terms marked with a in the Description column should not be usedin describing content; these features not currently used by PARCC.BindingAccessibility metadata accessibilityDisplayFeature element with RTTAv1.0 as thevocabulary source value in the manifest.V 0.65: Public Draft 20130912 175

MetadataPARCC Item Development Technical GuideMetadata ElementExampleXML[resource]0102030405060708091011121314Accessibility Display Feature............RTTAv1.0Magnification.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 176 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementExcluded Accessibility Display FeatureUse Item Asset Section Test Manifest CategoryAccessibilityFieldExcluded Accessibility Display FeatureField DescriptionIneligible accessibility display features.MultiplicityMultiple values permittedValid Values /Accessibility Display Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptionMagnificationMagnification IncreasedWhiteSpacing Increased White Spacing ReverseContrastReverse Contrast AlternateBackgroundColor Alternate Background Color AlternateTextColorAlternate Text Color InvertColorInvert Color ColorOverlayColor Overlay AnswerMaskingAnswer Masking GeneralMaskingGeneral Masking AdditionalTestingTime Additional Testing Time KeywordEmphasisKeyword EmphasisLineReaderLine Reader SpeechtoTextSpeech to TextRefreshableBrailleRefreshable BrailleClosedCaptionsClosed CaptionsReducedAnswersReduced Answers NegativesRemovedNegatives Removed ChunkingChunking ScaffoldingScaffolding AuditoryCalmingAuditoryCalming HazardHazardBreaksBreaks Usage GuidanceThe same vocabulary is used for both the accessibility display features and theexcluded accessibility display features.Vocabulary terms marked with a in the Description column should not be usedin describing content; these are display features supported by the test client.Vocabulary terms marked with a in the Description column should not be usedin describing content; these features not currently used by PARCC.BindingAccessibility metadata accessibilityExcludedDisplayFeature element withRTTAv1.0 as the vocabulary source value in the manifest.V 0.65: Public Draft 20130912 177

MetadataPARCC Item Development Technical GuideMetadata ElementExampleXML[resource]0102030405060708091011121314Excluded Accessibility Display Feature............RTTAv1.0Hazard.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 178 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementAccessibility Support FeatureUse Item Asset Section Test Manifest CategoryAccessibilityFieldAccessibility Support FeatureField DescriptionRelevant accessibility support features.MultiplicityMultiple values permittedValid Values /Accessibility Support Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptionTextOnlySpoken: Text OnlyGraphicsOnlySpoken: Graphics OnlyTextGraphicsSpoken: Text and GraphicsNonVisualSpoken: Non VisualDirectionsOnlySpoken: Directions OnlyBrailleBraille ContractedBrailleBraille: ContractedUncontractedBrailleBraille: UncontractedRefreshableBrailleBraille: RefreshableTactileTactileTactileSpokenFileTactile: Spoken FileTactileSpokenTextTactile: Spoken TextTactileBrailleTextTactile: Braille TextSigningASLSigning: ASLSigningSignedEnglishSigning: Signed EnglishSimplifiedLanguageSimplified Language KeywordTranslationKeyword TranslationItemTranslationItem Translation LangageLearnerSupport Learner Language Support Guidance CognitiveGuidanceSupport Cognitive Guidance Support Usage GuidanceThe same vocabulary is used for both the accessibility support features and theexcluded accessibility support features.The four Spoken features are exclusive, only one of the four should be present.Vocabulary terms marked with a in the Description column should not be usedin describing content; these features not currently used by PARCC.BindingAccessibility metadata accessibilitySupportFeature element with RTTAv1.0 as thevocabulary source value in the manifest.ExampleXML[resource]0102030405060708091011121314............RTTAv1.0TextOnly.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 179

MetadataPARCC Item Development Technical GuideMetadata ElementExcluded Accessibility Support FeatureUse Item Asset Section Test Manifest CategoryAccessibilityFieldExcluded Accessibility Support FeatureField DescriptionIneligible accessibility support features.MultiplicityMultiple values permittedValid Values /Accessibility Support Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptionTextOnlySpoken: Text OnlyGraphicsOnlySpoken: Graphics OnlyTextGraphicsSpoken: Text and GraphicsNonVisualSpoken: Non VisualDirectionsOnlySpoken: Directions OnlyBrailleBraille ContractedBrailleBraille: ContractedUncontractedBrailleBraille: UncontractedRefreshableBrailleBraille: RefreshableTactileTactileTactileSpokenFileTactile: Spoken FileTactileSpokenTextTactile: Spoken TextTactileBrailleTextTactile: Braille TextSigningASLSigning: ASLSigningSignedEnglishSigning: Signed EnglishSimplifiedLanguageSimplified Language KeywordTranslationKeyword TranslationItemTranslationItem Translation LangageLearnerSupport Learner Language Support Guidance CognitiveGuidanceSupport Cognitive Guidance Support Usage GuidanceThe same vocabulary is used for both the accessibility support features and theexcluded accessibility support features.Vocabulary terms marked with a in the Description column should not be usedin describing content; these features not currently used by PARCC.BindingAccessibility metadata accessibilityExcludedSupportFeature element withRTTAv1.0 as the vocabulary source value in the manifest.ExampleXML[resource]0102030405060708091011121314............RTTAv1.0SigningASL.........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 180 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata ElementCompanion MaterialUse Item Asset Section Test Manifest CategoryAccessibilityFieldCompanion MaterialField DescriptionAssociated tools required by item for student interaction or response.MultiplicityMultiple values permittedValid Values /Companion Material Vocabulary: Source RTTAControlled Vocabulary Vocabulary ValueDescriptioncalculatorCalculator (general)calculatorFourFunction Four Function Calculator with Square RootcalculatorScientificScientific CalculatorcalculatorGraphingGraphing Calculator (TI 84 Equivalent)calculatorFullFunction Full Function Graphing CalculatorrulerRuler (general)rulerEightRuler with 1/8 inch divisionsrulerQuarterRuler with 1/4 inch divisionsprotractorProtractorcompassCompassstraightEdgeStraight EdgenotePaperNote PapergraphPaperGraph PaperwordProcessingToolWord Processing ToolequationEditorEquation EditorpopupGlossaryPopup GlossarynotePadNote PadgraphicOrganizerGraphic OrganizerreadingPassageReading PassagedigitalMaterialDigital MaterialphysicalMaterialPhysical MaterialdictionaryDictionary thesarusThesarus glossaryGlossary textAnnotationText AnnotationspellCheckerSpell CheckerwordPredictionWord PredictionvisualDictionaryVisual DictionarydrawingToolDrawing ToolformulaChartFormula ChartUsage GuidanceEach companion material for the item is listed separately. Exclusive combinationsof items are included in as parts of the orComposite, otherwise there is only oneitem per orComposite. Any item not listed is not available to the student.Vocabulary terms marked with a in the Description column should not be usedin describing content; these features not currently used by PARCC.BindingIEEE LOM Technical.requirement element with RTTAv1.0 as the vocabularysource value in the manifest.V 0.65: Public Draft 20130912 181

MetadataPARCC Item Development Technical GuideMetadata ElementExampleXML[resource]010203040506070809101112131415161718192021222324Companion Material...............RTTAv1.0Companion MaterialRTTAv1.0calculator….........Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: 182 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideMetadata Metadata XML Document StructureThe metadata section within an XML document should be organized to group metadata elements in the followingorder:1. LOM metadata elements2. Accessibility metadata elements3. QTI metadata4. CSM (curriculum standards) metadata elementsWithin the LOM metadata, the elements should be ordered following the general base schema order presented inLOM [LOM 2002], e.g., general elements followed by life cycle elements, and proceeding though annotationelements and finally classification elements. Within the Accessibility, QTI and CSM metadata, there is no preferredordering of the elements.These recommendations are not part of the APIP profile and an XML document with metadata elements in any orderwill validate.The nominal ordering of elements is illustrated in Code Listing 6.1. For brevity, the example does not include fullset of metadata elements.Code Listing 6.1: Nominal Ordering of Metadata in an XML Document0102030405060708091011121314…………Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Line 02-04: The resource LOM metadata (metadata elements omitted) Line 05-07: The resource Accessibility metadata (metadata elements omitted) Line 08-10: The resource QTI metadata (metadata elements omitted) Line 11-13: The resource CSM metadata (metadata elements omitted)V 0.65: Public Draft 20130912 183

ExchangePARCC Item Development Technical GuideExchange PARCC uses the APIP Profile [APIP Tech 1.0] of Content Packaging [CP Info 1.2] to exchange assessment itemdescriptions (including accessibility information ) along with their associated metadadata and media assets.Content packages exchanges include: between the item developer and PARCC between the PARCC assessment system and a test clientGuidelines for exchange, based on the APIP 1.0 Best Practice and Implementation Guide [APIP BP 1.0], address: Overall content package structure including recommended PARCC folder structure Exchange of one or more item descriptions, an APIP Item Bank Package [APIP Tech 1.0: § 3.2.1] Exchange of items and sections, an APIP Section Package [APIP Tech 1.0: § 3.2.1] Exchange of an entire test including items, sections and test forms, an APIP Test Package [APIP Tech 1.0:§ 3.2.1] Expressing variants of an item used to provide alternative accessible forms of an item XML elements of manifests, tests and sectionsThe guidelines do not detail the APIP Item Package [APIP Tech 1.0: § 3.2.1] used to exchange only a single item; itis similar to the APIP Item Bank Package.All packaged data exchange must conform to all of the Exchange guidelines. Unless otherwise noted, all XMLdocuments must use the RTTA APIP Profile Schemata specified in the Schemata section.Package StructureAn APIP test is composed of one or more sections (sections may be recursively nested), each of which contains oneor more items, each of which in turn uses zero or more media assets. This nested structure of assets inside items,inside sections, inside a test is described through a collection of XML data. There is a separate XML documentdescribing the test, each section and each item, plus a separate media file for each version of each asset. There maybe additional files for resource processing templates and schema definitions. The relationship of these separatedocuments is described in yet another XML document, the package manifest. The manifest contains a flattenedstructure where each part references/points to its subparts, and the subparts are maintained as separate files.Metadata about each part is also contained inline within the manifest, along with metadata about the manifest as awhole. An example of a test structure is shown in Figure 7.1.TestPart T01Section S01Section S02Section S01aSection S01bQ007 Q008 Q009Q001 Q002 Q003 Q004 Q005 Q006A008 A009 A010A001 A002 A003 A004 A005 A006 A007Figure 7.1: Sample Test Structure184 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Each asset file and XML document for a test, section or item is given its own file name; the MIME type for an XMLdocument is text/xml (file extension .xml); the MIME type for each media file corresponds to the asset type. TheXML manifest document is named imsmanifest.xml.All files are collected and compressed into a zip archive format [ZIP]. This zipped file is used for exchange. Figure7.2 illustrates the sample test structure flattened in the manifest with links between items, and shows the files in thecorresponding zip file. The figure does not illustrate the folder structure within the zip file.Manifestimsmanifest.xmltest-T01.xmlsection-S01.xmlsection-S01a.xmlI-Q01.xmlI-Q02.xmlI-Q03.xmlsection-S01b.xmlI-Q04.xmlI-Q05.xmlI-Q06.xmlsection-S02.xmlI-Q07.xmlI-Q08.xmlI-Q09.xmlasset A001asset A002asset A003asset A004asset A005asset A006asset A007asset A008asset A009asset A010Test T01Section S01Section S01aItem Q001Item Q002Item Q003Section S01bItem Q004Item Q005Item Q006Section S02Item Q007Item Q008Item Q009Asset A001Asset A002Asset A003Asset A004Asset A005Asset A006Asset A007Asset A008Asset A009Asset A010FilesFigure 7.2: Sample Manifest and FilesDepending on the type of package, some of the elements may be omitted, e.g., an item bank does not contain test orsection data. The package may contain other optional files (e.g., XSD schemata), each of which will be described inthe manifest. Additional assets, e.g., the source media, variants, common files, may be included in the manifest.The Item Bank Manifest shown in Code Listing 7.1 illustrates adding additional files to the manifest. (Note: forversions, the links between the versions of the asset are described in the metadata, not the manifest.)Within the zip file, the various test, section and item files are organized into folders, as shown in Figure 7.3.imsmanifest.xmlteststest-T01test-T01.xmltest-...sectionssection-S01section-S01.xmlsection-...itemsitem-I01item-I01.xmlasset-A01asset-A02item-...item-....xmlasset-...resourcesasset-R01asset-...rptemplatesrpt-T01.xmlrpt-....xmlxsdsxsd-X01.xsdxsd-....xsdPackage .zipFigure 7.3: Sample .zip and Folder StructureThe following guidelines describe the structure of a PARCC package zip file and folders: The entire package is a zip [.zip] file. The file name must be descriptive, but otherwise there are no currentPARCC naming conventions for the file.V 0.65: Public Draft 20130912 185

ExchangePARCC Item Development Technical GuideA single imsmanifest.xml containing the entire package manifest is contained within the root level of thezip file.A single (optional) tests folder containing the test descriptions is contained within the root level of the zipfile.o Within the tests folder, there is a separate folder for each test. Each individual test folder namemust be descriptive and unique, but otherwise there are no current PARCC naming conventionsfor the folder.• Within each individual test folder is the XML document describing the test. The testXML document file name should correspond to the parent folder name, but it need not beidentical.A single (optional) sections folder containing the section descriptions is contained within the root level ofthe zip file.oWithin the sections folder, there is a separate folder for each section. Each individual sectionfolder name must be descriptive and unique, but otherwise there are no current PARCC namingconventions for the folder.• Within each individual section folder is the XML document describing of the section.The section XML document file name should correspond to the parent folder name, but itneed not be identical.A single items folder containing the item descriptions is contained within the root level of the zip file.o Within the items folder, there is a separate folder for each item. Each individual item folder namemust be descriptive and unique across ALL PARCC items.• Within each individual item folder is the XML document describing of the item. Theitem XML document file name should correspond to the parent folder name, but it neednot be identical.• Within each individual item folder is zero or more assets that are associated with theitem. Each asset file has a mime type that corresponds to the asset. The asset file nameshould be descriptive and must be unique to the item. Asset file name should be uniqueacross ALL PARCC items.• Within each individual item folder is a single (optional) companionmaterials foldercontaining any reading passage and digital material accessibility companion materials forthe item.• Within each individual item folder is a single (optional) preview folder containing theimage of the item (not shown in Figure 7.3). The preview file name should correspond tothe item file name.• Within each individual item folder is a single (optional) sourcemedia folder containingthe source media (e.g., source photos, uncompressed or raw video) for any media assetsused by the item (not shown in Figure 7.3). The source media file name shouldcorrespond to the corresponding asset file name.• Within each individual item folder is a single (optional) developerinfo folder containingany additional developer resources (not shown in Figure 7.3). File names shouldcorrespond to the item file name.A single (optional) resources folder containing the assets and resources shared across one or more items iscontained within the root level of the zip file.o Within the folder is one or more assets that are shared across item. Each asset file has a mimetype that corresponds to the asset. The asset file name should be descriptive and unique to theitem.o Within the folder is a single (optional) sourcemedia folder containing the source media (e.g.,source photos, uncompressed or raw video) for any shared media assets in the package (not shownin Figure 7.3). The source media file name should correspond to the corresponding shared assetfile name.A single (optional) rptemplates folder containing the response processing templates is contained within theroot level of the zip file.o Within the response processing templates folder is an individual XML document describing eachresponse processing template.186 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange A single (optional) xsds folder containing the XML schemata is contained within the root level of the zipfile.o Each of the unique XSDs references in the package are contained within the folder. The XSDsfollow the schemata file naming convention described in the Annex.A PARCC package need not include XSD schemata for the XML documents that use the standard PARCC APIPschemata.Currently, PARCC resource processing templates do need to be included in the package.All shared resources needed for an item need to be included in an item bank package even if those resources arealready in the item bank.The sample structure shown in Figures 7.1 and 7.2 corresponds to the zip file and folder structure shown in Figure7.4.Manifestimsmanifest.xmltest-T01.xmlsection-S01.xmlsection-S01a.xmlI-Q01.xmlI-Q02.xmlI-Q03.xmlsection-S01b.xmlI-Q04.xmlI-Q05.xmlI-Q06.xmlsection-S02.xmlI-Q07.xmlI-Q08.xmlI-Q09.xmlasset A001asset A002asset A003asset A004asset A005asset A006asset A007asset A008asset A009asset A010Test T01Section S01Section S01aItem Q001Item Q002Item Q003Section S01bItem Q004Item Q005Item Q006Section S02Item Q007Item Q008Item Q009Asset A001Asset A002Asset A003Asset A004Asset A005Asset A006Asset A007Asset A008Asset A009Asset A010Filesimsmanifest.xmlteststest-T01test-T01.xmlsectionssection-S01section-S01.xmlsection-S01asection-S01a.xmlsection-S01bsection-S01b.xmlsection-S02section-S02.xmlitemsitem-I01I-Q01.xmlasset-A001asset-A002asset-Ao03item-I02I-Q02.xmlitem-I03I-Q03.xmlasset-A004item-I04I-Q04.xmlitem-I05I-Q05.xmlasset-A005asset-A006item-I06I-Q06.xmlasset-A007item-I07I-Q07.xmlitem-I08I-Q08.xmlasset-.A008item-I09I-Q09.xmlasset-A009asset-A010Package .zipFigure 7.4: Package .zip File and Folder Structure for Sample Test StructurePARCC APIP Item Bank PackageAn item bank package is used to exchange of one or more items between systems. PARCC uses item bank packagesto exchange items between the item developer and the PARCC item bank. Because this package form does notcontain sections or test definitions, it is not suitable for exchanging complete assessments.As noted in the workflow , when an item is formally submitted to PARCC, the package must include: package level metadata the items the essential/required developer provided metadata for each item all assets used when the item is rendered in the test client, including associated stylesheets, JavaScript, etc. all source media for all assets an asset that is the item development template/documentationV 0.65: Public Draft 20130912 187

ExchangePARCC Item Development Technical Guidean asset that is a sample screen capture of the item renderingmetadata for all assets and resourcesFigure 7.5 illustrates a sample item bank containing two assessment items: The first item (I01) includes 3 assets (an audio file, A01), two images, A02, A03) and an additional“standalone” asset that is the item preview (P01) The second item (I02) includes one asset (an image, A04)I01I02A01 A02 A03 P01 A04Figure 7.5: Sample PARCC APIP Item Bank Exchange StructureFigure 7.6 illustrates the corresponding content package manifest structure.Manifestimsmanifest.xmlItem-I01.xmlItem-I02.xmlasset-I01-A01.mp3asset-I01-A02.svgasset-I01-A03.pngpreview-I01-P01.pngasset-I02-A04.pngFigure 7.6: Sample PARCC APIP Item Bank Manifest StructureFigure 7.7 illustrates the content package zip file and folder structure. The package includes 8 files: the manifest XML file two (2) assessment item XML files each in their own folder four (4) asset files in the corresponding item foldersimsmanifest.xmlitemsitem-I01Item-I01.xmlasset-I01-A01.mp3asset-I01-A02.svgasset-I01-A03.pngpreviewpreview-I01-P01.pngitem-I02Item-I02.xmlasset-I02-A04.pngPackage .zipFigure 7.7: Sample PARCC APIP Item Bank .zip File and Folder StructureCode Listing 7.1 illustrates a portion of the item bank content package manifest for a package containing twoassessment items. For brevity, the example does not include accessibility information, additional item developerinformation or source media files.Code Listing 7.1: Example PARCC APIP Item Bank Manifest XML Document188 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange 00010203040506070809101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657APIP Item Bank1.0.0V 0.65: Public Draft 20130912 189

ExchangePARCC Item Development Technical Guide5859606162636465666768697071Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 00-10: Standard XML header and namespace information Lines 12-13: A scheme declaration that identifies this as an item bank package Line 14: LOM metadata for the manifest as a whole (empty in the example) Lines 18-29: The first item:o Lines 20-23: LOM, accessibility, QTI and curriculum standards metadata for the first item (emptyin the example)o Line 25: File declaration link to locate the item description XML document in the folder structureinside the item-specific folder in the root level items foldero Lines 26-28: References to the asset files for the item: audio file and two image Lines 30-47: Descriptions of the three assets used in the first item, including their metadata and the link tothe asset file in the folder structure for each asset Lines 48-53: Description of a standalone resource that is the item preview (not used in the item), includingfile-level metadata and a link to the resource inside the preview folder in the item-specific folder in the rootlevel items folder Lines 55-63: The second item:o Lines 56-59: LOM, accessibility, QTI and curriculum standards metadata for the first item (emptyin the example)o Line 61: File declaration link to locate the item description XML document in the folder structureinside the item-specific folder in the root level items foldero Lines 62: Reference to the image asset file for the item Lines 64-69: Descriptions of the asset used in the second item, including its metadata and the link to theasset file in the folder structureFor the sake of brevity, the metadata attributes encoded in the LOM, accessibility, QTI and curriculum standardsmetadata sections have been collapsed into the empty , ,, and elements (lines 14, 20-23, 32, 38, 44, 50, 56-59, 65).The resource element type attribute defines the type of resource: The items (lines 18, 54) are declared as resource type imsqti_apipitem_xmlv2p1 The assets/resources (lines 30, 36, 42, 48, 52, 66) are declared as resource typeassociatedcontent/apip_xmlv1p0/learning-application-resourceIn addition to listing the resource files, the manifest describes the relationships between the resources. For example,the first item (line 18) requires three assets; the dependency between the item and its assets is defined through thedependency elements (lines 24-26). The dependency element includes the identifierref attribute with a value thatmatches the identifier attribute of the corresponding resource in the manifest.190 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange The items and each resource file element (lines 24, 34, 40, 46, 52, 61, 68) includes an href attribute with the URIpath to the location of the corresponding file in the package folder structure.The standalone resource preview-I01 (lines 48-53) is the preview for the item I01. The relationship between theitem and the preview is not expressed in the item, but is expressed as part of the metadata of both. Each resource’smetadata has a Master to Version Relation metadata attribute that links it to the preview. For the example, the item,I01 is linked to the preview preview-I01-P01 through a haspreview property in the item that links to the preview, andthe preview-I01-P01 resource has an ispreviewof property of the metadata attribute that links to the item. File-levelmetadata attributes for the preview resource would describe it as the item preview.PARCC APIP Item PackageAn item package is used to exchange a single item between systems. The item package is similar to the item bankpackage with two exceptions: Only one item is permitted. The package schema is APIP Item (versus APIP Item Bank), see lines 12-13 in CodeListing 7.1.PARCC APIP Section PackagePARCC APIP Section packages use the assessmentSection XML elements [QTI Info 2.1] to organizeassessmentItems into groups that may contain multiple assessmentItems, references to other assessmentSectionsand section-specific content in the form of rubricBlocks.Each assessmentSection element is described within its own XML file. An assessmentSection elementincorporates items into the assessment by use of the assessmentItemRef element, which uses identifier and hrefattributes to link to the appropriate item resource.Figure 7.8 illustrates a sample section (S01) containing two assessment items: The first item (I01) includes 6 assets (A01, A02, A03, A04, A05, A06) The second item (I02) includes one asset (A07)Section S01I01I02A01 A02 A03 A04 A05 A06 A07Figure 7.8: Sample PARCC APIP SectionFigure 7.9 illustrates the corresponding content package manifest structure.V 0.65: Public Draft 20130912 191

ExchangePARCC Item Development Technical GuideManifestimsmanifest.xmlsection-S01.xmlItem-I01.xmlItem-I02.xmlasset-I01-A01asset-I01-A02asset-I01-A03asset-I01-A04asset-I01-A05asset-I01-A06asset-I02-A07Figure 7.9: Sample PARCC APIP Section Manifest StructureFigure 7.10 illustrates the content package zip file and folder structure. The package includes 11 files: the manifest XML file for the section section package the section XML file two (2) assessment item XML files each in their own folder seven (7) asset files in the corresponding item foldersimsmanifest.xmlsectionssection-S01section-S01.xmlitemsitem-I01Item-I01.xmlasset-I01-A01asset-I01-A02asset-I01-A03asset-I01-A04asset-I01-A05asset-I01-A06item-I02Item-I02.xmlasset-I02-A04Package .zipFigure 7.10: Sample PARCC APIP Section .zip File and Folder StructureCode Listing 7.2 illustrates a partial package manifest that incorporates an assessmentSection that is comprised oftwo assessmentItems. For brevity, the example does not include accessibility information, additional itemdeveloper information or source media files.192 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Code Listing 7.2: Example Partial PARCC APIP Section Manifest XML Document000102030405060708091011121314151617181920212223242526272829303132333435363738394041424344454647484950515253APIP Section 1.0.0Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: V 0.65: Public Draft 20130912 193

ExchangePARCC Item Development Technical GuideThe example manifest does not include all of the assets used in the items.In the example: Lines 00-10: Standard XML header and namespace information Lines 12-13: A scheme declaration that identifies this as an section package Line 14: LOM metadata for the manifest as a whole (empty in the example) Lines 18-29: The first section:o Line 20: LOM for the first section (empty in the example)o Line 22: File declaration link to locate the section description XML document in the folderstructure inside the section-specific folder in the root level sections foldero Lines 23-24: References to the two items in the section Lines 26-40: The first item:o Lines 28-31: LOM, accessibility, QTI and curriculum standards metadata for the first item (emptyin the example)o Line 33: File declaration link to locate the item description XML document in the folder structureinside the item-specific folder in the root level items foldero Lines 34-39: References to the asset files for the item Lines 41-50: The first item:o Lines 43-46: LOM, accessibility, QTI and curriculum standards metadata for the first item (emptyin the example)o Line 48: File declaration link to locate the item description XML document in the folder structureinside the item-specific folder in the root level items foldero Line 49: Reference to the asset for the item Line 51: Placeholder for the omitted assetsFor the sake of brevity, the metadata attributes encoded in the LOM, accessibility, QTI and curriculum standardsmetadata sections have been collapsed into the empty , ,, and elements (lines 14, 20, 28-31, 43-46).The resource element type attribute defines the type of resource: The section (line 18) is declared as resource type imsqti_apipsection_xmlv2p1 The items (lines 26, 41) are declared as resource type imsqti_apipitem_xmlv2p1 The assets/resources (omitted) are declared as resource type associatedcontent/apip_xmlv1p0/learningapplication-resourceIn addition to listing the resource files, the manifest describes the relationships between the resources. For example,the section (line 18) includes two items; the dependency between the section and its item is defined through thedependency elements (lines 23-24). The dependency element includes the identifierref attribute with a value thatmatches the identifier attribute of the corresponding resource in the manifest.The section and each item file elements (lines 22, 33, 48) includes an href attribute with the URI path to the locationof the corresponding file in the package folder structure.The XML encoding describing the assessment section is shown in Code Listing 7.3.Code Listing 7.3: Example PARCC Assessment Section XML Document000102030405060708Please answer the questions using these directions...194 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange 091011Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 00-05: Namespace and schema references (assessmentSection specific) Lines 06-08: Rubric block for the section Lines 09-10: References to the items in the sectionThe rubricBlock contains content that is associated with all of the items contained within an assessmentSection. Inthis example, the content provides cursory instructions to the student taking the assessment. The rubricBlockelement may be used to present reading passage content or whatever other material is appropriate to associate withan entire section rather than an individual item.An apipAccessibility element (not shown) would follow the rubricBlock element. The apipAccessibility elementprovides accessibility information for the rubricBlock content in the same manner and with the same structure as anapipAccessibility element that details accessibility for an assessmentItem.The assessmentItemRef elements identify the assessmentItems to be included in a section. The identifier attributevalue for the element should match the identifier value of the resource element in the manifest associated with theitem.The assessmentSection description may contain additional optional data specifying complex ordering, scoring, andpresentation rules [QTI Info 2.1].PARCC APIP Test PackagePARCC APIP Test packages are used to describe an entire testing experience. The assessmentTest XML element[QTI Info 2.1] contains references to one or more assessmentSection, each of which in turn references theassessmentItem XML that represents individual test questions.Each assessmentTest element is contained within its own XML file. An assessmentTest element incorporatessections by use of the assessmentSectionRef element, which uses identifier and href attributes to link to theappropriate section resource.Each assessmentSection element is contained within its own XML file. An assessmentSection elementincorporates items by use of the assessmentItemRef element, which uses identifier and href attributes to link to theappropriate item resource.Figure 7.11 illustrates a sample test (T01) containing one section: The section (S01) includes two assessment items:o The first item (I01) includes 6 assets (A01, A02, A03, A04, A05, A06)o The second item (I02) includes one asset (A07)V 0.65: Public Draft 20130912 195

ExchangePARCC Item Development Technical GuideTest T01Section S01I01I02A01 A02 A03 A04 A05 A06 A07Figure 7.11: Sample PARCC APIP TestFigure 7.12 illustrates the corresponding content package manifest structure.Manifestimsmanifest.xmltest-T01.xmlsection-S01.xmlItem-I01.xmlItem-I02.xmlasset-I01-A01asset-I01-A02asset-I01-A03asset-I01-A04asset-I01-A05asset-I01-A06asset-I02-A07Figure 7.12: Sample PARCC APIP Test Manifest StructureFigure 7.12 illustrates the content package zip file and folder structure. The package includes 12 files: the manifest XML file for the test package the test XML file the section XML file two (2) assessment item XML files each in their own folder seven (7) asset files in the corresponding item foldersimsmanifest.xmlteststest-T01test-T01.xmlsectionssection-S01section-S01.xmlitemsitem-I01Item-I01.xmlasset-I01-A01asset-I01-A02asset-I01-A03asset-I01-A04asset-I01-A05asset-I01-A06item-I02Item-I02.xmlasset-I02-A04Package .zipFigure 7.13: Sample PARCC APIP Test .zip File and Folder StructureCode Listing 7.4 illustrates a partial package manifest that contains an assessmentTest containing oneassessmentSection with two items. For brevity, the example does not include accessibility information, additionalitem developer information or source media files.196 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Code Listing 7.4: Example Partial PARCC APIP Test Manifest XML Document0001020304050607080910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455APIP Section 1.0.0V 0.65: Public Draft 20130912 197

ExchangePARCC Item Development Technical Guide5657585060Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: The example manifest does not include all of the assets used in the items.In the example: Lines 00-10: Standard XML header and namespace information Lines 12-13: A scheme declaration that identifies this as an test package Line 14: LOM metadata for the manifest as a whole (empty in the example) Lines 18-24: The first section:o Lines 20: LOM for the first section (empty in the example)o Line 22: File declaration link to locate the test description XML document in the folder structureinside the test-specific folder in the root level tests foldero Line 23: References to the item in the section Lines 25-32: The first section:o Lines 27: LOM for the first section (empty in the example)o Line 29: File declaration link to locate the section description XML document in the folderstructure inside the section-specific folder in the root level sections foldero Lines 30-31: References to the two items in the section Lines 33-47: The first item:o Lines 35-39: LOM, accessibility, QTI and curriculum standards metadata for the first item (emptyin the example)o Line 40: File declaration link to locate the item description XML document in the folder structureinside the item-specific folder in the root level items foldero Lines 41-46: References to the asset files for the item Lines 48-57: The second item:o Lines 50-53: LOM, accessibility, QTI and curriculum standards metadata for the first item (emptyin the example)o Line 55: File declaration link to locate the item description XML document in the folder structureinside the item-specific folder in the root level items foldero Line 56: Reference to the asset for the item Line 58: Placeholder for the omitted assetsFor the sake of brevity, the metadata attributes encoded in the LOM, accessibility, QTI and curriculum standardsmetadata sections have been collapsed into the empty , ,, and elements (lines 14, 20, 27, 35-39, 50-53).The resource element type attribute defines the type of resource The test (line 18) is declared as resource type imsqti_apiptest_xmlv2p1 The section (line 25) is declared as resource type imsqti_apipsection_xmlv2p1 The items (line 33, 48) are declared as resource type imsqti_apipitem_xmlv2p1 The assets/resources (omitted) are declared as resource type associatedcontent/apip_xmlv1p0/learningapplication-resourceIn addition to listing the test, section and item files, the manifest describes the relationships between them. Forexample, the test (line 18) includes one dependency: the dependency between the test (Test-T01) and section(Section-S01) is defined through the dependency element (line 23). The dependency between the section (Section-S01) and its items (Item-I01, Item-I02) is defined through the dependency elements (lines 30-31). It is not necessary198 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange to include indirect dependencies. The dependency element includes the identifierref attribute with a value thatmatches the identifier attribute of the corresponding resource in the manifest.The test, section and each item file elements (lines 22, 29, 40, 55) includes an href attribute with the URI path to thelocation of the corresponding file in the package folder structure.The XML description of the test is shown in Code Listing 7.5.Code Listing 7.5: Example PARCC Assessment Test Element XML Document00010203040506070809Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 00-05: Namespace and schema references (assessmentTest specific) Lines 06-08: Test PartThe assessmentTest contains a single testPart that wraps references to the one assessmentSection using anassessmentSectionRef element: The identifier attribute of an assessmentSectionRef element should match one of the resource identifiers inthe manifest for an assessmentSection. The href attribute should point to the file location of the relevant assessmentSection, relative to the fileposition of the current assessmentTest file in the package folder structure.The assessmentTest description may contain additional optional data specifying complex ordering, scoring, andpresentation rules [QTI Info 2.1].The XML description of the section is shown in Code Listing 7.6.Code Listing 7.6: Example PARCC Assessment Section Element XML Document000102030405060708Example Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 00-05: Namespace and schema references (assessmentSection specific) Lines 06-07: References to the items in the sectionV 0.65: Public Draft 20130912 199

ExchangePARCC Item Development Technical GuideNote that the XML namespace URI of the assessmentSection found in the xmlns attribute of the assessmentSectionelement (line 03), is distinct from the namespace URI used for the assessmentTest.The two assessmentItemRef elements point to assessmentItem XML resources.The assessmentSection description may contain additional optional data specifying rubric blocks, complex ordering,scoring, and presentation rules [QTI Info 2.1].Item VariantsA variant of an item (i.e., an alternative representation, e.g., a language translation, media alternative, platformalternative) is defined by declaring the relationship between the original item and the variant in the manifest.Code Listing 7.7 illustrates a Spanish-language variant (B) of an item (A).Code Listing 7.7: Example Variant XML Document Fragment0001020304050607080910111213141516171819202122232425262728textualesExample Validated: not validatedXML: APIP Schema: Rendering: Behavior: Response: Accessibility: In the example: Lines 01-19: The original (A) item descriptiono Line 02: File declaration link to locate the original resource XML document in the folder structureo Lines 03-08: The metadata for the original itemo Line 09: Declaration of the variant relationshipo Line 10-19: Description of the variant using AfA DRD metadata [AfA DRD 09]200 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Lines 20-28: The variant (B) item descriptiono Line 21: File declaration link to locate the variant resource XML document in the folder structureo Lines 22-27: The metadata for the variantIn the original item, the identifierref attribute of the variant element points to the identifier of the variant item.The metadata for both the original and the variant must be present for a PARCC item. The additional variant itemmetadata that expresses how the variant is relaed to the original is defined using Access For All Digital ResourceDescription Metadata [AfA DRD 2.0].Item PackagingAs noted in the general description of a package, an item can include assets (with corresponding source material),rubric block files, companion materials, a preview, developer information and references to shared assets. Theremay be variants of an item or resource.Figure 7.14 illustrates an item with most of the possible item features. The item includes The item (I01) Two item-specific assets (A01, A02) A rubric block (RB01) A shared asset (SA03) A companion material (C01) An item preview (P01) An item developer file (D01) A source media file for an item-specific asset (M-A02 for asset A02) An alternative an the item-specific asset (V-A01 for asset V01) An alternative for the item as a whole (V-I01)I01V-I01V-A01A01 A02 SA03 RB01 C01 P01D01M-A02Figure 7.14: Sample PARCC APIP ItemFigure 7.15 illustrates the corresponding content package manifest structure.Manifestimsmanifest.xmlItem-I01.xmlItem-V01.xmlasset-I01-A01asset-I01-A02asset-shared-SA03asset-rubric-RB01companion-I01-C01preview-I01-P01developer-I01-D01master-I01-MA02asset-I01-VA01Figure 7.15: Sample PARCC APIP Item Manifest StructureFigure 7.16 illustrates the content package zip file and folder structure. The package includes 12 files.V 0.65: Public Draft 20130912 201

ExchangePARCC Item Development Technical Guidethe manifest XML file for the itemthe assessment item XML files in its own foldero two (2) asset files in the item foldero the rubric block file in the item foldero the asset variant in the item foldero the companion material file in a folder within the item foldero the preview in a folder within the item foldero the developer information file in a folder within the item foldero the source media for one of the assets in a folder within the item folderthe shared resource asset in the shared resources folderthe alternative item XML file in its own folderimsmanifest.xmlitemsitem-I01Item-I01.xmlasset-I01-A01asset-I01-VA01asset-I01-A02asset-I01-A02companionmaterialscompanion-I01-C01previewpreview-I01-P01developerinfodeveloper-I01-D01sourcemediamaster-I01-MA02item-V01Item-V01.xmlresourcesasset-shared-SA03Package .zipFigure 7.16: Sample PARCC APIP Item .zip File and Folder StructureThe example does not include source media for a shared asset. Source media for a shared asset would be placed in asource media (sourcemedia) folder in the shared resources (resources) folder.The example does not include source media for the item variant asset. The source media for the variant asset wouldbe placed in the source media (sourcemedia) folder in the item folder along with the other source media files for theitem.202 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange PARCC APIP Manifest ElementsPackage manifest may include specific elements. Elements used with PARCC manifest include: manifest [CP Info 1.2: § 6.4.1] dependency [CP Info 1.2: § 6.6.4] file [CP Info 1.2: § 6.6.3] File metadata [CP Info 1.2: § 6.7] Manifest metadata [CP Info 1.2: § 6.4.2] organizations [CP Info 1.2: § 6.5] resource [CP Info 1.2: § 6.6.2] Resource metadata [CP Info 1.2: § 6.7] resources [CP Info 1.2: § 6.6.1] variant [CP Info 1.2: § 6.8] AfA metadata [AfA DRD 09: § 6.2]Any APIP packaging element not listed is permitted unless formally excluded elsewhere.A summary of each of the elements follows. For each element: Definition: A narrative description of the element. Type: The type of the element (APIP CP, PARCC APIP CP profile, RTTA APIP CP profile). Container: The container elements that holds the element. Attributes: The list of element attributes (any attribute not listed is permitted unless formally excludedelsewhere, e.g., template attributes). For each attribute:o if the attribute is optional or if the attribute is required.o Name of the attribute.o Type of the attribute.o Acceptable attribute values.o Default attribute value if the attribute is not present.o Notes about the attribute Elements: The list of subelements included in the element (any element not listed is permitted unlessformally excluded elsewhere). Within the element, the subelements must appear in the order listed. Theelements, their attributes and any contained subelements are detailed elsewhere in the list. For eachelement:o if the element is optional, if the element is required or if PARCC guidelines exclude useof the element.o Name of the element.o Number of times the element can occur. If empty, only one occurrence is permitted.o Ordering of the elements when there are multiple instances. If empty, the elements are notordered.o Notes about the subelement. Notes: Notes about the element.V 0.65: Public Draft 20130912 203

ExchangePARCC Item Development Technical GuideElement manifestDefinition The description of the package.Type APIP CP [CP Info 1.2: § 6.4.1]Container Root imsmanifest.xml document in package zip file.Attributes Attribute Type Value Default Notes identifier identifier any noneElementsElement Number Order Notes(ordered) metadataSee element details organizationsSee element details resourcesSee element detailsNotesMetadata is manifest metadata.Element dependencyDefinition The identifiers of the dependencies of a resource.Type APIP CP [CP Info 1.2: § 6.6.4]Container resourceAttributes Attribute Type Value Default Notes identifierref identifier any noneElementsElement Number Order Notes(ordered)NoneNotesElement fileDefinition The description of a file resource.Type APIP CP [CP Info 1.2: § 6.6.3]Container resourceAttributes Attribute Type Value Default Notes href URI any noneElementsElement Number Order Notes(ordered) metadataSee element detailsNoneNotesMetadata is file metadata.Element metadata (File)Definition The metadata for a file.Type APIP CP [CP Info 1.2: § 6.7]Container fileAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) LOM MetadataNamespaced elementsNotes Specific required LOM metadata fields for a file are defined in .204 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Element metadata (Manifest)Definition The metadata for a manifest as a whole.Type APIP CP [CP Info 1.2: § 6.4.2]Container manifestAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) schemaContains a value from themetadata type schemavocabulary schemaversion Contains the value 1.0.0 LOM MetadataNamespaced elements Accessibility MetadataNamespaced elements QTI MetadataNamespaced elements CCCSS MetadataNamespaced elementsNotesSpecific required LOM, accessibility, QTI and curriculum metadata fields for a manifest aredefined in .Element organizationsDefinition Organization structures in the manifest – not used.Type APIP CP [CP Info 1.2: § 6.5]Container manifestAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered)NoneNotesThe element must be present in the manifest but must be empty.Element resourceDefinition The description of one resource in the package.Type APIP CP [CP Info 1.2: § 6.6.2]Container resourcesAttributes Attribute Type Value Default Notes identifier identifier any none type type any none APIP resource type href URI any none Resource location in packageElementsElement Number Order Notes(ordered) metadataSee element description file [0..*] See element description dependency [0..*] See element description variant [0..*] See element descriptionNotesMetadata is resource metadata.V 0.65: Public Draft 20130912 205

ExchangePARCC Item Development Technical GuideElement metadata (Resource)Definition The description of the collection of resources in the package.Type APIP CP [CP Info 1.2: § 6.7]Container resourceAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) LOM MetadataNamespaced elements Accessibility MetadataNamespaced elements QTI MetadataNamespaced elements CCCSS MetadataNamespaced elementsNotesSpecific required LOM, accessibility, QTI and curriculum metadata fields for a resource(resource specific) are defined in .Element resourcesDefinition The description of the collection of resources in the package.Type APIP CP [CP Info 1.2: § 6.6.1]Container manifestAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) resource [0..*] See element descriptionNotesElement variantDefinition The description of a variant alternative for a resource.Type APIP CP [CP Info 1.2: § 6.8]Container resourceAttributes Attribute Type Value Default Notes identifier identifier any none identifierref identifier any none Reference to the variantElementsElement Number Order Notes(ordered) metadataSee element descriptionNotesMetadata is access for all metadata.Element metadata (Access for All)Definition The metadata for a variant.TypeAPIP CPContainer variantAttributes Attribute Type Value Default NotesNoneElementsElement Number Order Notes(ordered) AfA DRD metadataNamespaced elementsNotes AfA DRD [AfA DRD 09] metadata fields for a variant are defined in .206 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange PARCC APIP Assessment Test ElementsPackage assessmentTest XML documents may include specific elements. Elements used with PARCC assessmenttest include: assessmentTest [QTI Info 2.1: § 11] testPart [QTI Info 2.1: § 11.1] assessmentSectionRef [QTI Info 2.1: § 11.2]Any APIP assessment test element not listed is permitted unless formally excluded elsewhere.A summary of each of the elements follows. The summary follows the format for manifest elements.Element assessmentTestDefinition The description of a test containing multiple test parts.Type APIP QTI [QTI Info 2.1: § 11]Container Root xml document in a test file. Referenced as a resource in the manifest.Attributes Attribute Type Value Default Notes identifier identifier any none title string any noneElementsElement Number Order Notes(ordered) outcomeDeclaration [0..*] Not used in PARCC tests timeLimits [0..1] Not used in PARCC tests stylesheet [0..*] Not used in PARCC tests testPart [1..*] See element description outcomeProcessing [0..1] Not used in PARCC tests testFeedback [0..*] Not used in PARCC testsNotesElement testPartDefinition The description of a test part containing multiple sections.Type APIP QTI [QTI Info 2.1: § 11.1]Container assessmentTestAttributes Attribute Type Value Default Notes identifier identifier any none navigationMode navigation linear none Verify submissionMode submission any none VerifyElementsElement Number Order Notes(ordered) itemSessionControl [0..1] Not used in PARCC tests timeLimits [0..1] Not used in PARCC tests assessmentSectionRef [1..*] See element description testFeedback [0..*] Not used in PARCC testsNotes .Element assessmentSectionRefDefinition The description of the link to a section within the test.Type APIP QTI [QTI Info 2.1: § 11.2]Container testPartAttributes Attribute Type Value Default Notes identifier identifier any noneV 0.65: Public Draft 20130912 207

ExchangePARCC Item Development Technical GuideElementElements(ordered)NotesassessmentSectionRef href URI any none Section location in packageElement Number Order NotesNonePARCC APIP Assessment Section ElementsPackage assessmentSection XML documents may include specific elements. Elements used with PARCCassessment section include: assessmentSection [QTI Info 2.1: § 11.2] assessmentItemRef [QTI Info 2.1: § 11.2]Any APIP assessment section element not listed is permitted unless formally excluded elsewhere.A summary of each of the elements follows. The summary follows the format for manifest elements.Element assessmentSectionDefinition The description of a section containing multiple items.Type APIP QTI [QTI Info 2.1: § 11.2]Container Root xml document in a test file. Referenced as a resource in the manifest.Attributes Attribute Type Value Default Notes identifier identifier any none required boolean any false fixed boolean any false title string any none visible boolean any none keepTogether boolean any trueElementsElement Number Order Notes(ordered) selection [0..1] Not used in PARCC tests ordering [0..1] Not used in PARCC tests rubricBlock [0..*] Not used in PARCC tests assessmentItemRefassessmentSectionRef[0..*] Contains either elementSee element descriptionNotes208 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Element assessmentItemRefDefinition The description of the link to an item within the section.Type APIP QTI [QTI Info 2.1: § 11.2]Container assessmentSectionAttributes Attribute Type Value Default Notes identifier identifier any none required boolean any false fixed boolean any false href URI any none Item location in package category identifier any noneElementsElement Number Order Notes(ordered) timeLimits [0..1] Not used in PARCC tests weight [0..1] Not used in PARCC testsNotesElement assessmentSectionRefDefinition The description of the link to a section within the section.Type APIP QTI [QTI Info 2.1: § 11.2]Container assessmentItemAttributes Attribute Type Value Default Notes identifier identifier any none href URI any none Item location in packageElementsElement Number Order Notes(ordered)NoneNotesPARCC Entity Naming ConventionsThere are names, identifiers, titles, etc. for items, accessibility information, metadata and packaging elements andresponse processing templates. Specific PARCC guidelines for names and identifiers are summarized below inTable 7.1. These guidelines insure that different independently developed items can be mix in test and stored in thePARCC item bank without conflicts. Specific entities and the associated attribute that is has a name/identifier are listed in the table, or generalcategories (in italics) are shown when the same convention applies to all entities in the category. Guidelines are given for the uniqueness of the name/identifier:o PARCC unique: the identifier or name must be unique in the scope of all PARCC entities; a DCEUUID [UUID] meets the uniqness criteriao Item unique: the identifier or name must be unique to the item. Another item may use the sameidentifier; a more unique scope may be usedo Package unique: the identifier or name must be unique to the package. Another package may usethe same identifier; a more unique scope may be used Guidelines are given for nam/identifier format. Notes describe how the name/identifier value is related to the value of another entity. An expression of theform xxx indicates that the xxx entity value of some other entity matches the value of the entity.Item developers may select names/identifiers, etc., of their choice for any entity not listed.V 0.65: Public Draft 20130912 209

ExchangePARCC Item Development Technical GuideTable 7.1: PARCC Entity Naming ConventionsObject Attribute Uniqueness Form NotesItemassessmentItem identifier PARCC TBD Must match one of the item’smetadata identifiers.accessibilityInfo / accessElement /contentLinkInfo /qtiLinkIdentifierRef title None N/A Must match item metadata titlefolder name PARCC TBD Should be similar to identifierhref/file name PARCC path+file File should be similar to identifierhref includes appropriate pathresponseDeclaration identifier Item TBD interaction / responseIdentifier outcomeDeclaration identifier Item TBD RPT itemBody id Item TBD accessibility content item content element id Item TBD accessibility content any interaction id Item TBD accessibility content any interactionsubelementidentifier Item TBD Response mappingsid Item TBD accessibility content Item Accessibility InformationaccessElement identifier Item TBD inclusionOrder / elementOrder /identifierRef accessibilityInfo contentLinkIdentifier Item TBD accessibilityInfo / accessElement /contentLinkInfo /apipLinkIdentifierRef relatedElementInfo identifier Item TBDcompanionMaterial filehref Item TBDdigitalMaterial filehref Item TBDMetadataEntity ID identifier PARCC TBD Any LOM ID (multiple)Relation Resource identifier PARCC TBD related resource IdentifierPackagezip file filename PARCC TBDroot test folder none fixed testroot sections folder none fixed sectionsroot items folder none fixed itemsitem companion none fixed companionmaterialsmaterials folderitem preview folder none fixed previewitem source media none fixed sourcemediafolderdeveloper info folder none fixed developerinforoot resources folder none fixed resourcesresources source none fixed sourcemediamedia folderroot RPT folder none fixed rptemplatesroot schema folder none fixed xsds210 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideExchange Object Attribute Uniqueness Form Notesmanifest identifier PARCC TBDXML document none fixed imsmanifest.xmlfilenameassessmentTest identifier PARCC TBDtitle None N/Afolder PARCC TBD Should be similar to identifierfilename PARCC path+file File should be similar to identifiertestPart identifier Test TBDXML document PARCC path+file File should be similar to identifierfilenameassessmentSection identifier Test TBDtitle None N/Afolder PARCC TBD Should be similar to identifierfilename PARCC path+file File should be similar to identifierassessmentSectionRef identifier Test TBD Matches a section resourcefile/href PARCC path+file File should be similar to identifierhref includes appropriate pathassessmentItemRef identifier PARCC path+file matches an item resourceresource identifier PARCC TBD dependency / identifierref variant / identifierref file/href PARCC path+file File should be similar to identifierhref includes appropriate pathvariant identifier PARCC TBDResponse Processing Templatetemplate file filename PARCC TBDPARCC Versioning ConventionsPARCC entities are managed and versions, including items, assets, companion materials and response processingtemplates. The guidelines for versioning are summarized below. Any new version of an item or asset should be given a new version number.o The format for PARCC version number is one to three non negative integers separated by periods Any substinative change, i.e., the form, rendering or behavior of the item would be different for the student,implies a new version The metadata for the item or asset must contain the appropriate version number The relation metadata for the new version should link via an isversionof relation to the prior versiono Reciprocal relations in the metadata (hasversion) are not requiredV 0.65: Public Draft 20130912 211

ValidationPARCC Item Development Technical GuideValidation PARCC is committed to using applicable industry-recognized, open-licensed interoperability standards includingstandards for assessment items, assessment and results data, accessibility, student data, and APIs. As described inthis Guide, PARCC has placed additional conditions on assessment items. Validation and conformance testing areused to ensure that PARCC items and systems are interoperable and conform to the required interoperabilitystandards and PARCC guidelines.Items must be validated to conform to the PARCC guidelines and the underlying RTTA profiled APIPspecifications. Item developers must validate items as part of their internal QA/QC processes and prior to deliveringitems to PARCC. Additionally PARCC may validate any items transmitted from the item developer prior to finalacceptance.Validation guidelines address: RTTA and PARCC APIP validation, including:o QTI validationo Item Accessibility validationo Test Client Accessibility validationo Embedded Support validationo Content Packaging validationo Metadata validation Editorial and Style validation Rendering validation Behavior interaction validation Response Processing validation Accessibility validationValidation is performed, in part, through available conformance testing software and manual inspection. Itemdevelopers are reminded that conformance testing does not fully validate all features and item semantics. Additionalmanual validation is required.The Guide does not address validation and conformance testing of any software component of the assessmentsystem, e.g., item bank import/export, and test client behavior.At this time, PARCC does not require formal APIP or QTI conformance certification [APIP Conformance 1.0].Unless otherwise noted, all XML documents must use the RTTA APIP Profile Schemata specified in the Schematasection for validation.Note: PARCC XML documents using the RTTA APIP Profile will not validate against the current APIP Profile.Note: IMS APIP Validator [APIP Validator] RTTA Profile is not the RTTA profile referred to in this Guide.PARCC XML documents using the RTTA APIP Profile will not validate against the IMS RTTA Profile.PARCC APIP ValidationEach item must be validated against the PARCC and APIP guidelines for accessibility , device and embeddedsupports , encoding (QTI) , metadata and exchange (Content Packaging) . Validation is performed in partusing the available APIP validator [APIP Validator] (validation against the APIP v1.0 Package Core Profile) and inpart through inspection and independent sematic testing of the item XML representation (the conformance test suitecurrently only tests the structure of the XML document, not the semantics or resulting behavior of the item).212 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideValidation Tables 8.1 – 8.5 list the set of QTI, Item Accessibility, Test Client Support, Embedded Support, and Metadata andPacking Features used in PARCC items and processes (alphanumeric codes in the first column align with APIPlabels for QTI, accessibility and packaging features). Features that must be validated are indicated with a in the“PARCC Validation” column of the tables. Syntactic XML validation performed by the APIP conformance testsuite is indicated with a in the “Test Suite Features” column of the tables (derived from [APIP Conformance 1.0:§ 3])Items in Table 8.3: Test Client Validation and Table 8.4: Embedded Supports Validation are functions of the testclient and are not defined in the item, content metadata or content package. Validation processes for these featuresare described in the Behavior Validation section below.Table 8.1: PARCC APIP QTI ValidationQTI Feature PARCC Validation Test Suite FeatureTestsT1 Outcome Declaration T2 Time Limits T2 Stylesheet T4 Test Parts T5 Item Session Control T6 Time Limits T7 Sections T8 Test FeedbackT9a Outcomes Processing - Common Cartridge T9b Outcomes Processing - Full T10 Test FeedbackSessionsS1 Item Session ControlS2 Time LimitsS3 SelectionS4 OrderingS5 Rubric Block S6 IncludeS7 Items S8 Sections InteractionsQ1 Associate InteractionQ2 Choice Interaction Q3 Custom InteractionQ4 Drawing InteractionQ5 End Attempt InteractionQ6 Extended Text Interaction Q7 Gap Match InteractionQ8 Graphic Associate InteractionQ9 Graphic Gap Match InteractionQ10 Graphic Order InteractionQ11 Hotspot InteractionQ12 Hottext InteractionQ13 Inline Choice InteractionQ14 Match InteractionQ15 Media InteractionQ16 Order InteractionV 0.65: Public Draft 20130912 213

ValidationPARCC Item Development Technical GuideQTI Feature PARCC Validation Test Suite FeatureQ17 Position Object InteractionQ18 Selection Point InteractionQ19 Slider InteractionQ20 Text Entry InteractionQ21 Upload InteractionComposite ItemsItemsI1 responseDeclaration I2 outcomeDeclaration I3 templateDeclaration I4 templateProcessing I5 stylesheet I6 Item Body I7 HTML (Block) I8a Response Processing-Fixed Template I8b Response Processing-Full I9 Modal Feedback I10 Inline Feedback Content ElementsRubric BlocksItem FragmentsMathMLTable 8.2: PARCC APIP Item Accessibility Support Feature ValidationItem Accessibility Feature PARCC Validation Test Suite FeatureA1 Spoken: Text Only A2 Spoken: Text & Graphics A3 Spoken: Non-Visual A4 Spoken: Graphics OnlyA5 Spoken: Directions Only A6 Spoken: User PreferencesA7 Spoken: Screen Reader PreferencesBrailleBraille: ContractedBraille: UncontractedA8 Braille: Refreshable A9 Braille: User PreferencesA10 Tactile Tactile: Spoken FileTactile: Spoken TextTactile: Braille TextA11 Signing: ASL A12 Signing: Signed English A13 Item TranslationA14 Keyword Translation A15 Simplified LanguageC9 Language Learner GuidanceC10 Cognitive Guidance214 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideValidation Table 8.3: PARCC APIP Test Client Accessibility Feature ValidationTest Client Accessibility Feature PARCC Validation Test Suite FeatureB1 Magnification B2 Magnification: User PreferencesIncreased White SpaceB3 Reverse Contrast B4 Alternative Text & Background Colors B5 Alternative Colors, User PreferencesInvert ColorsB6 Color Overlay B7 Color Overlay: Color Preferences C1 Answer Masking C2 General Masking C3 Auditory CalmingC4 Additional Testing TimeC5 BreaksC6 Keyword Emphasis C7 Line Reader C8 Line Reader: Color PreferencesC9 Language Learner GuidanceC10 Cognitive GuidanceSpeech to TextRefreshable BrailleClosed CaptionsReduced AnswersNegatives RemovedChunkingScaffoldingHazardsTable 8.4: PARCC Embedded Support / Companion Materials Feature ValidationEmbedded Support Feature / Companion Materials PARCC Validation Test Suite FeatureD1 Calculator Calculator: Four FunctionCalculator: ScientificCalculator: GraphingCalculator: Full FunctionD2 Ruler Ruler: 1/8 th inchRuler: 1/4 th inchD3 Protractor CompassStraight EdgeD4 Reading Passage D5 Digital Companion / Digital Material D6 Physical Companion / Physical MaterialNote PaperNote PadGraph PaperWord Processing ToolV 0.65: Public Draft 20130912 215

ValidationPARCC Item Development Technical GuideEmbedded Support Feature / Companion Materials PARCC Validation Test Suite FeatureEquation EditorPopup GlossaryGraphic OrganizerDictionaryGlossaryThesaurusText AnnotationSpell CheckerWord PredictionVisual DictionaryDrawing ToolFormula ChartTable 8.5: PARCC APIP Metadata and Packaging ValidationMetadata / Packaging Feature PARCC Validation Test Suite FeatureP1 Test Instances P2 Section Instances P3 Item Banks P4 Item Instances P5 Manifest Metadata (LOM) P6 Resource Metadata (LOM) Resource Accessibility Metadata (RTTA)P7 Resource Metadata (QTI) P8 Curriculum Standards Metadata P9 Learning Tools Interop v1.1 Language, Editorial and Style ValidationEach item and all associated resources and assets must be validated against the Language, Editorial and Styleguidelines . Language, Editorial and Style validation must be performed through inspection of the item, either itssource XML or as rendered by a test client.PARCC may publish future guidelines for specific language, editorial and style validation tests and processes for anitem.Rendering ValidationThe rendering of an item in the test client must be checked to validate that the item layout and rendering iscorrect. Rendering validation must be performed through visual inspection of the item as rendered in a test client,and must be performed using the currently approved PARCC test clients.An image (screen capture) showing the item as rendered in the test client must be include with the item as an assetwhen the item is transmitted to PARCC. The image(s) are included in the package as a standalone resource for theitem. All images for an item should be in an item-level subfolder folder named preview in the package (more detailsabout including previews and other developer information with the image is presented in ). The image is listed asa resource in the manifest and should have a set of file metadata, including: Entity ID: The developer’s unique identifier assigned to the image; same as one of the item’s identifiers(LOM General.identifier)216 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideValidation Description: A description indicating that the file is a preview image and identifying the test client used tocapture the image (LOM General.description)Status Date: The timestamp when the preview was captured. (LOM LifeCycle.contribute.date)MIME Type: The MIME type of the file (LOM Technical.format; preferred media types are image/png,image/jpeg)Relationship: Relationship data indicating that the image is a preview of the item (ispreviewof). The itemshould include the reciprocal relationship in its metadata (haspreview)To Do: Verify how to include the image in the package, e.g., format, file name, metadata, …Item developers are encouraged to test item rendering in multiple test clients. Open source QTI implementationsmay be used to test validation and rendering. (Tools such as QTIWorks [QTIWorks] could be extended to supportAPIP validation and rendering; it currently only processes canonical QTI, LOM and CP namespaces.)PARCC may publish future guidelines for specific rendering validation tests and processes for an item.Behavior ValidationThe behavior of an item in the test client must be checked to validate that the item interactions operate asexpected. Behavior validation must be performed through observing interactions with the rendered item in a testclient, and must be performed using the currently approved PARCC test clients.PARCC may publish future guidelines for specific behavior validation tests and processes for an item.PARCC also requires that all approved test clients be independently validated using a common set of test items andprocesses. Test client validation is not described in this Guide.Response Processing ValidationThe behavior of an item in the test client must be checked to validate that the item response processing operateas expected. Response processing validation must be performed through checking item response processing andscoring with the rendered item in a test client, and must be performed using the currently approved PARCC testclients.PARCC may publish future guidelines for specific response processing validation tests and processes for an item.Accessibility ValidationThe behavior of an item in the test client must be checked to validate that the accessibility features and embeddedsupports , operate as expected. Behavior validation must be performed through observing interactions with therendered item in a test client, and must be performed using the currently approved PARCC test clients.PARCC may publish future guidelines for specific accessibility validation tests and processes for an item.PARCC also requires that all approved test clients be independently validated using a common set of test items andprocesses. Test client validation is not described in this Guide.V 0.65: Public Draft 20130912 217

GlossaryPARCC Item Development Technical GuideGlossaryAccess Element: This is the structure within APIP that is used to contain a single facet of the APIP accessibilityinformation. The alternative content for an item is defined using a number of access elements. Each access elementdefines the alternative content and identifies the part of the original QTI Item to which it refers. (From [APIP Terms1.0].)Accessibility Features: Accessibility features are available to all students (i.e., not limited to students with IEPs, 504plans, or ELs), but will be selected and “turned on” by a school-based educator prior to the assessment, based oneach student’s Personal Needs and Preferences (PNP) Profile. Accessibility features should be selected by schoolbasededucators (e.g., classroom teachers, and staff members of IEP teams, 504 plan teams, EL teams – ifapplicable) based on individual need and with input from the student and parent, where applicable.Accessible Portable Item Profile (APIP) Standard: The APIP Standard [APIP] provides assessment programs andquestion item developers a data model for standardizing the interchange file format for digital test items. Thestandard builds on the IMS Question and Test Interoperability (QTI) v2.1 Specification [QTI] and the IMS Accessfor All Personal Needs and Preferences (PNP) v2.0 Specification [AfA].Accommodation: Accommodations are assessment practices and procedures that change the presentation, response,setting, or timing and scheduling of assessments that are intended to provide equitable testing conditions for studentswith disabilities. Accommodations for English learners are practices and procedures that provide equitable accessduring instruction and assessments for ELs and provide a valid means for ELs to show what they know and can do.Accommodations are intended to provide support to students with developing English language proficiency in theclassroom and on state assessments in terms of their access to instructional or test content, interactions with content,and response to content. Once an EL becomes English proficient, the accommodation may no longer be necessary.Activate By Default: In the APIP Personal Needs and Preferences profile, many of the supports include theactivateByDefault tag. This means that the specified support should be actively running when the testing session isinitiated. For example, if a user had a magnification need, and activateByDefault = true for that user, when their testsession began, the testing interface would have the magnification turned on, not just available as an option. (From[APIP Terms 1.0].)Additional and Supporting Content: This term is specific to Mathematics content. The Additional and SupportingContent in a grade/course is determined by that grade level's Additional and Supporting Clusters as identified in thePARCC Model Content Frameworks for Mathematics [PARCC Math Frameworks].Analytic Writing: Writing that places a premium on using evidence while demonstrating logical integration andcoherence in order to inform/explain, convey an opinion, advance an argument, or simultaneously meet acombination of these purposes. Notably, narrative elements may also be included in analytic writing, butinformative/explanatory or opinion/argumentative elements must be included for a piece to be considered analyticwriting.Anchor Text: This term is relevant only for ELA-Literacy assessment components. An anchor text is the extendedtext used during the research simulation task in conjunction with the additional short texts read during the researchsimulation task. (See also: Extended Text.)Answer Reduction: This is the process by which the number of possible answers in a multiple-choice question isreduced. The content author must define which possible answers are to be removed and the order in which theremoval should take place. (From [APIP Terms 1.0].)APIP Interchange File: This is the ‘zip’ file that is used to contain one or more APIP Items and all of the associatedasset files, and the mandatory imsmanifest.xml file. This interchange file is a profiled form of the ‘zip’ file definedas a content package in the Content Package Specification [CP Info 1.2]. (From [APIP Terms 1.0].)218 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossaryAPIP Item: An APIP Item is a collection of QTI assessmentItems that provides an accessibility enabled QTIassessmentItem. The multiple forms provide alternative renderings of the basic assessmentItem to reflectconfiguration of the item for particular learner accessibility preferences. (From [APIP Terms 1.0].)APIP Test: An APIP Test is equivalent to a QTI assessmentTest. An APIP Content Package may contain a teststructure. (From [APIP Terms 1.0].)APIP Content Package: The APIP profile of a content package. (See also: Content Package.)Assessment Content Repository: The PARCC data repository that stores and retrieves data regarding blueprints,tests, items, assets, and metadata. (See also: Item Bank.)Assessment Interoperability Framework: A set of data interoperability standards that support the assessmentsystems being developed by the Race to the Top Assessment (RTTA) Consortia [AIF].AssessmentItem: See QTI Assessment Item.AssessmentTest: See QTI Assessment Test.Asset: In a test item, additional supporting text, multimedia, or images in digital form.Assigned Support: In the APIP Personal Needs and Preferences Profile many of the supports include theassignedSupport tag. When included for the support, the tag is considered true by default. It means that the studentrequires this support during assessment. If a profile includes the support tag, but not the assignedSupport tag, theassumption is that the support should be provided. The possibility of an assignedSupport=false is included in theevent that the user profile wanted to affirm that the user is specifically not to use a support during testing, mostlikely changing from a previous use of the support. (From [APIP Terms 1.0].)Associate Interaction: Structured content (text, graphics and media elements) that presents the student with anumber of choices and allows the student to create associations between the choices.Bar Graph Item: The bar graph (BG) item …Blueprint: A blueprint is a guide for indicating the content and structure of an assessment. It is an exact anddetailed chart designating the minimum score points supporting each claim. A blueprint may designate the totalnumber of tasks or items for any given assessment component. There will be separate blueprints for EnglishLanguage Arts/Literacy and for Mathematics for each assessment component for each grade level. (See also: TestSpecification.)Braille Text: This is the text that is rendered as Braille using an appropriate piece of hardware (refreshable Brailledisplay). (From [APIP Terms 1.0].)Choice Interaction: Structured content (text, graphics and media elements) that presents a set of choices to thestudent. The student task is to select one or more of the choices.Chunk: Chunking is designed to assist students in processing information by breaking passages into smallersections, each of which focus on a specific topic or element of information. The chunk is used with extended textpassages and specifies how a passage is to be divided into shorter segments, chunks, when displayed for a student.Chunking is reserved for future uses in APIP. It is not used within the APIP v1 profile. (From [APIP Terms 1.0].)Claim: A statement about students indicating what they know and can do. Claims are supported by evidencegathered from student responses. The claims about students’ knowledge and skills are developed according to thepurpose of the assessment (e.g., assessing progress or end-of-course knowledge) and the domain covered therein.When the purpose is summative, claims are written to represent the set of skills and knowledge that students mustacquire by the end of a period of instruction, such as a school year. (See also: Master Claim, Reporting Categories,Supporting Reporting Categories.)V 0.65: Public Draft 20130912 219

GlossaryPARCC Item Development Technical GuideCommon Education Data Standards (CEDS): Common Education Data Standards [CEDS] are the most commoneducation data elements used to support the effective exchange of data within and across states, as studentstransition between educational sectors and levels, and for Federal reporting. This common vocabulary enables moreconsistent and comparable data to be used throughout all education levels and sectors necessary to support improvedstudent achievement. The standards are being developed by the National Center for Education Statistics (NCES)with the assistance of a CEDS Stakeholder Group that includes representatives from states, districts, institutions ofhigher education, state higher education agencies, early childhood organizations, federal program offices,interoperability standards organizations, and key education associations and non-profit organizations. CEDS is avoluntary effort and will increase data interoperability, portability, and comparability across states, districts, andhigher education organizations.Companion Materials: Companion Materials are materials and tools that the examinee is expected to work withwhile performing an item. These materials and tools may include a reading passage, a primary document, a periodictable, ruler, protractor, calculator, etc. Companion materials information also identifies any lookup dictionariesassociated with the item to provide definitions or translations of specific words within an item. The companionmaterials information is intended to be used by a test client interface to make the requisite material available whenthe item is presented or to identify the appropriate definition or translation of item content when the examineerequests such information. (From [APIP Terms 1.0].)Complexity: The intended cognitive demand of an item or task from a student in understanding and responding to it.For example, an item or a task requiring students to predict a phenomenon based on data presented in a graph will beexpected to be more complex (or more challenging, or more cognitively complex) than an item or task requiringstudents to describe the same data presented in the graph. (See also: Item Difficulty.)Complex Drag and Drop Item: The complex drag and drop item …Complex Hot Spot Item: The complex hot spot item …Composite Graph Item: The composite graph (CMG) item … One version of the item uses lines and another usesshapes.Composite Item: An item that contains more than one point of interaction. Composite items may contain multipleinstances of the same type of interaction or have a mixture of interaction types. (See also: Simple Item.) (From[APIP Tech 1.0].)Constructed Response Item: The constructed response (CR, PCR) item … A version of the item includes use of theequation editor (EE).Content Information: Content information provides information about the contents of the item that are to bepresented to an examinee assuming no access needs have been defined for that examinee. This information includesthe item type, the prompt, media associated with the item (e.g., figures, tables, graphs), response options, correctresponse, scoring rule, etc. The content information component specifies the information that forms the item andadditional information used by a test engine to score an item. The APIP content information is based on QTIspecifications [QTI]. (From [APIP Terms 1.0].)Content Link Information: This is the description of how the new APIP alternative content is linked to the originalQTI assessmentItem content. The link to the control structures in the assessmentItem is via the use of the ‘id’attribute (this is an optional attribute for all of the HMTL content features in QTIv2.1). Each new APIP contentfeature can itself have alternative content features, i.e., recursive. In the latter case the content link information usesthe value of the contentLinkIdentifier attribute that must be assigned to every alternative piece of content. Thecontent link can refer to either the entire structure identified or, in the case of text, to some substructure, e.g., acharacter, a word or a string of characters. (From [APIP Terms 1.0].)Content Package: The key exchange object defined in the Content Packaging (CP) Specification [CP Info 1.2]. Aprofiled version of CP is used in IMS QTIv2.1 for the exchange of assessmentItems and assessmentTests. It is the220 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossaryprofiled version of CP for QTI that is further profiled in APIP to create the APIP Interchange File. (From [APIPTerms 1.0].)Control Information: This is the collection of needs and preferences for how to configure alternative access systemsfor controlling a device. In APIPv1.0, none of the original AfA PNP features are supported, i.e., only the newfeatures added by APIP are permitted. (From [APIP Terms 1.0].)Custom Interaction: An item interaction defined in the QTI Specification [QTI Info 2.1] as an extension. (From[PCI].)Device: Digital tools that students may use to respond to the PARCC assessments. The use of this term is meant toimply no preference for a specific platform. PARCC‘s expectation is that the assessment will be delivered on thewidest possible range of platforms. (See also: Test Client.)Diagnostic Assessment: Diagnostic assessments are designed to measure students’ strengths and weaknesses interms of specific standards or knowledge and skills. These assessments are developed to inform instructionalstrategies, remediation, and intervention. Development of diagnostic assessments requires a theoretical frameworkthat explains how students learn different skills and knowledge, and how such skills and knowledge are interrelated.Results of such assessments inform what particular standards students need to master in order to master the next setof knowledge and skills within their reach.Display Information: This is the AfA PNP v2.0 information that is used to describe the user preferences fordisplaying information, i.e., the way in which the content should be rendered for the user. (From [APIP Terms 1.0].)Drag and Drop Item: The drag and drop (DD) item …Drawing Interaction: A graphic image and a common set of tools that is presented to the student. The student canuse the tools to manipulate the image.Embedded Support: An embedded support is a tool, support, scaffold, or preference that is built into the assessmentsystem that can be activated by any student at his or her own discretion. Embedded supports are Universal Designfeatures that are expected to benefit a diversity of students and are available to all students, either onscreen, stored ina toolbar, or accessible through a menu or control panel, as needed. When a support is made available to only asubset of users based on their learner profile, it is considered an accessibility feature. (See also: Student Toolbox,Support.)Evidence: Any type of information gathered from student responses supporting claims about student performance inreference to the construct being measured in the assessment. Evidences are derived from observable studentbehavior(s) in response to assessment items or tasks. Each evidence is linked to a particular claim.Evidence Statement: Statements that indicate what students must demonstrate in an assessment in support of theclaims about the students in that assessment. Evidence statements describe the observable student behavior(s) orwork product(s) that support claims about students’ mastery of particular standards. In other words, evidencestatements describe what one can point to, highlight, or underline in a student work product that substantiates thatthe standard has been mastered by that student. Evidence statements must be aligned with particular standards. (Seealso: Claim.)Evidence-Based Selected Response (EBSR): This term is relevant only for ELA-Literacy assessment components.This term refers to a specific item model where students are required to answer a two-part, selected-responsequestion. The first part of this item model is a traditional selected-response item. In the second part of the item, thestudent is required to demonstrate the ability to cite evidence from the text in determining the response to the firstpart of the item. To demonstrate this ability, students may be asked to grid in the line(s) of text the student wishes tocite or alternatively to choose which from a set of lines of text presents the best citation.Evidence-Centered Design (ECD): Evidence-Centered Design is a process of assessment development that involvesgathering, organizing, and transforming information in a variety of representational forms within the framework of aV 0.65: Public Draft 20130912 221

GlossaryPARCC Item Development Technical Guideclearly articulated assessment argument. It includes the following: identifying potential claims about whatconstitutes student proficiency; identifying evidence (what students might say, do, or produce that will constituteobservable evidence for the claims); and identifying the kinds of situations or tasks that might produce this evidence.Extended Text: This term is relevant only for ELA-Literacy assessment components. Text that is designated as anextended text is text that is closest in length to the maximum length listed for a given grade level. As part of theresearch simulation task, one extended text is used in conjunction with additional short texts. In this case, theextended text is referred to as the extended anchor text. (See also: Anchor Text, Short Text.)Extended Text Interaction: Structured content (text, graphics and media elements) that provides the student with amechanism to enter a block of text. Note: Extended Text for ELA-Literacy is not the same as the extended textresponse in an extended text interaction.File Metadata: This is the metadata defined for a file within the manifest of a content package. Each file can haveits own metadata description. The metadata for a file should be based upon a profile of the IEEE LOM [LOM, LOMCorrigendum] metadata. (From [APIP Terms 1.0].)Fill in the Blank Item: The fill in the blank (FIB) item … There are three versions of the item: unconstrainedresponse, response constrained to using a specific character set (e.g., digits) or a response created using the equationeditor (EE).Fraction Model Item: The fraction model item …Free-Form Graphic Organizer Item: The free-form graphic organizer item …Function Graph Item: The function graph (FG) item …Gap Match Interaction: Structured content (text, graphics and media elements) that contains a number of gaps thatthe student can fill from an associated set of choices.Geometric Transform Item: The geometric transform item …Graphic Associate Interaction: A graphic interaction with an associated image with choices indicated as areas onthe image. The student is to order the areas with each other.Graphic Gap Match Interaction: A graphic interaction with an associated image that contains a number of gapsindicated as areas on the image and an additional set of gap choices that are defined outside the image. The studentcan associate the images with the gaps.Graphic Order Interaction: A graphic interaction with an associated image with choices indicated as areas on theimage. The student is to order the areas.Gridded Response Item: The gridded response (GR) item …GUID: A label (typically a string of characters) that is unique within the scope of all PARCC identifiers. To beused as an identifier, a GUID must be associated with something.Guidance: This is the container for the instructions on how to render information that is subjected to guidance(Language Learner Guidance or Cognitive Guidance). This is used for students who require assistance identifyingthe key components of an item. Guidance presents additional information or cues to the examinee. A guidancesupport is applied to item content and specifies to the test delivery system both the additional information that is tobe displayed for the examinee and the content with which the guidance is associated. When the item is presented onscreen, the test delivery system may automatically display guidance content associated with the item or may displayguidance content on-demand, depending on the specifications provided in the student access profile. (From [APIPTerms 1.0].)222 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossaryHand Scoring: The use of trained human judges to assign ratings to student’s work on the writing prompts or on theperformance-based tasks in ELA-Literacy and Mathematics. (See also: Key-Based Scoring, Rule-Based Scoring.)Hot Spot Interaction: A graphic interaction with an associated image with choices indicated as areas on the image.The student is to select one or more of the areas.Hot Spot Item: The hot spot (HS) item …Hot Text Interaction: Structured content (text, graphics and media elements) that presents a set of choices to thestudent represented as selectable runs of text embedded within a surrounding context. The student is to select one ormore of the choices.Identifier: An identifier is the association of a name with something to be identified. A name may only beassociated with one thing at any time, and the name is said to identify the thing. (From [PILIN].)Inclusion Order: Inclusion Order specifies the order in which accessibility elements are to be presented to anexaminee with a given category of access needs. The six categories of access needs for which an inclusion order isspecified include: 1) Braille presentation; 2) Spoken, Text Only presentation; 3) Spoken, Text & Graphicspresentation; 4) Spoken Non-visual presentation; 5) Graphics Only spoken presentation; 5) American SignLanguage presentation; and 6) Exact Signed English presentation. For each category of access needs, the inclusionorder also specifies whether the accessible content element is to be presented by default, where accessibilityelements are presented to an examinee from the beginning to the end of their specific inclusion order, withoutstopping between elements and requiring the examinee to reinitiate playback. Some categories (Spoken Text Only,Spoken Text & Graphics, Spoken Graphics Only, ASL, Signed English) also include an “…onDemandOrder”. Ondemand orders include content that is presented to the examinee only at the specific request of the examinee. Anexample might be a label for a diagram, where the examinee would not want the label presented to them whenunderstanding an item’s stimulus, prompt, or responses; but the examinee would access this information whenexamining the diagram when considering their response. For these six categories of access needs, defaultpresentation and on-demand presentation are described in greater detail in the Examinee Access Information section.(Note: The number of categories is as listed in [APIP Terms] and is incorrect.) (From [APIP Terms 1.0].)Inline Choice Interaction: A span of text that presents the student with a number of choices, each of which are asimple piece of text, and allows the student to select one of the choices.Inline Choice Item: The inline choice (IC) / drop down item …Integrative Task: This term is specific to Mathematics content. A task that clearly codes to a cluster heading,without clearly coding to any single standard in the cluster; or a task that clearly codes to a domain or grade/course,without clearly coding to any single cluster in the domain or grade/course. This might arise from a task thatincorporates several individual standards as identifiable component parts, or it might arise from synthesis ofindividual standards. Not every cluster or domain will be assessed using integrative tasks. The presence ofintegrative tasks in the assessment design is not intended to permit loose interpretations of the standards. Such tasksare used where necessary to measure plausible and immediate implications of what is written in the standards,without ever slipping into the imposition of additional requirements.Interaction: Interactions allow the student to interact with the item. Through an interaction, the student selects orconstructs a response. (From [QTI Info 2.1].)Interaction Type: One of the available interactions.Interactive Number Line Item: The interactive number line item …Interoperability: The ability of two or more systems or components to exchange information and to use theinformation that has been exchanged. Interoperability must be distinguished from Open Standards. Although thegoal of each is to provide effective and efficient exchange between computer systems, the mechanism foraccomplishing that goal is very different. Open Standards imply interoperability ab-initio, i.e., by definition, whileV 0.65: Public Draft 20130912 223

GlossaryPARCC Item Development Technical Guideinteroperability does not, by itself, imply wider exchange between a range of products, or similar products fromseveral different vendors, or even past or future revisions of the same product.Item: An individual test question or activity that students complete. All items are assumed to be scored to allowstudents to earn points to be attributed to a claim.Item Accessibility: The degree to which items/tasks, stimuli, passages, performance tasks, online tools, and graphicsare made available to and appropriate for as many test-takers as possible, beginning in the initial test design stagesand continuing throughout the test development process. Item design increases access for all participating students,not just those with special needs or limited English proficiency. Item writers must consider accessibility in the textand graphical presentation of the item/task' students’ interaction with the item/task; student navigation betweenitems, screens, and sections; and mode of student responses.Item Bank: A data repository that stores and retrieves data regarding blueprints, tests, items, assets, and metadata.Item Calibration: This is the process of estimating the location of an item on a scale where that scale may be basedon classical true score theory or latent trait theory.Item Difficulty: Observed statistic (or estimated parameter) for an item that is based on the proportion of studentsresponding correctly to that item. While it is true that more complex items usually have higher difficulty, itemdifficulty and complexity are not the same. (See also: Complexity.)Item Generation Model: For ELA-Literacy, a model to develop operational items (sometimes referred to as a taskmodel by those publishing research on Evidence Centered Design). An item generation model allows testdevelopers to generate an operational item that elicits targeted evidence aligned to one or more standards. Each itemgeneration model has fixed features—the structural elements of the model that are common to all operational itemsdeveloped using this model. Each item generation model can also have variable features—those elements that canvary to create different/unique items. For the End-of-Year Assessment, item generation models may not necessarilycombine in ways that fulfill the requirements of a specified task generation model. Instead, an item generationmodel may generate an item that “stands alone” eliciting evidence aligned to one or more standards without logicallycohering to a collection of items. For the Mid-Year Assessment (MYA) and Performance-Based Assessment (PBA)components of the PARCC English Language Arts/Literacy summative assessment, all items will be developed aspart of a task. In other words, the item generation models used on the MYA and PBA must combine in ways thatfulfill the requirements of a specified task generation model.Item Fragment: A part of an item maintained as a separate resource and typically shared across multiple items. ForPARCC items, an item fragment may not contain any interactions.Item-Specific Widget Item: The item-specific widget item …Key-Based Scoring: Key-based scoring refers to the use of an answer key to assign ratings or correct/incorrectscores to students’ answers on true/false and multiple-choice response formats. (See also: Hand Scoring, Rule-Based Scoring.)Keyword Emphasis: The alternative content presentation that is to be rendered when keyWordEmphasis is enabled.Emphasis is often represented as bold, italic, or bold/italic, though other forms would be permissible. (From [APIPTerms 1.0].)Keyword Translation: An examinee for whom the default language used to represent item content is different thanthe examinee’s native language may require specific key words to be translated to another language. When keywordtranslation is activated, the test delivery system should allow an examinee to access a key word translation ondemandat any time while the item is displayed. (From [APIP Terms 1.0].)Label: A label is a symbol that can potentially be used as a name. As an identifier, labels are typically strings.(From [PILIN].)224 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossaryLine Graph Item: The line graph (LG) item …Link: A hypermedia feature that allows the student to access a definition, audio pronunciation, graphicrepresentation, etc. Such links are embedded in text and signal a way for students to get more information about aterm or concept.Major Content: This term is specific to Mathematics content. The major content in a grade/course is determined bythat grade level’s Major Clusters as identified in the PARCC Model Content Frameworks for Mathematics [PARCCMath Frameworks] (with designations for high school courses to come in the final Frameworks). Note that tasks onPARCC assessments providing evidence for Sub Claim A about Major Content will sometimes require the student toapply knowledge, skills, and understandings from across several Major Clusters.Manifest: This is the XML structure describing assessment content contained within the file imsmanifest.xml thatmust be included within a content package. (From [APIP Terms 1.0].)Manifest Metadata: This is the metadata that is defined at the top level of the manifest. IEEE LOM [LOM, LOMCorrigendum] is used as the required format and manifest metadata is required in an APIP Content Package. Thismetadata is used to describe the APIP Content Package as a whole and not just the manifest within the package.(From [APIP Terms 1.0].)Master Claim: The master claim is about the overall performance goal for PARCC assessments—students mustdemonstrate that they are college- and career-ready by the end of high school, or on track for college and careerreadiness at other grades. The extent to which a master claim is true is indicated by scale scores. (See also: SubClaim.)Match Interaction: Structured content (text, graphics and media elements) that presents the student with two sets ofchoices and allows them to create associates between pairs of choices in the two sets, but not between pairs ofchoices in the same set.Media Interaction: Structured content (text, graphics and media elements) that includes time-based media. Theinteraction includes media controls that limit and report how many times the student interacts with the media.Metadata: Often referenced as “data about data”, metadata are pieces of descriptive information associated with adocument, file, dataset, data profile, or multimedia object that are used to catalog a range of properties about the file,and therefore as means of encoding the object to enhance technical functions such as interoperable data exchange,data storage and retrieval, web search, and many other related programs and applications. Complex sets of metadataelements may be organized into formalized and standardized schemas to meet the needs of particular industries orapplications.Multiple Choice Technology-Enhanced Item: The multiple choice technology-enhanced (MCTE) item …Multiple Select Item: The multiple select (MS) item …Name: A name is the association of a label with a context that differentiates labels used for distinct purposes.(From [PILIN].)Number Line Item: The number line (NL) item …Open Standards: Standardized data formats and data transport protocols that are available for broad public andcommercial use as a means to promote interoperability. Standards considered open may be administered by thestandards owners or governing bodies with varying degrees of openness in their approaches to permissions andlicensing, but open standards are generally royalty-free and frequently have a user community-driven model of longtermstandards management. In contrast, proprietary (closed) standards are generally only available for reuse undercontractual cost-based licensing and are controlled exclusively by the standard owner.V 0.65: Public Draft 20130912 225

GlossaryPARCC Item Development Technical GuideOrder Interaction: Structured content (text, graphics and media elements) that includes an initially ordered set ofchoices. The student reorders the choices.Organization: This is a structure within a content package that is used to describe the logical structure of thecontents within a content package. Organizations are not permitted in an APIP Content Package. (From [APIPTerms 1.0].)PARCC APIP Profile: The PARCC-Specific profile of the RTTA APIP Profile incorporating the PARCC-specificmodifications to APIP that both extend and constrain the RTTA APIP Profile to incorporate PARCC-specificrequirements and features.Performance-Based Task: For ELA-Literacy, an operational task generated from a task generation model whichprovides students with an authentic or realistic scenario. In performance-based tasks, evidences are observable instudents’ work products.Performance Level Descriptors (PLDs): There are two types of PLDs: general and specific. The general PLDsconvey policy goals. For example, the policy board setting the standards might require that one of the performancelevels indicate readiness for the next grade level. These policy level PLDs are usually not grade level or subjectspecific. On the other hand, specific PLDs indicate the minimum knowledge or skills required at each performancelevel for the given grade and subject. This second type of PLDs indicates “how well” students are expected toperform on the content standards and “how good is good enough” to be judged as having achieved specificperformance standards. Draft PLDs (sometimes called target PLDs) are useful early in the assessment designprocess to inform the range of task complexity required at each grade level to ensure reliable measurement across allperformance categories. In an evidence-centered design approach to assessment development, task models aredirectly informed by draft PLDs.Personal Needs and Preferences (PNP): A standard that provides the detailed student needs and preferences forspecific assessments. These needs and preferences might include magnification, contrast, foreground/backgroundcolor, audio text, Braille, etc. [AfA PNP 2.0].Polygon Graph Item: The polygon graph (PG) item …Position Object Interaction: A graphic interaction with an associated image where the student is to position animage on top of the base image.Practice-Forward Tasks: This term is specific to Mathematics content. A practice-forward task is intentionallydesigned or intentionally selected to elicit one or more particular practices in connection to specified content. Eachtargeted practice or its absence is observable in the student‘s response, whether directly through observing studentwork or indirectly through an incorrect answer to a problem in which the practice will have made a correct answermuch more likely. Thus, a requirement of practice-forward tasks is that it be unlikely or impossible to earn fullcredit on the task without engaging in the practice. General examples of practice-forward tasks might include: Tasks that require execution of the modeling cycle in high school (MP.4; see pp. 72,73 [CCSSM])Tasks that require the student to justify or prove a statement, or critique such reasoning (MP.3)Tasks that reward seeing structure in an algebraic expression and using the structure to rewrite it for apurpose (MP.7).Practice-Integrated Content Standard: A content standard or part thereof in which one or more practices is explicit.Examples: practice standard MP.3 is explicit in content standards 3.NF.3b and in part of 4.NF.2; practice standardMP.4 is explicit in part of content standard F-BF.2.Practice-Related Content Standard: A content standard or part thereof in which one or more practices is implicit.Examples: practice standards MP.1, MP.2, MP.7, and MP.8 are implicit in content standard 4.NBT.5 (see PARCCModel Content Framework for Mathematics, p. 21[PARCC Math Frameworks]).226 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossaryPreference: A feature that can be changed by the user but is thought to be irrelevant to performance (e.g., choice ofwriting with a pen with blue ink or a pen with black ink on the quality of a written essay). Examples of a preferencecould include allowing the user to: enlarge the font size, alter the line spacing, alter the leading (space between lines)and margins, change the font color, or alter the background color. Often it is useful to have students interact withthe system to select preferences before a timed task begins. Preferences may be linked with the learner profile andstored for use across subtests or sessions.Presentation Editor Item: The presentation editor item …Profiling: This is the process by which one or more specifications are tailored and combined to meet theinteroperability requirements of a specific market sector or user community. (From [APIP Terms 1.0].)Progression-Sensitive Task: This term is specific to Mathematics content. A task intentionally designed orintentionally selected to be informative about students’ location along a specified content progression in theCommon Core State Standards. Progression-sensitive tasks trace coherent progressions in the standards and canplay an important role in the assessment design. Example: Write 1/2 + 1/3 + 1/4 as a fraction. This computation islikely beyond the reach of a typical student who meets the grade 4 standards, yet likely within the reach of a typicalstudent who meets the grade 5 standards. A similar example that requires more strategy and persistence will be:Write 3/4 – 1/10 + 1/8 as a fraction.Prose Constructed Response (PCR): This term is relevant only for ELA-Literacy assessment components. Thisterm refers to a specific item model where students are required to produce written prose in response to a prompt.Prose constructed-response items always measure the writing claim (Writing and Language Standards).Question and Test Interoperability (QTI): Defines a standard format for the representation of assessment contentand results, supporting the exchange of this material between authoring and delivery systems, repositories and otherlearning management systems. It allows assessment materials to be authored and delivered on multiple systemsinterchangeably. It is designed to facilitate interoperability between systems. [QTI]QTI Assessment Item: This is the representation of an item using QTI. Each assessmentItem is contained in its ownXML instance file. An APIP Item is a type of QTI assessmentItem, i.e., a profiled version. (From [APIP Terms1.0].)QTI Assessment Test: This is the representation of a Test using QTI. Each assessmentTest is contained in its ownXML instance file. The associated assessmentItems are contained in their own XML instance files. (From [APIPTerms 1.0].)QTI Metadata: This is the metadata for QTI assessmentItems as defined within the IMS QTI v2.1 specification [QTIInfo 2.1]. Within APIP this metadata is contained with the IEEE LOM for the metadata [LOM, LOM Corrigendum]of a resource in the manifest of the APIP Content Package. (From [APIP Terms 1.0].)Readiness Tool: Online dynamic and interactive technology readiness tool to support technology transitions andimplementation that is jointly being developed for the Smarter Balanced Assessment Consortium (SBAC) andPARCC [PARCC Readiness].Related Element Information: This is the collection of the accessibility information that is used for the variousalternative renderings of the QTI content. For APIPv1.0 this includes the forms of spoken, brailleText, tactileFile,signFile, keywordTranslation, revealAlternativeRepresentation, guidance and keyWordEmphasis. (From [APIPTerms 1.0].)Rendering Engine: A rendering engine is a software component designed to display QTI-compliant items. (Seealso: Test Client.) (From [PCI].)Reporting Categories: Reporting Categories correspond to the master and major claims about student performancesthat are supported by sufficient evidence to yield scale scores. (See also: Supporting Reporting Categories, MasterClaims.)V 0.65: Public Draft 20130912 227

GlossaryPARCC Item Development Technical GuideResource: A resource is a structure in a content package that is used to identify the physical resources that are used.In APIP the resource types are the original root QTI XML instance, the set of alternative QTI XML instancesreflecting the accessibility capabilities, the set of related asset files (such as images, audio files, etc.) and the set ofcontrol files (such as XSDs) contained within the content package. Every physical file contained within the contentpackage must be identified in a resource. (From [APIP Terms 1.0].)Resource Metadata: This is the metadata defined for a resource within the manifest of a content package. Eachresource is expected to have its own metadata description. The metadata for a resource is based upon a profile ofthe IEEE LOM metadata [LOM, LOM Corrigendum] that also includes an extension to support the QTI Metadata.(From [APIP Terms 1.0].)Reveal Alternative Representation: This is the information that defines the preferences for the manner in which thealternative representation should be revealed. In APIPv1.0 only textString is supported, i.e., rendered using someform of text-based presentation. (From [APIP Terms 1.0].)RTTA APIP Profile: The RTTA-Specific profile of the APIP profile incorporating common RTTA-specificmodifications to APIP that both extend and constrain the APIP model to incorporate RTTA-specific requirementsand features.Rubric Block: A part of an item that it typically used to present instructions to different users, e.g., student or scorer.A rubric block may not contain any interaction elements.Rule-based Scoring: Rule-based scoring refers to using sets of decision rules to assign ratings or correct/incorrectscores to students’ answers on gridded-response, short constructed response and other constrained constructedresponse formats. (See also: Hand Scoring, Key-Based Scoring.)Scaffold: A support that is provided initially but subsequently faded and withdrawn. Training wheels are oftenconsidered a scaffold as they help a beginning/novice bike rider but subsequently become unnecessary. Scaffoldsand supports are identical with the exception of the expectation for how long it will be used (temporarily versusalways).Scale Interaction: The scale interaction …Scale Item: The scale item …Scenario: A problem/ issue/ question that establishes the context for a task.Schools Interoperability Framework (SIF): A technical blueprint for enabling diverse applications to interact andshare data related to entities in the preK–12 instructional and administrative environment. The SIF ImplementationSpecification [SIF] defines architecture requirements and communication protocols for software components and theinterfaces between them that enable diverse applications to interact and share data efficiently, reliably, and securely,regardless of the platform hosting those applications.Selected Response Item: The selected response (MC) item …Short Text: This term is relevant only for ELA-Literacy assessment components. A text that is designated as a shorttext is one that is close in length to the minimum length listed for a given grade-level.Simulation Item: The simulation item …Select Point Interaction: A graphic interaction with an associated image where the student is to select one or morepoints.Sign File: This is a file that contains a visual (video) rendering of the signing that is used to accompany somewritten text. (From [APIP Terms 1.0].)228 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossarySimple Item: An item that contain only one point of interaction. (See also: Composite Item.)Slider Interaction: Structured content (text, graphics and media elements) that presents the student with a controlfor selecting a numerical value between a lower and upper bound.Solution Set Graphing Item: The solution set graphing item …Source Media: Original media assets that are the source for assets rendered in a test, e.g., an original uncroppedphotograph, a source drawing for a JPEG image, the unedited/raw video, the uncompressed audio file.Spoken: This is the content that is to be presented in a spoken form, e.g., read aloud using a speech synthesizer (liveor pre-recorded) or pre-recorded human sound file. The actual form in which the spoken rendering is realized isdependent upon the content presented as the alternative forms. (From [APIP Terms 1.0].)Structured Mask: For students who require assistance maintaining focus, masking may be used to display smallerblocks of information. Structured masking is used to assist the student in developing an understanding of an item bymasking specific elements of the item and revealing them in a prescribed order. A separate structured mask tag isapplied to each item content element and the order in which the content is intended to be revealed is specified foreach mask. When a student access profile specifies structured masking, the test delivery system will initially presentthis item with the introductory text and item prompt revealed. At the student’s demand, the graphic element will berevealed. At the student’s demand, each answer option will be revealed. Answer options are included in structuredmask by default, and should be ordered last. Structured Mask is reserved for future uses in APIP. It is not usedwithin the APIP v1 profile. (From [APIP Terms 1.0].)Student Toolbox: The collection of supports available individually on-screen, stored in a tool palette, or accessiblethrough a menu or control panel as needed. (See also: Embedded Support.)Sub Claim/Supporting Claim: A claim that supports another higher-level claim. Each sub claim is related tostudents’ mastery of particular knowledge and skills based on the evidence outlined in evidence statements. Notethat a sub claim can be under another sub claim. (See also: Master Claim.)Summative Assessment: The purpose of summative assessments is to measure the level of competency of a studentagainst all of the knowledge and skills within the domain of interest at the end of an instructional phase such as anentire school year. In the case of PARCC, summative assessments will measure the full range of the Common CoreState Standards and will be designed to report the extent to which students are “on track” or “ready” for college andcareers. In the PARCC assessment system, the summative assessment includes the combination of the Performance-Based Assessment and the End-of-Year Assessment, and may include the Mid-Year Assessment after further study.Support: A context-specific performance aid. Some directions may need to be provided concerning how this typeof aid can be used. Spell checking may be a tool that is provided in workspaces that involve writing but disabled incontexts that involve mathematical problem solving. (See also: Embedded Support.)Supporting Reporting Categories: …Tag: In order to gather data from an assessment, pieces of data must have specific computer coding associated withthe data. The computer is then able to “gather” all pieces of data with the same code together. To tag a piece ofdata (e.g., an item, a graphic, a passage) is to associate that piece of data with a specified code. The act ofassociating the code with a piece of data is called tagging. Data that has been coded is said to be tagged. (See also:Metadata.)Task: This term has content-specific meanings. In ELA-Literacy a task is an operational, coherent collection of items. Some collections of items (tasks) arecohesive only insofar as they are linked to a shared stimulus (e.g., a collection of items that are connectedto a specific reading passage). Some tasks have more extensive cohesive qualities. For the purposes of thePARCC ELA-Literacy assessments, all tasks must clearly reflect a specified task generation model.Operational tasks must be equipped with teacher directions, student directions, scoring tools, and all otherV 0.65: Public Draft 20130912 229

GlossaryPARCC Item Development Technical Guideancillary materials needed for administration of the collection of items. The number of tasks on anyoperational form may be defined by the operational blueprint used to develop the test form. The Mid-Yearand Performance-Based Assessments are comprised of two large tasks, one focused on research and onefocused on reading literature.In Mathematics, a task is an operational item that may either have a single prompt or be multi-prompt innature. There are three types of tasks for mathematics, as described below: Type I tasks are tasks assessing concepts, skills and procedureso Balance of conceptual understanding, fluency, and applicationo Can involve any or all mathematical practice standardso Machine scorable including innovative, computer-based formatso Will appear on the End-of-Year and Performance-Based Assessment components Type II tasks are tasks assessing expressing mathematical reasoningo Each task calls for written arguments / justifications, critique of reasoning, or precision inmathematical statements (MP.3, MP.6)o Can involve other mathematical practice standardso May include a mix of machine-scored and hand-scored responseso Included on the Performance-Based-Assessment component Type III tasks are tasks assessing modeling/applicationso Each task calls for modeling/application in a real-world context or scenario (MP.4)o Can involve other mathematical practice standardso May include a mix of machine-scored and hand-scored responseso Included on the Performance Based Assessment componentTask Generation Model: This term has content-specific meanings.In ELA-Literacy, a task generation model allows test developers to generate many different tasks that areroughly equivalent for multiple operational assessments. Each task generation model has fixed features—the structural elements of the model that are common to all operational tasks developed using this model.Each task generation model can also have variable features—those elements that can vary to createdifferent/unique performance-based tasks.In Mathematics, a task generation model also allows test developers to generate multiple, roughlyequivalent tasks. A model indicates the following with necessary metadata:a. Claim(s) for which evidence is being providedb. Particular standard(s) being assessedc. Important features of the task (practice-forward, integrative, etc.)d. Markup of the task showing any parameters that can change from instance to instance of the taske. Limits on parameters and additional guidance for task developersf. If appropriate, annotations of the rubric that elucidate the evidence generated by the taskg. If appropriate, notes on technologically enhanced features of the taskTask Models: In Evidence Centered Design, task models describe how to structure the kinds of situations in anassessment to obtain the evidence needed to support claims about students’ knowledge and skills. Task modelsidentify variables that describe features of tasks to be presented to the student in light of the type of evidence that thetasks will yield. They describe how the assessment materials must be presented to the students and expected studentwork products in response to the assessment materials for the purposes of the PARCC assessments, given thedifferences in the assessment design for ELA-Literacy and Mathematics, the role of task models is somewhatdifferent.Technology-Enhanced Items: These are items that utilize technology in presenting assessment materials to studentsand capturing student responses in a way that cannot be accomplished without the use of such technology. Suchitems might include simulation, interactivity, and often allow for various types of constructed response.Technology-enhanced items may be designed to target content standards that in the past have been difficult to230 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideGlossarymeasure or may be designed to allow for efficiencies in test administration (e.g., to more efficiently capture datathan traditional short answer items, thereby reducing student testing time or the amount of hand-scoring required).Test Client: An application running on a computer device that presents and manages the test for the student and testadministrator. (See also: Device.)Test Delivery: A component of the PARCC assessment system that manages the secure delivery of the test anditems to the student, captures student responses and metrics, and orchestrates the scoring of the test.Test Specification: A test design indicating various characteristics of a test, including the grade level, the number oftest questions, or the number of points related to each content area and standard on the test and the relative emphasisplaced on each competency. (See also: Blueprint.)Text Annotation Item: The text annotation item …Text Entry Interaction: A span of text that provides the student with a mechanism to enter a simple piece of text.Text Extraction Item: The text extraction (EXT) item …Text Flagging Item: The text flagging item …Tool: See Companion Material.Universal Design for Assessment: Principles that support a flexible design approach for test items such that allparticipating students are able to demonstrate what they know and can do regardless of physical, sensory,behavioral, or cognitive impairment, and recognizing that no single model will meet all students’ needs [UniversalDesign].Universal Design Principles: Principles guiding the designing environments, products, and communications in away that is inherently accessible to all intended users.Upload Interaction: Structured content (text, graphics and media elements) that provides the student with amechanism to upload a file.Variant: This is a feature in the Content Packaging [CP Info 1.2] that is used to contain alternative resourceinformation. A resource can have many variants (for example, an English variant, a Spanish variant, and aSimplified English Variant). In APIP the variant structure is used to contain the metadata that describes theconditions under which the alternative forms of an item are available to be used. Variants for an item are packagedtogether in a single item content package. (From [APIP Terms 1.0].)Web Search Item: The web search item …Zoom Number Line Item: The zoom number line item …Note: Words in italics in a gloss are defined elsewhere in the glossary.V 0.65: Public Draft 20130912 231

AcronymsPARCC Item Development Technical GuideAcronymsAACCLIPAfA DRDAfA PNPAFAIFAPIPATBLTICCCCSSCEDSCIPACOPPACPCSMCSSDRDEBSRECDELELA-LESESEAFERPAGUIDAccommodationsAccess for All Learner Information PackageAccess for All Digital Resource DescriptionAccess for All Personal Needs & PreferencesAccessibility FeaturesAssessment Interoperability FrameworkAccessible Portable Item ProtocolAssistive TechnologyBasic Learning Tools InteroperabilityCommon CartridgeCommon Core State StandardsCommon Education Data StandardsChildren’s Internet Protection ActChildren’s Online Privacy Protection ActContent PackagingCurriculum Standards MetadataCascading Style SheetDigital Resource DescriptionEvidence-Based Selected ResponseEvidence-Centered DesignEnglish LearnerEnglish Language Arts-LiteracyEmbedded SupportsElementary and Secondary Education ActFamily Education Rights and Privacy ActGlobally Unique Identifier232 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideAcronymsHTMLIANAIDEAIEPJSONLOMLTIMathMLPARCCPCIPCRPLDPNPQTIRPTRTTASBACSIFTECRTEIURIWCAGXHTMLXMLXSDHyperText Markup LanguageInternet Corporation for Assigned Names and NumbersIndividuals with Disabilities Education ActIndividualized Education ProgramJavaScript Object NotationLearning Object MetadataLearning Tools InteroperabilityMathematical Markup LanguagePartnership for Assessment of Readiness for College and CareersPortable Custom InteractionProse Constructed ResponsePerformance Level DescriptorsPersonal Needs & PreferencesQuestion & Test InteroperabilityResponse Processing TemplateRace to the Top AssessmentSmarter Balanced Assessment ConsortiumSchools Interoperability FrameworkTechnology-Enhanced Constructed ResponseTechnology-Enhanced ItemUniversal Resource IdentifierWeb Content Accessibility GuidelineseXtensible HyperText Markup LanguageeXtensible Markup LanguageXML Schema DefinitionV 0.65: Public Draft 20130912 233

ReferencesPARCC Item Development Technical GuideReferences[Accessibility Metadata] Accessibility Metadata Model[AfA] Access for All, IMS Global Learning Consortium Inc.[http://www.imsglobal.org/accessibility/index.html][AfA DRD 2.0] Access For All Digital Resource Description Information Model, Final Release, Version 2.0,R. Schwerdtfeger, M. Rothberg and C. Smythe, IMS Global Learning Consortium Inc., October 2009[http://www.imsglobal.org/accessibility/accdrdv2p0/html/ISO_ACCDRDv2p0_InfoModelv1.html][AfA PNP 2.0] Access For All Personal Needs & Preferences Digital Resource Description for Digital DeliveryInformation Model, Final Release, Version 2.0, R. Schwerdtfeger, M. Rothberg and C. Smythe, IMS GlobalLearning Consortium Inc., April 2010[http://www.imsglobal.org/accessibility/accpnpv2p0/spec/ISO_ACCPNPinfoModelv2p0.html][AIF] Assessment Interoperability Framework, CEDS/NCES[https://ceds.ed.gov/aif.aspx][APIP] The Accessible Portable Item Protocol (APIP), IMS Global Learning Consortium Inc.[http://www.imsglobal.org/apip/][APIP BP 1.0] Accessible Portable Item Protocol (APIP): Best Practices and Implementation Guide, CandidateFinal Release, Version 1.0, G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_Best_v1p0cf.html][APIP Conformance 1.0] Accessible Portable Item Protocol (APIP) Conformance and Certification, Candidate FinalRelease, Version 1.0, G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_Conf_v1p0cf.html][APIP Overview 1.0] Accessible Portable Item Protocol (APIP) Overview, Candidate Final Release, Version 1.0,G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_Oview_v1p0cf.html][APIP PNP 1.0] Accessible Portable Item Protocol (APIP): Technical Specification for AfA PNPv2.0 Features,Candidate Final Release, Version 1.0, G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_PNP_v1p0cf.html][APIP QTI 1.0] Accessible Portable Item Protocol (APIP): Technical Specification for QTIv2.1 Features, CandidateFinal Release, Version 1.0, G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_QTI_v1p0cf.html][APIP Tech 1.0] Accessible Portable Item Protocol (APIP): Technical Specification, Candidate Final Release,Version 1.0, G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_Profile_v1p0cf.html][APIP Terms 1.0] Accessible Portable Item Protocol (APIP) Terms and Definitions, Candidate Final Release,Version 1.0, G. Driscoll, et al., IMS Global Learning Consortium Inc., March 2012[http://www.imsglobal.org/apip/apipv1p0cf/APIPv1p0_Terms_v1p0cf.html][APIP Validator] IMS Assessment Conformance and Certification Validator, IMS Global Learning Consortium Inc.[http://validator.imsglobal.org/assessment/]234 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideReferences[AVI] AVI File Format, Microsoft Developer Network, Microsoft[http://msdn.microsoft.com/en-us/library/ms779631.aspx][CC] Common Cartridge, IMS Global Learning Consortium Inc.[http://www.imsglobal.org/cc/][CC Implementation 1.2] Common Cartridge Profile: Implementation, Version 1.2, J. Kahn (Ed.), Final Release,IMS Global Learning Consortium Inc., October 2011[http://www.imsglobal.org/cc/ccv1p2/imscc_profilev1p2-Implementation.html][CC XSD 1.2] Common Cartridge Profile: Appendices, Version 1.2, J. Kahn (Ed.), Final Release, IMS GlobalLearning Consortium Inc., October 2011[http://www.imsglobal.org/cc/ccv1p2/imscc_profilev1p2-Appendices.html][CCSS] Common Core State Standards[http://www.corestandards.org/][CCSSE] Common Core State Standards for English Language Arts & Literacy in History/Social Studies, Science,& Technical Subjects[http://www.corestandards.org/ELA-Literacy][http://www.corestandards.org/assets/CCSSI_ELA%20Standards.pdf][CCSSM] Common Core State Standards for Mathematics[http://www.corestandards.org/Math][http://www.corestandards.org/assets/CCSSI_Math%20Standards.pdf][CEDS] Common Education Data Standards, CEDS/NCES[https://ceds.ed.gov/][CEDS 3.0] Domain Entity Schema, Version 3.0, Common Education Data Standards, CEDS/NCES, January 2013[https://ceds.ed.gov/domainEntitySchema.aspx][Chicago] The Chicago Manual of Style, 16 th Edition, University of Chicago Press Staff (Eds.), August 2010[CIPA] Children's Internet Protection Act[http://www.fcc.gov/guides/childrens-internet-protection-act][COPPA] Children’s Online Privacy Protection Act[http://www.coppa.org/][CP] Content Packaging, IMS Global Learning Consortium Inc.[http://www.imsglobal.org/content/packaging/index.html][CP BP 1.2] Content Packaging Best Practice and Implementation Guide, Version 1.2, W. Kraan, et al., Public DraftV 2.0, IMS Global Learning Consortium Inc., March 2007[http://www.imsglobal.org/content/packaging/cpv1p2pd2/imscp_bestv1p2pd2.html][CP Info 1.2] Content Packaging Information Model, Version1.2, W. Kraan, et al., Public Draft V 2.0, IMS GlobalLearning Consortium Inc., March 2007[http://www.imsglobal.org/content/packaging/cpv1p2pd2/imscp_infov1p2pd2.html][CP XML 1.2] Content Packaging XML Binding, Version1.2, W. Kraan, et al., Public Draft V 2.0, IMS GlobalLearning Consortium Inc., March 2007[http://www.imsglobal.org/content/packaging/cpv1p2pd2/imscp_bindv1p2pd2.html]V 0.65: Public Draft 20130912 235

ReferencesPARCC Item Development Technical Guide[CSS] CSS Specifications, World Wide Web Consortium (W3C)[http://www.w3.org/Style/CSS/current-work][ECMAScript] ECMAScript Language Specification, Edition 5.1, ECMA-262, ECMA International, June 2011[http://www.ecma-international.org/publications/standards/Ecma-262.htm][ESEA] Elementary and Secondary Education Act[http://www.ed.gov/esea/][FERPA] Family Educational Rights and Privacy Act[http://www.ed.gov/policy/gen/guid/fpco/ferpa/index.html][GIF89] Graphics Exchange Format, Version 89a, CompuServe Incorporated, July 1990[http://www.w3.org/Graphics/GIF/spec-gif89a.txt][HTML5] HTML 5.1, R. Berjon et al. (Eds.), W3C Draft, World Wide Web Consortium (W3C)[http://www.w3.org/html/wg/drafts/html/master/][IANA MIME] MIME Media Types, The Internet Corporation for Assigned Names and Numbers (IANA)[http://www.iana.org/assignments/media-types][IDEA] Individuals with Disabilities Educational Act[http://idea.ed.gov/][JPEG] Digital Compression and Coding of Continuous-tone Still Images: Requirements and Guidelines, ISO/IEC10918-1:1994[http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=18902][JSON] The application/json Media Type for JavaScript Object Notation (JSON), RFC 4627, D. Crockford, InternetEngineering Task Force (IETF), July 2006[http://tools.ietf.org/html/rfc4627][Lang Tag] Tags for Identifying Languages, RFC 5646, A. Phillips and M. Davis (Eds.), Internet Engineering TaskForce (IETF), September 2009[http://tools.ietf.org/html/rfc5646][LOM] IEEE 1484.12.1-2002: IEEE Standard for Learning Object Metadata, The Institute of Electrical andElectronics Engineers Inc., 2002[http://standards.ieee.org/findstds/standard/1484.12.1-2002.html][LOM Corrigendum] IEEE 1484.12.1-2002/Cor 1-2011 - IEEE Standard for Learning Object Metadata -Corrigendum 1: Corrigenda for 1484.12.1 LOM (Learning Object Metadata), The Institute of Electrical andElectronics Engineers Inc., 2011[http://standards.ieee.org/findstds/standard/1484.12.1-2002-Cor_1-2011.html][LOM XML] IEEE 1484.12.3-2005: IEEE Standard for Learning Technology—Extensible Markup Language(XML) Schema Definition Language Binding for Learning Object Metadata, The Institute of Electrical andElectronics Engineers Inc., 2005[http://standards.ieee.org/findstds/standard/1484.12.3-2005.html][LOM XML Corrigendum] IEEE P1484.12.3-1 2005/Cor 1/D1: Draft Standard for Learning Technology—Extensible Markup Language (XML) Schema Definition Language Binding for Learning Object Metadata —Corrigendum 1: Corrigendum to reflect the Learning Object Metadata corrigendum, The Institute of Electrical andElectronics Engineers Inc., 2009236 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideReferences[LTI Implementation 1.1] Learning Tools Interoperability Implementation Guide, Version 1.1.1, G. McFall, et al.(Eds.), Final Specification, IMS Global Learning Consortium Inc., September 2012[http://www.imsglobal.org/LTI/v1p1/ltiIMGv1p1.html][MathML] Mathematical Markup Language (MathML), Version 3.0, D. Carlisle, P. Ion and R. Miner (Eds.),W3C Recommendation, World Wide Web Consortium (W3C), October 2010[http://www.w3.org/TR/MathML3/][MP4] Coding of Audio-Visual Objects – Part 14: MP4 File Format, ISO/IEC 14496-14:2003[http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38538][MPEG] Coding of Moving Pictures and Associated Audio for Digital Storage Media at up to About 1,5 Mbit/s –Part 2: Video, ISO/IEC 11172-2:1993[http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=22411][PARCC Accessibility Guide] PARCC Accessibility Guidelines, PARCC[PARCC Accommodations Manual] PARCC Accommodations Manual for Students with Disabilities and EnglishLearners, First Edition, PARCC, April 2013[http://www.parcconline.org/sites/parcc/files/PARCCDraftAccommodationsManualforSWDEL.pdf]PARCC ELA Audio] PARCC ELA Audio Guidelines, V1.0, PARCC, April 2012[PARCC ELA Frameworks] PARCC Model Content Frameworks for ELA/Literacy, V2.0, PARCC, August 2012[http://www.parcconline.org/sites/parcc/files/PARCCMCFELALiteracyAugust2012_FINAL.pdf][PARCC Evidence] PARCC Evidence Statements, PARCC[http://www.parcconline.org/assessment-blueprints-test-specs][PARCC Math Frameworks] PARCC Model Content Frameworks for Mathematics, V3.0, PARCC, November 2012[http://www.parcconline.org/sites/parcc/files/PARCCMCFMathematicsNovember2012V3_FINAL.pdf][PARCC Readiness] PARCC Assessment Capacity Planning Tool, PARCC, April 2013[http://www.parcconline.org/sites/parcc/files/PARCCCapacityPlanningTool_3-5-13FINAL4-12-13.xlsx][PARCC Style Guide] PARCC Style Guide, Version 1.1, PARCC, April 2013[PARCC Tech Guide] Technology Guidelines for PARCC Assessments, V2.1, PARCC, February 2013[http://www.parcconline.org/sites/parcc/files/PARCCTechnologyGuidelines2dot1_Feb2013Update.pdf][PARCC TEI] PARCC Technology-Enhanced Item Definitions, PARC[PCI] Portable Custom Interactions, Version 1.0, Final Release, M. Aumock, M. McKell, P. Spruiell (Eds.), IMSGlobal Learning Consortium Inc., February 2013[http://www.imsglobal.org/assessment/interactions.html][PILIN] PILIN Glossary[http://resolver.net.au/hdl/102.100.272/HHYMV8JQH][PNG] Portable Network Graphics (PNG) Specification, Second Edition, D. Duce (Ed.), W3C Recommendation,World Wide Web Consortium (W3C), November 2003[http://www.w3.org/TR/PNG/][QTI] Question & Test Interoperability Specification, IMS Global Learning Consortium Inc.[http://www.imsglobal.org/question/index.html]V 0.65: Public Draft 20130912 237

ReferencesPARCC Item Development Technical Guide[QTI Implementation 2.1] Question & Test Interoperability Implementation Guide, Version 2.1, S. Lay, P. Gorissenand W. Kraan, Final Release, IMS Global Learning Consortium Inc., August 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_implv2p1.html][QTI Info 2.1] Question & Test Interoperability Assessment Test, Section and Item Information Model, Version 2.1,S. Lay, P. Gorissen and W. Kraan, Final Release, IMS Global Learning Consortium Inc., August 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_infov2p1.html][QTI Integration 2.1] Question & Test Interoperability Integration Guide, Version 2.1, S. Lay, P. Gorissen andW. Kraan, Final Release, IMS Global Learning Consortium Inc., November 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_intgv2p1.html][QTI Metadata 2.1] Question & Test Interoperability Metadata and Usage Data, Version 2.1, S. Lay, P. Gorissenand W. Kraan, Final Release, IMS Global Learning Consortium Inc., November 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_mdudv2p1.html][QTI Migration 2.1] Question & Test Interoperability Migration Guide, Version 2.1, S. Lay, P. Gorissen andW. Kraan, Final Release, IMS Global Learning Consortium Inc., August 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_migrv2p1.html][QTI Overview 2.1] Question & Test Interoperability Overview, Version 2.1, S. Lay, P. Gorissen and W. Kraan,Final Release, IMS Global Learning Consortium Inc., August 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_oviewv2p1.html][QTI Results 2.1] Question & Test Interoperability Results Reporting, Version 2.1, S. Lay, P. Gorissen andW. Kraan, Final Release, IMS Global Learning Consortium Inc., August 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_resultv2p1.html][QTI XML 2.1] Question & Test Interoperability (QTI) XSD Binding, Version 2.1, S. Lay, P. Gorissen andW. Kraan, Final Release, IMS Global Learning Consortium Inc., August 2012[http://www.imsglobal.org/question/qtiv2p1/imsqti_bindv2p1.html][QTIWorks] QTIWorks[https://www2.ph.ed.ac.uk/qtiworks/][SAMI] Synchronized Accessible Media Interchange, Microsoft Developer Network, Microsoft Corporation[http://msdn.microsoft.com/en-us/library/ms971327.aspx][Section 504] Rehabilitation Act of 1973, Section 504[Section 508] Rehabilitation Act of 1973, Section 508[https://www.section508.gov/][SIF] Schools Interoperability Framework Data Model Implementation Specification, Version 2.5, SIF Association,May 2011[http://specification.sifassociation.org/Implementation/US/2.5/html/index.html][SMIL] Synchronized Multimedia Integration Language (SMIL 3.0), Version 3.0, D. Butlerman, et al. (Eds.), W3CRecommendation, World Wide Web Consortium (W3C), December 2008[http://www.w3.org/TR/SMIL3/][SVG] Scalable Vector Graphics (SVG), Version 1.1 (Second Edition), E. Dahlström, et al. (Eds.), W3CRecommendation, World Wide Web Consortium (W3C), August 2011[http://www.w3.org/TR/SVG11/]238 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideReferences[UCS] Universal Coded Character Sets (UCS), ISO/IEC 10640:2012[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=56921][Universal Design] Universal Design Applied to Large Scale Assessments, Synthesis Report 44, S. Thompson,C. Johnstone and M. Thurlow, University of Minnesota, National Center on Educational Outcomes, 2002[http://www.cehd.umn.edu/NCEO/OnlinePubs/Synth44.pdf][URI] Uniform Resource Identifier (URI): Generic Syntax, RFC 3986, T. Berners-Lee, R. Fielding, L. Masinter,Internet Engineering Task Force (IETF), January 2005[http://tools.ietf.org/html/rfc3986][UUID] A Universally Unique IDentifier (UUID) URN Namespace, RFC 4122, P. Leach, M. Mealling, R. Salz,Internet Engineering Task Force (IETF), July 2005[http://www.ietf.org/rfc/rfc4122.txt][VCARD] A MIME Content-Type for Directory Information, RFC 2425, T. Howes, M. Smith and F. Dawson,Internet Engineering Task Force (IETF), September 1998[http://tools.ietf.org/html/rfc2425][VCARD Profile] vCard MIME Directory Profile, RFC 2426, F. Dawson and T. Howes, Internet Engineering TaskForce (IETF), September 1998[hhttp://tools.ietf.org/html/rfc2426][WAVE] Wave File Format[http://web.archive.org/web/20080113195252/http://www.borg.com/~jglatt/tech/wave.htm][WCAG 2.0] Web Content Accessibility Guidelines (WCAG), Version 2.0, B. Caldwell et al. (Eds.), W3CRecommendation, World Wide Web Consortium (W3C), December 2008[http://www.w3.org/TR/WCAG20/][Webster’s Collegiate] Merriam-Webster's Collegiate Dictionary, 11 th Edition, Merriam Webster, April 2008[Webster’s International] Webster's Third New International Dictionary, Merriam Webster, June 2002[XHTML] XHTML 1.0 The Extensible HyperText Markup Language, Second Edition, W3C Recommendation,World Wide Web Consortium (W3C), August 2002[http://www.w3.org/TR/xhtml1/][XInclude] XML Inclusions (XInclude), Version 1.0, Second Edition, J. Marsh, D. Orchard and D. Viellard (Eds.),W3C Recommendation, World Wide Web Consortium (W3C), November 2006[http://www.w3.org/TR/xinclude/][XSD 2] XML Schema Definition Language (XSD) Part 2: Datatypes, Version 1.1, D. Peterson et al. (Eds.),W3C Recommendation, World Wide Web Consortium (W3C), April 2012[http://www.w3.org/TR/xmlschema11-2/][ZIP] .ZIP Application Note, PKWare[http://www.pkware.com/support/zip-app-note]V 0.65: Public Draft 20130912 239

SchemataPARCC Item Development Technical GuideSchemataRTTA APIP Profile SchemataUnless otherwise noted, all XML documents must use the following RTTA APIP Profile XML Schemata. If there isno particular RTTA profile schemata, use the current APIP Profile schemata.Until the RTTA APIP Profile is completed, use the current APIP Profile.Note: PARCC XML documents will not validate against the current APIP Profile.Future Guide Version: Incorporate RTTA APIP Profile Schemata in a subsequent version of this Guide.RTTA APIP AfA DRD V2.0 Profile XSD[/rttav1p0_afadrdv2p0_v1p0.xsd]RTTA APIP Curriculum Standard Profile XSD[/rttav1p0_imscsmdv1p0_v1p0.xsd]RTTA APIP Manifest Metadata (LOM) Profile XSD[/ rttav1p0_lommanifestv1p0_v1p0.xsd]RTTA APIP Resource Metadata (LOM) Profile XSD[/ rttav1p0_lomresourcev1p0_v1p0.xsd]RTTA Accessibility Metadata XSD[/rttav1p0_accessibliltymetadatav1p0_v1p0.xsd]Future Guide Version: Additional Profile Schemata will be defined in subsequent versions of this Guide.APIP Profile SchemataAPIP AfA DRD V2.0 Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_ afadrdv2p0_v1p0.xsd]APIP AfA PNP V2.0 Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_afapnpv2p0_v1p0.xsd]APIP AfA PNP Extensions V2.0 Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_afapnpextv1p0_v1p0.xsd]APIP Content Packaging V1.2 Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_imscpv1p2_v1p0.xsd]APIP Content Packaging Extensions V1.2 Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_cpextv1p2_v1p0.xsd]APIP Curriculum Standard Metadata Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_imscsmdv1p0_v1p0.xsd]240 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideSchemataAPIP Manifest Metadata (LOM) Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_lommanifestv1p0_v1p0.xsd]APIP Resource Metadata (LOM) Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_lomresourcev1p0_v1p0.xsd]APIP QTI V2.1 Extensions Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtiextv2p1_v1p0.xsd]APIP QTI V2.1 Item Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtiitemv2p1_v1p0.xsd]APIP QTI V2.1 Metadata Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtimetadatav2p1_v1p0.xsd]APIP QTI V2.1 Outcomes Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtioutcomesv2p1_v1p0.xsd]APIP QTI V2.1 Results Processing Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtiresprocessingv2p1_v1p0.xsd]APIP QTI V2.1 Section Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtisectionv2p1_v1p0.xsd]APIP QTI V2.1 Test Profile XSD[http://www.imsglobal.org/profile/apip/apipv1p0/apipv1p0_qtitestv2p1_v1p0.xsd]General SchemataAccess For All Digital Resource Description Information Model XSD[http://www.imsglobal.org/xsd/imsaccdrd_v2p0.xsd]Access For All Personal Needs & Preferences Digital Resource Description for Digital Delivery Information ModelXSD[http://www.imsglobal.org/xsd/imsafapnp_v2p0.xsd]Accessible Portable Item Protocol (APIP) XSDs[http://www.imsglobal.org/apip/apipv1p0cf/apipv1p0cf.zip]Common Cartridge Curriculum Standard Metadata XSD[http://www.imsglobal.org/profile/cc/ccv1p2/ccv1p2_imscsmd_v1p0.xsd]Content Packaging XSD[http://www.imsglobal.org/xsd/imscp_v1p2.xsd]Content Packaging Extensions XSD[http://www.imsglobal.org/xsd/imscp_extensionv1p2.xsd]Content Packaging XLink XSD[http://www.imsglobal.org/xsd/ims_xlink.xsd]Learning Object Metadata XSD[http://standards.ieee.org/reading/ieee/downloads/LOM/lomv1.0/]V 0.65: Public Draft 20130912 241

SchemataPARCC Item Development Technical GuideMathML XSD[http://www.w3.org/Math/XMLSchema/mathml3/mathml3.xsd]QTI Assessment, Section and Item XSD[http://www.imsglobal.org/xsd/qti/qtiv2p1/imsqti_v2p1.xsd]QTI Metadata XSD[http://www.imsglobal.org/xsd/qti/qtiv2p1/imsqti_metadata_v2p1.xsd]QTI Result Reporting XSD[http://www.imsglobal.org/xsd/qti/qtiv2p1/imsqti_result_v2p1.xsd]QTI Usage Data XSD[http://www.imsglobal.org/xsd/qti/qtiv2p1/imsqti_usagedata_v2p1.xsd]242 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideRTTA APIP ProfileAnnex: RTTA APIP ProfileThe encoding, exchange and validation guidelines are derived from the current (version 1.0) APIP specification[APIP]. The guidelines herein both extend and constrain the APIP model to incorporate PARCC and RTTA-specificrequirements and features. The RTTA APIP Profile is a profile of APIP incorporating these RTTA-specificmodifications to APIP.The RTTA APIP Profile includes: RTTA APIP Profile Technical Specification, including:o RTTA-specific Access for All Personal Needs & Preference Featureso RTTA-specific QTI Featureso RTTA-specific Metadata Featureso RTTA-specific Accessibility Metadata Featureso RTTA-specific Packaging Featureso RTTA-specific Alignment Features RTTA APIP Profile Conformance Requirements RTTA APIP Profile Schemata XSDsUpon completion of the profile, the validation guidelines and schemata description will be updated to incorporateuse of the RTTA APIP Profile.Profile VersioningThe current version of the PARCC and RTTA profiles is 1.0.Naming conventions follow the IMS naming convention of assigning a major and point version number to an artifactand having a three part profile name, with the parts concatenated with an underscore (_). The three name parts areeach followed by “v”, followed by the major version number, followed by a “p”, followed by the point versionnumber to indicate the version. The three parts are: Profile base name, either rtta or parcc, with concatenated version information, e.g., rttav1p0 Versioned source specification being profiled with concatenated version information, e.g., qtiitemv2p1 XDS version which is just the version informationThus, for example, the XSD for the RTTA profile of the APIP AfA DRD V2.0 Profile XSD would be namedRTTAv1p0_afadrdv2p0_v1p0.xsdFuture Guide Version: Develop RTTA APIP Profile for subsequent version of this Guide.APIP Accessibility ProfilingThe list enumerates the difference between the PARCC accessibility profile elements and the APIP profile (profilevocabularies are listed in the Vocabularies section below): Additional companion materials are supported.Note: The list above is not complete. Individual companion material details are not included.V 0.65: Public Draft 20130912 243

RTTA APIP ProfilePARCC Item Development Technical GuideAPIP QTI ProfilingThe list enumerates the difference between the PARCC QTI profile elements and the APIP profile (profilevocabularies are listed in the Vocabularies section below): The QTI Modal Feedback element is not permitted The QTI Item Template element is not permitted. The QTI Stylesheet element is not permitted. The QTI prompt element is not used.o Enable inside interactions. PARCC-specific interactions are added:o scaleInteraction Specific interaction attributes are constrained or additional attributes are added or modified:o All interaction shuffle attributes are always false.o choiceInteraction maxChoices attribute is optional in APIP QTI schema, required with default 1 inQTI documentation.o hotspotInteraction maxChoices attribute is optional in APIP QTI schema, required with default 1in QTI documentation.o hottextInteraction maxChoices attribute is optional in APIP QTI schema, required with default 1in QTI documentation.o positionObjectInteraction maxChoices attribute is optional in APIP QTI schema, required withdefault 1 in QTI documentation.o selectPointInteraction maxChoices attribute is optional in APIP QTI schema, required with default1 in QTI documentation.o positionObjectInteraction centerPoint attribute is appears as centrePoint in APIP QTI schema(en-US vs. en-UK).o endAttemptInteraction countAttempt attribute is new to APIP QTI schema and not documented.o PARCC-specific interactions have been added.o gapMatch matchGroup attribute is deprecated but remains in APIP QTI schema.o gapImg matchGroup attribute is deprecated but remains in APIP QTI schema.o gapText matchGroup attribute is deprecated but remains in APIP QTI schema.o simpleAssociableChoice matchGroup attribute is deprecated but remains in APIP QTI schema.o simpleAssociableChoice fixed attribute does not have a default value in APIP QTI schema; allother fixed attributes are default false.o sliderInteraction lowerBound, upperBound and step attributes are double in APIP QTI schema,float in QTI documentation.o outcomeDeclaration longInterpretation, normalMaximum and normalMinimum attributes aredouble in APIP QTI schema, float in QTI documentation.o areaMapEntry mappedValue attribute is double in APIP QTI schema, float in QTIdocumentation.o matchTableEntry sourceValue attribute is double in APIP QTI schema, float in QTIdocumentation.o areaMapping lowerBound, upperBound and defaultValue attributes are double in APIP QTIschema, float in QTI documentation.o mapEntry mappedValue attribute is double in APIP QTI schema, float in QTI documentation.o mapping lowerBound, upperBound and defaultValue attributes are double in APIP QTI schema,float in QTI documentation.o areaMapping defaultValue attribute is optional in APIP QTI schema, required in QTIdocumentation.o mapping defaultValue attribute is optional in APIP QTI schema, required in QTI documentation.o interpolationTableEntry targetValue attribute is string in APIP QTI schema, valueType in QTIdocumentation.o matchTableEntry targetValue attribute is string in APIP QTI schema, valueType in QTIdocumentation.244 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideRTTA APIP ProfileNote: The list above is not complete. Individual interaction type attributes are not included, new interaction typesare not included.Metadata ProfilingThe list enumerates the differences between the RTTA metadata profile elements and the APIP profile (profilevocabularies are listed in the Vocabularies section below): The LOM Entity ID element permits multiple values. The LOM Author element is required by APIP but not RTTA. The QTI Composite element is required if the item contains multiple interactions. The QTI Interaction Type element is required. The QTI Interaction Type is inconsistent between the APIP documentation, APIP schema and QTI:o InlineChoiceInteraction and TextEntryInteraction are missing from the documentation.o The binding uses positionObjectInteraction while the documentation uses positionObjectStage.o The binding uses selectionPointInteraction while the documentation uses selectPointInteraction.o The binding omits mediaInteraction.o CEDS uses upper camel case names, APIP uses lower camel case.o sliderInteraction and selectionPointInteraction are missing from the CEDS vocabulary.Note: The list above is not complete. The profile must align with requirements for metadata listed in Table 6.1.Packaging ProfilingThe list enumerates the differences between the RTTA packing profile elements and the APIP profile (profilevocabularies are listed in the Vocabularies section below): Metadata is extended to include LOM, accessibility, QTI and curriculum metadata for manifests andresources. The assessmentSection itemSessionControl element is in the APIP documentation but has been removedfrom the schema. The assessmentSection timeLimits element is in the APIP documentation but has been removed from theschema. The assessmentSection selection element is described in the APIP documentation as being deleted but hasnot been removed from the schema. The assessmentSection ordering element is described in the APIP documentation as being deleted but hasnot been removed from the schema. The assessmentTest testFeedback element is described in the APIP documentation as being deleted buthas not been removed from the schema. The assessmentTest testPart element is not described in the APIP documentation but is present in theschema.Note: The list above is not complete.Profile VocabulariesVarious vocabulary profiles are listed in Tables P.1 through P.7. The vocabularies are classified based on their usein describing: accessibility, items, metadata or packaging.LOM Vocabularies (LOMv1.0)V 0.65: Public Draft 20130912 245

RTTA APIP ProfilePARCC Item Development Technical GuideTable P.1 lists the LOM [LOM 2002] vocabularies used in the RTTA APIP Profile. PARCC- or RTTA-specificmodifications to the vocabularies are indicated with a .Table P.1: RTTA APIP Profile LOM VocabulariesLOM VocabularyRelation (subset of standard LOM vocabulary)[metadata]Relation (extension of LOM vocabulary)Source RTTAv1.0metadata]Rights (standard LOM vocabulary)[metadata]Text Complexity (Semantic Density vocabulary)[metadata]Valueshasversionisversionofhaspreviewispreviewofyesnovery lowlowmediumhighvery highCCSSO VocabulariesTable P.2 lists the CCSS [CCSS] vocabularies used in the RTTA APIP Profile. PARCC- or RTTA-specificmodifications to the vocabularies are indicated with a (currently none).Table P.2: RTTA APIP Profile CCSS VocabulariesCCSS VocabularyCommon Core Subject Label[metadata]Common Core URI[metadata]ValuesCommon Core State StandardMathematicsEnglish Language Arts - Literacyhttp://www.corestandards.org/math.xmlhttp://www.corestandards.org/ELA-Literacy.xmlCEDS VocabulariesTable P.3 lists the CEDS [CEDS 3.0] vocabularies used in the RTTA APIP Profile. PARCC- or RTTA-specificmodifications to the vocabularies are indicated with a (currently none).Table P.3: RTTA APIP Profile CEDS VocabulariesCEDS VocabularyAssessment Item Type[metadata]ValuesMultipleChoiceFillInTheBlankTrueFalseEssayMatchingShortAnswerLabelingVisualRepresentationShowYourWork246 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideRTTA APIP ProfileCEDS VocabularyValuesOtherConstructedResponsePerformanceTaskOtherExtendedResponseInnovativeReorderingSubstitutionOtherAPIP Vocabularies (APIPv1.0)Table P.4 lists the APIP [APIP Tech 1.0] vocabularies used in the RTTA APIP Profile. PARCC- or RTTA-specificmodifications to the vocabularies are indicated with a .Table P.4: RTTA APIP Profile APIP VocabulariesAPIP VocabularyAssessment Interaction Type[item, metadata]Inclusion Order[accessibility, metadata]ValuescustomInteractiondrawingInteractiongapMatchInteractionmatchInteractiongraphicGapMatchInteractionhotspotInteractiongraphicOrderInteractionselectionPointInteractiongraphicAssociateInteractionsliderInteractionchoiceInteractioninChoiceInteractionmediaInteractionhottextInteractionorderInteractionpositionObjectStageextendedTextInteractiontextEntryInteractionuploadInteractionassociateInteractionscaleInteractionbrailleDefaultOrdertextOnlyDefaultOrdertextOnlyOnDemandOrdertextGraphicsDefaultOrdertextGraphicsOnDemandOrdergraphicsOnlyOnDemandOrdernonVisualDefaultOrderaslDefaultOrderaslOnDemandOrdersignedEnglishDefaultOrdersignedEnglishOnDemandOrderV 0.65: Public Draft 20130912 247

RTTA APIP ProfilePARCC Item Development Technical GuideAPIP VocabularyRelated Element[accessibility, metadata]Response Processing Template[item]Resource Type[packaging]Metadata Schema[packaging]ValuesspokenbrailleTexttactileFilesigningkeyWordTranslationrevealAlternativeRepresentationguidancestructuredMaskscaffoldchunkanswerReductionkeyWordEmphasismatch_correctmap_responsemap_response_pointimsqti_apiptest_xmlv2p1imsqti_apipsection_xmlv2p1imsqti_apipitem_xmlv2p1imsqti_apipresprocessing_xmlv2p1imsqti_apipoutcomes_xmlv2p1associatedcontent/apip_xmlv1p0/learning-applicationresourceimslti_xmlv1p1controlfile/apip_xmlv1p0extension/apipv1p0APIP PackageAPIP Test BankAPIP Item BankAPIP Object BankAPIP TestAPIP SectionAPIP Item248 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideRTTA APIP ProfileRTTA Vocabularies (RTTAv1.0)Table P.5 lists the custom RTTA vocabularies used in the RTTA APIP Profile.Table P.5: RTTA APIP Profile RTTA VocabulariesRTTA VocabularyAcademic Course[metadata]Accessibility Display Feature[accessibility, metadata]Accessibility Support Feature[accessibility, metadata]ValuesAlgebra 1Algebra 2GeometryMath 1Math 2Math 3Not ApplicableMagnificationIncreasedWhiteSpacingReverseContrastAlternateBackgroundColorAlternateTextColorInvertColorColorOverlayAnswerMaskingGeneralMaskingAdditionalTestingTimeKeywordEmphasisLineReaderSpeechtoTextRefreshableBrailleClosedCaptionsReducedAnswersNegativesRemovedChunkingScaffoldingAuditoryCalmingHazardBreaksTextOnlyGraphicsOnlyTextGraphicsNonVisualDirectionsOnlyBrailleContractedBrailleUncontractedBrailleRefreshableBrailleTactileTactileSpokenFileTactileSpokenTextTactileBrailleTextV 0.65: Public Draft 20130912 249

RTTA APIP ProfilePARCC Item Development Technical GuideRTTA VocabularyAssessment Type[metadata]Delivery Mode[metadata]Calculator Type[accessibility]Cognitive Complexity[metadata]Companion Material[accessibility, metadata]ValuesSigningASLSigningSignedEnglishSimplifiedLanguageKeywordTranslationItemTranslationLangageLearnerSupportCognitiveGuidanceSupportSummativeNon-SummativeDiagnosticMid-YearPerformance AssessmentComputer Based DeliveryPaper and Pencil DeliveryBasicStandardScientificGraphingFullFunctionvery lowlowmediumhighvery highcalculatorcalculatorFourFunctioncalculatorScientificcalculatorGraphingcalculatorFullFunctionrulerrulerEightrulerQuarterprotractorcompassstraightEdgenotePapergraphPaperwordProcessingToolequationEditorpopupGlossarynotePadgraphicOrganizerreadingPassagedigitalMaterialphysicalMaterialdictionarythesarusglossary250 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideRTTA APIP ProfileRTTA VocabularyGrade Level[metadata]Graphic Organizer Type[accessibility]Media Type[metadata]Package Type[packaging]RequirementRTTA Assessment[metadata]Scale Shape[item]ValuestextAnnotationspellCheckerwordPredictionvisualDictionarydrawingToolformulaChartKG010203040506070809101112HSVennDiagramTChartStoryMapConceptMapFlowMapText PassageImageTableVideoAudioInteractiveAnimationTranslationTranscriptRTTA PackageCompanion MaterialEnd of YearPerformance BasedMid-YearNarrative WritingResearch SimulationSpeaking and ListeningLiterary AnalysisDiagnostichorizontalverticalsemiCircleV 0.65: Public Draft 20130912 251

RTTA APIP ProfilePARCC Item Development Technical GuideRTTA VocabularyScoring Model[metadata]Status[metadata]Technology-Enhanced Item Type[metadata]Task Type[metadata]ValuescircleHuman ScoringAutomated Machine ScoringKey-based ScoringRule-based ScoringIn DevelopmentIn ReviewRejectedApproved for Field TestApproved for OperationalDeployed to OperationalReleasedSelectedResponseGriddedResponseMultipleSelectConstructedResponseConstructedResponseEquationEditorFillInTheBlankSpecificCharacterSetFillInTheBlankUnconstrainedCharacterSetFillInTheBlankEquationEditorDragandDropHotSpotMultipleChoiceTechnologyEnhancedInlineChoiceComplexDragandDropComplexHotSpotTextExtractionLineGraphBarGraphFractionModelTextFlaggingTextAnnotationItemSpecificWidgetFunctionGraphInteractiveNumberLineCompositeGraphCompositeGraphwithShapeGeometricTransformationZoomNumberLineSolutionSetGraphPolygonGraphScaleSimulationPresentationEditorWebSearchFreeFormGraphicOrganizerResearch Simulation TaskLiterary Analysis Task252 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideRTTA APIP ProfileRTTA VocabularyValuesNarrative Writing TaskNot ApplicablePARCC Vocabularies (PARCCv1.0)Table P.6 lists the PARCC-specific vocabularies used in the PARCC APIP Profile.Table P.6: PARCC APIP Profile PARCC VocabulariesPARCC VocabularyPARCC Alignment Label[metadata]PARCC Item Type[metadata]PARCC Performance Level[metadata]PARCC Score Points[metadata]Response Processing Template[item]ValuesEvidenceStatementSubClaimTaskModelReading - EBSRReading - TECRELA - PCRMath - Type IMath - Type IIMath - Type IIILevel 1Level 2Level 3Level 4Level 5Type 1 - 1 pointType 1 - 2 pointsType 2 - 2 pointsType 2 - 3 pointsType 2 - 4 pointsType 3 - 3 pointsType 3 - 6 pointsEBSR - 2 pointsTECR - 2 pointsPCR Reading - 2 pointsPCR Reading - 3 pointsPCR Reading - 4 pointsTBDV 0.65: Public Draft 20130912 253

Response Processing TemplatesPARCC Item Development Technical GuideAnnex: Response Processing TemplatesThis annex lists the complete XML for the available response processing templates, including a link to the template.The description of the behavior of the template is included with the item encoding .Standard Response Processing TemplatesMatch Correct Response Processing TemplateTemplate Location: http://www.imsglobal.org/question/qtiv2p1/rptemplates/match_correct.xmlCode Listing RPT.1: Match Correct Response Processing Template XML Document01020304050607080910111213141516171819202110Template Validated: 20130528 Copy of IMS TemplateMap Response Response Processing TemplateTemplate Location: http://www.imsglobal.org/question/qtiv2p1/rptemplates/map_response.xmlCode Listing RPT.2: Match Response Response Processing Template XML Document01020304050607080910111213140.0254 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideResponse Processing Templates151617181920Template Validated: 20130528 Copy of IMS TemplateMap Response Point Response Processing TemplateTemplate Location: http://www.imsglobal.org/question/qtiv2p1/rptemplates/map_response_point.xmlCode Listing RPT.3: Match Response Point Response Processing Template XML Document01020304050607080910111213141516171819200.0Template Validated: 20130528 Copy of IMS TemplatePARCC Response Processing TemplatesFuture Guide Version: Include PARCC Response Processing Templates.V 0.65: Public Draft 20130912 255

Response Processing TemplatesPARCC APIP ExamplesAnnex: PARCC APIP ExamplesThis annex contains a set of complete APIP Examples illustrating PARCC content: Illustrative item and interactions An item bank package A section package A test package A response processing template packagePackaging examples include metadata.PARCC Item and Interaction ExamplesThe item and interaction examples are available at:http://www.parcconline.org/document-URL-TBDTo Do: Host PARCC item and interaction examples.PARCC APIP Item Bank Package ExampleTo Do: Develop PARCC example.The item bank package example is available at:http://www.parcconline.org/document-URL-TBDPARCC APIP Section Package ExampleTo Do: Develop PARCC example.The section package example is available at:http://www.parcconline.org/document-URL-TBDPARCC APIP Test Package ExampleTo Do: Develop PARCC example.The test package example is available at:http://www.parcconline.org/document-URL-TBDPARCC Response Processing Template Package ExampleTo Do: Develop PARCC example.The response processing template package example is available at:http://www.parcconline.org/document-URL-TBD256 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideChange LogChange LogDate Version Author Notes20130410 0.3 DR Initial draft release.Metadata changes from 2013-03-11 Metadata Spreadsheet: Dropped the “Element” number from all element descriptions due to confusion inusage Changed “Authors Item ID” to “Entity ID” for LOM alignment Changed “Stimulus Title” to “Title” for LOM alignment Added “Description” for APIP conformance Added “Author” for APIP conformance For “Academic Course”, use “Not applicable” for ELA Changed “PARCC Assessment” to “Assessment” for consistency Changed “Item Status” to “Status” for LOM alignment Changed “Item Status Date” to “Status Date” for LOM alignment Added “Version” for APIP conformance Changed the vocabulary for “Response Type” to use the CEDS 3.0 vocabulary(upper camel case) for “Assessment Item Type", e.g., “MultipleChoice” instead of“Multiple-choice” Added “positionObjectInteraction” and drop “Other” in the “Interaction Type”vocabulary for consistency with APIP Added “Composite Item” for APIP conformance Changed “Task Types” to “Task Type” (singular) for consistency Changed the vocabulary for “Text Complexity” to match the LOM vocabulary Changed “Item Cognitive Complexity” to “Cognitive Complexity” for consistency Changed “PARCC Task Models” to “PARCC Task Model” (singular) for consistency Changed “PARCC Scoring Mode” to “Scoring Model” for consistency Added “Copyright” Changed “Stimulus Media Type” to “Media Type” for consistency Added “Package Type” for APIP conformance Changed “Stimulus MIME Type” to “MIME Type” for consistency Added “Master to Version Relation” for APIP conformance Added a “Scoring” category for score-related elements Added a “Rights” category for rights-related elements Added a “Media” category for data about assets Added required elements for assets, sections, test and packages20130516 0.35 DR Draft for 20130521 Denver Meeting.Editorial and clarifications.Described use of PARCC and APIP Profile vs. default (non validating) APIP Profile.Added device characteristics.Corrected inconsistencies in metadata element names, taxon paths and examples.20130530 0.4 DR Draft for 20130531 Virtual Meeting.Editorial and clarifications.Described use of RTTA versus PARCC-specific APIP Profiles.Added multiplicity field to metadata element descriptions.Added value space or vocabulary source to metadata element descriptions.Metadata Updates: Changed “Grade Level” binding Changed “Status Date” binding Changed “File Size” measure to bytes for LOM conformance Aligned “TEI Type” vocabulary Changed “CCSS IDs” to “CCSS ID” (singular) for consistency Changed “CCSS ID” to use multiple items instead of a comma-separated list Changed “PARCC Evidence Statements” to “PARCC Evidence Statement” (singular)for consistencyV 0.65: Public Draft 20130912 257

Change LogPARCC Item Development Technical GuideDate Version Author Notes Changed “PARCC Evidence Statement” to use multiple items instead of a commaseparatedlist Changed “PARCC SubClaims” to “PARCC SubClaim” (singular) for consistency Changed “PARCC SubClaim” to use multiple items instead of a comma-separatedlist Changed “PARCC Task Model” to use multiple items instead of a comma-separatedlist Changed “PARCC License ID” to “License ID” for consistency Defined RTTAv1.0 vocabulary space Defined PARCCv1.0 vocabulary space Corrected inconsistencies and APIP misalignments in requirements and multiplicityDescribed optional LOM metadata elements.Described file metadata.Described order of metadata elements.Added additional references as needed.Added Acronyms section.Updated Style section to reference Style Guide v 1.1.Added placeholder in Style section for Audio and Video guidelines.Added definitions of QTI and TEI item types in the glossary.Added item behavior and response processing validation.Updated QTI item style sheet information – not used by PARCC.Added QTI Response Processing Templates section with examples.Added Item Template description.Added Response Processing Templates Annex.Added placeholder for Response Processing Template Packaging Example.Added MathML information.Separated Behavior and Accessibility Validation.Added to Profile Annex the initial deltas for the metadata profile.Added to Profile Annex all of the metadata vocabularies.Added individual item attributes.Added ALT tags on images, tables, code listings, …Added description of composite items.Added descriptions of item content elements, rubric blocks.Updated Accessibility section.20130601 0.5 DR Public DraftEditorial.20130627 0.6 DR Draft for reviewEditorial and clarifications.Removed redline tracking notes for metadata element changes.Added list of tables, figures, code.Added even/odd headers and footers.Added additional references as needed.Added additional glossary terms for QTI encodings.Indicated validation status of all XML examples.Added accessibility metadata.Added accessibility metadata vocabularies to the RTTA vocabulary set in the annex.Added MathML attributes and example.Added Item Fragments and XInclude processing.Updated validation tables to align with accessibility updates.Updated all accessibility items to align with accessibility metadata.Added APIP companion material descriptions.Added APIP inclusion order description.Added APIP accessibility info element descriptions.Added APIP element details.Added Accessibility profiling.Added Accessibility terms to APIP vocabulary set in the annex.Updated response processing templates and description to include metadata.258 V 0.65: Public Draft 20130912

PARCC Item Development Technical GuideChange LogDate Version Author NotesAdded file metadata.Added how to include preview image for rendering validation in the package.Added composite item example.Added individual interaction behaviors (Q1, Q2, Q3, Q4, Q5, Q6, Q7, Q8, Q9, Q10, Q11, Q12,Q13, Q14, Q15, Q16, Q17, Q18, Q19, Q20, Q21).Added individual interaction illustrations (Q1, Q2, Q3, Q4, Q5, Q6, Q7, Q8, Q9, Q10, Q11,Q12, Q13, Q14, Q15, Q16, Q17, Q18, Q19, Q20, Q21).Updated item attributes.Updated item elements.Added itembody attributes.Added rubric block elements.Added response variable descriptions to interactions.Added response and outcome declaration elements.Made style description pointers to Style Guide.Added list of APIP vs. QTI schema/documentation discrepancies.Added list of APIP vs. CP schema/documentation discrepancies.Added Scale Interaction.Added packaging folder structure diagrams for packages, item banks, sections, tests.Updated examples for packages, item banks, sections, tests, variants.Added example item packaging with all most options.Added packaging elements.Added versioning and naming structure for profile XSDs.Added test elements.Added test section elements.Added AfA DRD metadata for variants.Added PARCC naming conventions.Added PARCC versioning conventions.20130912 0.65 DR Public DraftEditorial and clarifications.Added additional glossary terms.Clarified that companion material/tools are limited to the list specificed, no extensions.Added scoring type information to items.Clarified use of response processing instructions.Permit approved custom operators for response processing.Restricted rubric blocks to permit only one of each type.Added missing vocabulary terms for interaction type.2013xxxx xx xx Future VersionEditorial and clarifications.Add PARCC classes.Add PARCC response processing custom operatorsUpdate usage guidance for all item behaviors.Add audio and video content guidelines.Add accessibility content guidelines.Add PCI guidelines.Add item bank behaviors.Add PARCC/RTTA profile details.Add PARCC response processing templates.Align item and forms metadata.V 0.65: Public Draft 20130912 259