Notes from @ssastry

Some old notes form our parsing team meeting in case it helps ... we are going to be brainstorming about a parser extension mechanism while at the hackathon .. so this might make a cameo appearance there.

• maybe treat as wt = page-wt + <namespace ns="..", title=".."></namespace>
• (but file pages the custom wikitext comes last, category pages it ccomes first)
• cscott's idea is to try to encapsulate structured data inside the opaque "extension" so that we can let folks write specialized editors as "extensions"
• pretend the wikitext is: <special type="category">category description in wikitext</special>, so that you could then write an "extension" to edit the wikitext portion w/o directly exposing it.
• file pages would have more complicated structured data "inside".

this is a bit foggy, have to think about how to preserve appropriate abstraction so that PHP side can expose structured data w/o (necessarily) exposing it to Parsoid core... but leave it in a form that would let a Parsoid extension optionally work on it.

Another important note:

This output is NOT useful for editing clients, only for reading clients. So this is why we are investigating it within the scope of the PCS and not within Parsoid at this time.