Distributed extensibility

Use cases

Anchor(htmleditors)

HTML Editors

• Round-trip metadata across sessions, maintaining a strong metadata association that is resilient to subsequent editing operations by other user agents
  • Possible round-trip formats:
    • HTML file
    • Document fragments, such as during copy paste
• Such metadata can include:
  • Editor state
    • Author information
    • Relationship to other files
    • References to the original source repository
• Rich formatting information
  • Links back to editing templates
  • Identifying multiple markup components as composite controls
• Intelligently edit third-party extended markup, even markup that doesn't run directly a web browser
  • Preserve extended markup integrity (lossless pass-through)
  • Uniquely identify extended markup to the user, e.g. distinguish from validation errors
  • Avoid the need to define new parsing rules to identify and edit extended content
    • Note: Validation of the content of the extension would still necessitate custom rules, but by constraining the form of the extension to a well-defined set, the scope/complexity of the custom rules can be minimized.
• Such extended markup may include:
  • FBML
  • PHP
  • Declarative script library extensions (e.g. dojo dijit)

Namespaces in legacy HTML

Requested namespace support

• MathML
• SVG
• XForms
• RDF
• WAI@role
• ARole
• Dublin Core
• SMIL
• SSML