> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/learn/specifications/layout-specification.md). # Layout specification This is the layout specification for Saral App. Layout ROIs are captured in this format and configured in the backend for each exam. Internally Saral App uses this json interface for predicting ROIs. Checkout Github release tag and refer Release v1.5 refer `Project-Saral/specs/v1.5/saral-physical-layout-representation-specs.yaml` Release v1.0 refer `Project-Saral/specs/v1/saral-physical-layout-representation-specs.yaml` ![](/files/pB2vHRn34jX15C4BNdJ6) 1. The **Cell** is a field-level grouping of ROIs. It is a group of ROI's which will be predicted and grouped together. For example, Student ID may have 13 ROI's(for 13 digits) and they are all grouped under one cell to represent the student ID field as a whole. 2. ROI(Region Of Interest) is an area of interest in the image that will be used as input to predict/recognize a character/digit/OMR. `Refer` [Source Code Repository](/engage/source-code-repository.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://saral.sunbird.org/learn/specifications/layout-specification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.