github-featured / opendataloader-project--opendataloader-pdf

发布

0 发布 77 Git 标签

RSS 订阅源
  • v2.4.0 c09eb5f2de
    比较

    docs(readme): mark auto-tagging as shipped and stop overpromising compliance

    frostbyte_neo 发布于 2026-04-29 12:29:00 +00:00

    Objective: Two messaging problems in README confuse the target audience
    (accessibility teams at organizations seeking open-source remediation
    tools):

    1. Auto-tagging is presented as "Coming Q2 2026" in 14 places, but it
      has shipped (--format tagged-pdf, --format json,tagged-pdf, etc.).
      The Python sample showed a fake auto_tag=True parameter that does
      not exist in CLIOptions.java — the real API uses format="tagged-pdf".
    2. The Problems table marks "PDF accessibility compliance" as Shipped,
      and the AI-AGENT-SUMMARY says we "automate PDF accessibility
      compliance". Auto-tagging alone is not compliance — PDF/UA requires
      alt text, language metadata, validation, and PDF/UA export
      (enterprise-only). Marking compliance itself as shipped overpromises
      what the open-source tier delivers.

    Approach:

    1. Replace every "Q2 2026" / "Coming Q2 2026" / "preview" reference
      with the shipped state. Rewrite the Auto-Tagging Preview section as
      "Auto-Tagging" with the real Python + CLI examples. Update the
      Which-Mode table, Capability Matrix, Accessibility Pipeline table,
      workflow diagram, and FAQ. Remove auto-tagging from the Roadmap.
    2. Tone down the Problems table:
      "PDF accessibility compliance ... Shipped" →
      "Manual PDF remediation cost ... Auto-tag: Shipped. PDF/UA export:
      Enterprise", explicitly framing auto-tagging as "Foundation for
      PDF/UA workflows".
      Update AI-AGENT-SUMMARY: "automate PDF accessibility compliance" →
      "accelerate PDF accessibility remediation ... as foundation for
      PDF/UA". This positions the OSS tier honestly while keeping the
      commercial value clear.

    Evidence:

    • grep "Q2 2026|coming Q2|auto_tag\s*=" README.md → 0 hits.
    • The fake API auto_tag=True is fully replaced by format="tagged-pdf"
      (Python/Node) and --format tagged-pdf (CLI), matching the actual
      values in CLIOptions.applyFormatOption (cli/CLIOptions.java:514-545).
    • The "Coming Soon" reference for Hancom Data Loader integration
      (L279) is intentionally preserved — it is unrelated to auto-tagging.

    Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

    下载附件