Submission f0197628c76c

Event log

Review

Decision: reject
Classification (automatic): Software Engineering (cs.SE)

Reject: Requirement 5.

The paper states that static generation uses “a flag that adds file extensions to links and removes the submission workflow.” It later claims that “a generated page differs from the served one only where the static site drops the submission workflow.” These statements conflict because rewritten links constitute a second difference. To satisfy requirement 5, state both differences and delimit what the shared rendering path guarantees, or revise the implementation and evidence so the exclusivity claim is true.

## Remarks

- Requirement 12, Register: The conflicting claim quoted above overstates the equivalence between generated and live pages. The manual requires results stated at the strength the description supports.

- Requirement 12, Grammar and mechanics: “A submitter told which requirement failed, and shown the passage that failed it, has a defined next task” contains misplaced commas. The sentence needs an opening comma after “submitter” and no comma before “and,” or an active rewrite.

- Requirement 12, Grammar and mechanics: “Every other requirement returns a written remark and the archive publishes the paper regardless” joins independent clauses without a comma or period.

- Requirement 12, Metaphor: “the identifier survives revision” uses a figurative verb. State that the identifier remains unchanged across revisions.

- Requirement 12, Vague references: “fails on those grounds however it looks on screen” does not name the applicable ground. Name the extractable-text requirement and replace the visual metaphor with “regardless of its rendered appearance.”

- Requirement 12, Metaphor: “the archive abandons a review after fifteen minutes” attributes intent to software. State that the archive terminates the review after fifteen minutes.

- Requirement 12, Metaphor: “the submission waits on its status page” attributes an action to the submission. State that its status remains held until the owner decides.

- Requirement 12, Terminology: “Listings answer at /list/{subject}/{period}” assigns the server’s action to the listings. State that the server provides listings at that route.

- Requirement 12, Metaphor: “a paper that reaches the listing through a secondary subject” uses figurative movement. State that the paper appears in the listing because the listed category is its secondary subject.

- Requirement 12, Metaphor: “The archive also writes itself out as a static site” should state directly that the archive generates a static site.

- Requirement 12, Vague references: “the documents in both forms” leaves the forms unnamed. Name the rendered-page and Markdown-source forms.

- Requirement 12, Terminology: “the static site drops the submission workflow” uses informal developer language. State that the static site omits the submission workflow.