Structure and meaning in file reports

Read OPDS category reports in ManYue: separate term, scheme and display label

Compare three category records to distinguish relabelling from shared labels across schemes without treating a category as book identity.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Identical catalogue labels need not identify one category, while one category can receive a different human-readable label. Read an Atom category excerpt as a PDF report in ManYue, tracking term, scheme, label individually. This explains Atom fields used by OPDS without promising XML inspection, field-based filters or automatic category merging.

Prepare three auditable sample records

Externally save the three excerpts below as records A,B,C in order. Their example.invalid addresses are illustrative scheme identifiers, require no access and contain no personal server data. Put excerpts, a three-column ledger and an original comic-entry observation sheet on PDF pages P1–P3. The excerpts omit required feed/entry fields and are not a connectable OPDS service. Before importing, verify full addresses and quotes are legible rather than let report clipping erase evidence.

<category xmlns="http://www.w3.org/2005/Atom" term="river" scheme="https://example.invalid/subjects" label="Rivers"/>
<category xmlns="http://www.w3.org/2005/Atom" term="river" scheme="https://example.invalid/subjects" label="Waterways"/>
<category xmlns="http://www.w3.org/2005/Atom" term="river" scheme="https://example.invalid/collections" label="Rivers"/>

Copy required term instead of guessing from labels

Write river in the first column for all three records and verify term exists. Atom requires category term, a string identifying the category, rather than one uniquely displayed title. Missing term is a structural issue; an informative label does not automatically supply it. An English-looking term does not guarantee the interface displays that word. Retain exact characters without translating identifiers or changing plural forms. Keep table headings separate from field values so explanatory text does not enter the data.

Treat scheme as a categorization-scheme identifier

Copy the complete scheme: A/B use subjects and C collections. Those endings are discussion abbreviations; retain full IRIs in evidence. Optional scheme identifies a categorization system, not an acquisition link, cover location or necessarily accessible web page. A placeholder failing to open is not invalid-category evidence, and it is not a server login base. Check presence before characters. Missing scheme means undeclared, not automatic inheritance from a neighboring record. This exercise compares specified strings without inventing complex IRI normalization rules.

Use label as human-readable text rather than a unique key

Labels are Rivers, Waterways, Rivers. Optional label is user-facing, language-sensitive text; its absence does not remove the category. A/B share term and scheme and differ only in display wording, so the exercise’s identity ledger groups them. C also says Rivers but has another scheme and stays separate. Three records produce two scheme-term combinations and two label strings, coincidentally equal counts under different rules. Visual label equality is not permission to merge comic files or delete entries.

Changing A’s label to Chinese河流 while retaining term and scheme preserves the recorded category combination. A language-sensitive label can change without translating identifiers. Removing C’s label still leaves term and scheme,so retain the category. Actual fallback to a term,blank or other text is not promised for an unknown client.

Check displayed text through entity escaping

Add a P3 example using an amp entity between Maps and Rivers. In XML it denotes the ampersand character rather than new markup; decoded text is Maps & Rivers. Keep raw syntax separate from decoded text instead of copying already decoded browser text back as raw XML. Escaped angle brackets likewise represent characters, not executable tags. In the PDF compare displayed source with expected text. If an entity name appears, inspect possible double escaping during external export before attributing it to OPDS processing in ManYue.

<category xmlns="http://www.w3.org/2005/Atom" term="maps" label="Maps &amp; Rivers"/>

Record only what a real catalogue displays

Read the report in ManYue and bookmark the ledger first. If an authorized OPDS library is already available, optionally record labels, title, author, cover for a known entry without demanding server changes. A visible label alone cannot reconstruct scheme or prove deletion of original term. Without an original response report mark those fields unknown. Keep ordinary OPDS whole-file acquisition separate from OPDS-PSE page streaming; displayed categories do not prove directly readable content. The PDF task remains complete without a personal catalogue.

Trace three kinds of mistaken merging

Treating A/B as different schemes may confuse Waterways with scheme. Merging A/C may compare only Rivers. Filling a missing term from Rivers confuses a required identifier with optional display text. Correct one ledger column and retain the old value instead of bulk-editing server tags. Display differences may involve another entry, language or response, so verify identity and time before speculation. Category identity differs from book identity: one category can contain many books and one book multiple categories. Category count is not comic page count.

Attach all three category records to one original entry and state one book entry,three category records,two explicit combinations. This catches category counts mistaken for book counts. Without a ranking rule,alphabetical order does not imply popularity,and two occurrences of a label do not prove two works.

Reopen and deliver source, identity, display layers

Reopen the report bookmark, cover the ledger and read each term and complete scheme, then explain why two Rivers labels cannot simply merge. Revisit P3’s decoded ampersand while retaining raw amp syntax. Acceptance preserves three records,two combinations,two label strings and unobserved fields; omitting a layer loses the explanation. Leave unperformed reopening or catalogue sampling pending and deliver the source and notes. Recheck responses after changing services; no universal OPDS scheme or automatic app deduplication is claimed.

OPDS link purposes; LANraragi tag queries.

Method references: RFC4287 section4.2.2 Atom categories; OPDS1.2 catalogue specification. Diagrams, report data, counterexamples and ledgers are original exercises.

Version checked on 17 November 2026: the Apple public lookup lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later; see the official App Store for published capabilities. Use self-made PDFs or supported comic images; controls depend on the installed version. External preparation and paper predictions do not constitute device observations. Leave unperformed checks blank.