Port-authority circulars are published as HTML pages on the authority's public notice board, complete with navigation menus, a sidebar of unrelated links, and the actual notice text in the page body. What is the most appropriate extraction approach?
Select an answer to reveal the explanation.
Short Explanation
You have structured, machine-readable HTML, so use an HTML parser to find the notice body and skip the navigation and unrelated sidebar links. That keeps the useful text without making you rely on a screenshot or include page clutter.
Full Explanation
Using an HTML-parsing approach to isolate the notice body and discard navigation, sidebar, and boilerplate markup is correct because the source has a document structure that a parser can use to target the elements containing the notice text. This also systematically removes surrounding page content that is irrelevant to the notice. Saving raw HTML bytes without parsing would preserve the tags, navigation link text, and sidebar content alongside the notice, diluting the useful semantic signal and potentially reducing retrieval quality. Capturing each page as an image and applying OCR is a poorer fit when the text is already digitally available in the HTML: OCR adds recognition error and processing cost without recovering anything unavailable from the source. Treating HTML tags as meaningful content is also wrong because tags provide structure rather than the notice’s substantive meaning; embedding their syntax adds noise. The exam-relevant caveat is to choose an extraction method that uses the source’s actual structure, rather than defaulting to OCR or skipping parsing. As a practical check, inspect the extracted text and confirm that the notice remains while the navigation, sidebar, and boilerplate are absent.