René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Simplify enum deduplication logic in JtdPropertyTest","articleBody":"Issue #99: Enforce RFC 8927 semantics for {} schema and remove AJV compatibility\n\n## Problem\n\nCurrent codebase contains legacy AJV/JSON Schema compatibility where `{}` could mean \"accept anything\".\nThis contradicts RFC 8927: `{}` always means an object with no properties allowed \n(`properties = {}`, `optionalProperties = {}`, `additionalProperties = false`).\n\nThis dual behavior causes complexity and test contradictions.\n\n## Goals\n1. Rip out all AJV-style \"compatibility mode\" handling (`fromRef`, `EmptySchema fallback`).\n2. Make `{}` always RFC 8927 strict (`PropertiesSchema` with no properties, no additionalProperties).\n3. Add an `INFO` log warning whenever `{}` is compiled to help developers spot semantic differences from AJV/JSON Schema.\n4. Rewrite AJV-derived tests to expect failures or exceptions under RFC mode.\n5. Update README.md and AGENTS.md to document the difference.\n\n## Implementation Notes\n- Follow Markdown-Driven-Development: update documentation before code\n- Add INFO-level logging when {} schema is compiled\n- Ensure all tests validate strict RFC 8927 behavior\n- Update user-facing documentation to explain the semantic difference\n\nEOF \u003c /dev/null","author":{"url":"https://github.com/simbo1905","@type":"Person","name":"simbo1905"},"datePublished":"2025-09-28T21:59:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/104/java.util.json.Java21/issues/104"}