Decide where the work belongs
Name the filing decision
Record how the reader identifies the downloaded file later and whether the visible title carries date, revision, or subject information. Note if a wrong extension or removed character could cause another process to treat the file differently.
Map naming variants
List formats, Unicode characters, duplicate names, revisions, and download paths that produce different results. Compare the visible label and saved name across direct download, retry, and alternate representation without guessing at a browser's behavior.
Choose the queue
Queue identity correction when the saved bytes belong to another document, naming-policy work when information is lost, or explanatory copy when normalization is intentional but surprising. Attach names and document identifiers from one reproducible case.
What to carry forward
Prioritize the mismatch when readers can file, share, or process the wrong-looking document or cannot distinguish revisions after download, without reopening or rechecking the source. A documented normalization that preserves identity can rank below collisions and misleading extensions.
Technical background: RFC Editor reference.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow