Hi Subbu, I have another two question: 1. According to the roadmap, you will research the “HTML-only wiki support” and “DOM-based templating”. Does it mean that if you launch these functions, wikitext will no longer be supported, even the round-trip doesn’t work? 2. In “MediaWiki_DOM_spec” there are a lot of discussing and implemented status. Will the parsoid output change a lot in the future? What is the approximate percentage?
Thanks Feng Yi
On Wed, Sep 11, 2013 at 8:00 PM, wikitext-l-request@lists.wikimedia.orgwrote:
Send Wikitext-l mailing list submissions to wikitext-l@lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.wikimedia.org/mailman/listinfo/wikitext-l or, via email, send a message with subject or body 'help' to wikitext-l-request@lists.wikimedia.org
You can reach the person managing the list at wikitext-l-owner@lists.wikimedia.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Wikitext-l digest..."
Today's Topics:
- Re: Diff between real Parsoid result and Introduction page (Subramanya Sastry)
Message: 1 Date: Tue, 10 Sep 2013 13:13:59 -0700 From: Subramanya Sastry ssastry@wikimedia.org To: wikitext-l@lists.wikimedia.org Subject: Re: [Wikitext-l] Diff between real Parsoid result and Introduction page Message-ID: 522F7D87.2010905@wikimedia.org Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 09/10/2013 02:18 AM, Feng Yi wrote:
Hi, I'm in google wiki knowledge team and currently work on Parsoid. I found there are some diffs between http://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec and real Parsoid output. For example: /RFC 1945 / in page: <arel="mw:ExtLink/PMID" resource="http://purl.org/commons/html/pmid/20610307" href="//www.ncbi.nlm.nih.gov/pubmed/20610307?dopt=Abstract <
http://www.ncbi.nlm.nih.gov/pubmed/20610307?dopt=Abstract%3E"
about="#_:PMID-20610307-1234" class="external mw-magiclink-pmid">PMID 20610307
</a> in Parsoid: *<a typeof="mw:ExtLink/RFC" href="//tools.ietf.org/html/rfc1945 <http://tools.ietf.org/html/rfc1945>" rel="mw:ExtLink/RFC">RFC 1945</a></p>* / / I have removed the "parsoid-data" and other global tags, but still a lot of diff. The page is updated several days ago, so is the released Parsoid not newest?
Hi Feng,
The spec for RFC is this:
<a rel="mw:ExtLink/RFC" href="http://tools.ietf.org/html/rfc1945" resource="urn:ietf:rfc:1945" about="#_RFC-1945-1234" class="external mw-magiclink-rfc"> RFC 1945
</a>
and output after discarding data-parsoid is:
<a rel="mw:ExtLink/RFC" href="//tools.ietf.org/html/rfc1945" typeof="mw:ExtLink/RFC"> RFC 1945
</a>
So, there are diffs, yes. We are in the process of cleaning up our spec (and actively making a few changes) -- in some cases, the spec is outdated, and in other cases, the spec has information about proposed changes (but not yet implemented). In the next week or so, we'll try to clean up our spec (removing/updating outdated information, or adding annotations where the spec is proposing changes).
Thanks for alerting us about the mismatch.
Subbu.
On Wed, Sep 18, 2013 at 7:51 AM, Feng Yi zlfengyi@google.com wrote:
I have another two question:
- According to the roadmap, you will research the “HTML-only wiki
support” and “DOM-based templating”. Does it mean that if you launch these functions, wikitext will no longer be supported, even the round-trip doesn’t work?
At least initially, HTML-only wiki support will mean that it is *possible* to install an HTML-only wiki, not that it is required.
DOM-based templating is an orthogonal issue; long-term we are trying to make template nesting more sane.
2. In “MediaWiki_DOM_spec” there are a lot of discussing and implemented
status. Will the parsoid output change a lot in the future? What is the approximate percentage?
Sections which are not explicitly marked w/ discussion or 'implementing' are expected to remain stable. We reserve the right to change the spec if needed, but most of it is in production use and working satisfactorily and is not expected to change. The most in-flux bits are the bits which are not currently implemented and/or supported by Visual Editor. Our process is to work out a spec proposal with the Visual Editor team, implement it in Parsoid, then implement support for the new feature in Visual Editor. During these stages the spec is often found deficient in some way and is fixed. Once the feature lands in Visual Editor and is deployed, we have reasonable confidence that the spec is correct and will not need to be changed further. --scott
On 09/18/2013 04:51 AM, Feng Yi wrote:
Hi Subbu, I have another two question:
- According to the roadmap, you will research the “HTML-only wiki
support” and “DOM-based templating”. Does it mean that if you launch these functions, wikitext will no longer be supported, even the round-trip doesn’t work?
For Wikipedia, we plan to store both HTML *and* Wikitext for quite a while. This gives us time to perfect the HTML-only mode of operation with a low risk to existing content.
Eventually, Parsoid can be used as a wikitext front-end that converts from stored HTML to wikitext for editing, and then converts the modified wikitext back to HTML for storage. This mode of operation is already used in the upcoming 'Flow' discussion system.
- In “MediaWiki_DOM_spec” there are a lot of discussing and implemented
status. Will the parsoid output change a lot in the future? What is the approximate percentage?
We are currently doing some clean-up in the spec:
* Transclusion parameters are always wrapped in a parts array (see https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Transclusion_conte...). There is another tweak to the parameter structure coming. See [1].
* mw:WikiLink/Interwiki becomes mw:ExtLink. See [2].
* mw:ExtLink/* will become just mw:ExtLink. The information can mostly be extracted by matching a href prefix. Client-side rendering of numbered external links will be handled with CSS as discussed in bug 53505. See [2].
* mw:WikiLink/Category becomes mw:PageProp/Category as these are not really links. They don't render at all in the page, don't accept a caption etc. See [2].
* mw:WikiLink/Language becomes mw:PageProp/Language - same as with categories. See [2].
* Transclusion-affected attributes are moved to data-mw according to https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Transclusion-affec...
Once these changes are deployed (likely to happen in the next weeks), the Parsoid spec version will be incremented to version 1. After this cleanup, we expect the spec to remain stable for a while.
Gabriel
[1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53135 [2]: https://bugzilla.wikimedia.org/show_bug.cgi?id=53432
wikitext-l@lists.wikimedia.org