This list outlines the remaining steps to transition the OpenFDD project from a "pioneer specification" into a globally adopted document standard.
- Zero-Trust Embed Scrubbing:
<script>,<iframe>,<object>blocked in both parsers. - Compiler Security Rejection:
fdd-packfatally rejects templates containing hostile embedding vectors. - v1.2.0 did:web Identity:
identity.js,signFdd(),parse(),verify(), clientresolveIssuer()+verifySignature(). - Published v1.2.0:
@coreyburns/node-fdd@1.2.0live on NPM. Git tagv1.2.0pushed. - Docs Updated:
README.md,site/index.html, andspec/SPEC.mdall reflect v1.2.0 did:web workflow and CDN tag. - Security Audit: Test Zero-Trust regex against obfuscated
<scr+ipt>payloads.
- Chrome Web Store Submission: Submit the
extension/directory. - Firefox Add-ons Support: Test in Firefox and list on AMO.
-
fdd-validateCLI command: Checks.fddfiles against the W3C VC schema.
- Medical Example:
examples/medical_lab_result.fdd— signed lab results with editable physician notes. - Legal Example:
examples/legal_contract.fdd— consulting agreement with client signature binding. - Finance Example:
examples/bank_statement_v2.fdd— bank statement with transaction table. - Update SPEC.md: Complete rewrite to v1.2 covering did:web lifecycle, trust badge, Zero-Trust policy.
- Developer Sandbox: Live Builder on GitHub Pages for in-browser
.fddgeneration.
- Social Launch: Execute sharing block in README (X, LinkedIn, Reddit, YouTube).
- SaaS Outreach: Identify 3–5 open-source SaaS products and submit ".fdd Export" PRs.
- Browser Vendor Advocacy: Draft a Chromium/Firefox proposal for native
.fddfile handling.