Hi,
I am writing to request an SVN account to host source code for an extension that we are currently developing for MediaWiki. This extension is being developed by a collaboration of two Northeastern University students and CIM Engineering, Inc (dba "CIM3").
The Software Idea: With 2,073,813 articles in English and growing, Wikipedia is the world's largest collaboratively edited source of encyclopedic knowledge. As more and more people adding content and using it as reference for their research, it becomes important to know what data resides where on the wiki. Users generally do this by book marking page for future reference. Book marking option in web browser let you bookmark the URL, which is generally the whole page. With the amount of content on any given page, it might still take a while to find the content user is looking for. The aim of the projects is to produce an extension that will add Purple Numbers and collaborative tagging capability to MediaWiki. Purple Numbers will provide the following added functionality in MediaWiki.
1.* High resolution addressability in a wiki page:* With Purple Numbers, MediaWiki user can have high resolution addressibility to a wiki page. The purpose of Purple Numbers is simple: to produce HTML documents that can be addressed with high resolution (also called "fine granularity"). It does this by automatically creating name anchors with static (nidÿÿs) and hierarchical (hidÿÿs) addresses at the beginning of each node, and by displaying these addresses as links at the end of each node.
2.* Transclusion:* Transclusion is the inclusion of part of a document into another document by reference. Transclusion is best explained by an example. Consider the following scenario a user wants to display some data (picture, chart, etc.) about X on page that mentions X in some other content. With Transclusion, user can reference data about X from the X page without copy/paste the data on their own page. Since the data is referenced and not copied, any changees made to the data will reflect on the userÿÿs page also.
3.* Collaborative tagging at node (Purple Numbers) level:* Collaborative tagging (also know as folksonomy, social classification, social indexing and other names) is the practice and method of collaboratively creating and managing tags to annotate and categorize content. In contrast to traditional subject indexing, metadata is not only generated by experts but also by creators and consumers of the content. Freely chosen keywords are used instead of controlled vocabulary.
Some Important Links:
Project Wiki: http://project.cim3.net/wiki http://project.cim3.net/wiki/PMWX
Project Status: http://project.cim3.net/wiki/PMWX
History of Purple Numbers: http://community.cim3.net/cgi-bin/wiki.pl?PurpleNumbers http://www.bootstrap.org/#9B http://www.eekim.com/software/purple/purple.html http://collab.blueoxen.net/cgi-bin/wiki.pl?PurpleNumbers
Transclusion: http://en.wikipedia.org/wiki/Transclusion
Collaborative tagging: http://en.wikipedia.org/wiki/Collaborative_tagging
The Team: http://project.cim3.net/wiki/PMWX#The_Team
Can someone suggest on this?
Thanks --Viral
On 2/26/08, Viral Gupta viralgupta0@gmail.com wrote:
2.* Transclusion:* Transclusion is the inclusion of part of a document into another document by reference. Transclusion is best explained by an example. Consider the following scenario a user wants to display some data (picture, chart, etc.) about X on page that mentions X in some other content. With Transclusion, user can reference data about X from the X page without copy/paste the data on their own page. Since the data is referenced and not copied, any changees made to the data will reflect on the userÿÿs page also.
We already have that - it's our Templates feature.
On Tue, Feb 26, 2008 at 11:46 PM, Andrew Garrett andrew@epstone.net wrote:
We already have that - it's our Templates feature.
There's also the existing Labeled Section Transclusion extension:
http://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion
I think purple is not the same. It's automated and works at a higher level of granularity.
http://www.eekim.com/software/purple/purple.html
I'm curious - how does purple handle insertions and deletions of paragraphs that have already been assigned numbers? The example at the link shows things in ascending consecutive order.
Jim Hu
On Feb 26, 2008, at 7:52 AM, Stephen Bain wrote:
On Tue, Feb 26, 2008 at 11:46 PM, Andrew Garrett andrew@epstone.net wrote:
We already have that - it's our Templates feature.
There's also the existing Labeled Section Transclusion extension:
http://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion
-- Stephen Bain stephen.bain@gmail.com
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
===================================== Jim Hu Associate Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054
There are 2 different kinds of tags (stateful, non-stateful). The non-stateful is Hierarchical addressing which captures the relative hieracrhy of the html element within the document. This is rendered just before the viewing the page which is the right time to determine relative hierarchy. The stateful is handled differently. These are more of permanaent tags added to a element. When the element is deleted the tag is removed along with it.
Thanks --Viral
On Tue, Feb 26, 2008 at 10:44 AM, Jim Hu jimhu@tamu.edu wrote:
I think purple is not the same. It's automated and works at a higher level of granularity.
http://www.eekim.com/software/purple/purple.html
I'm curious - how does purple handle insertions and deletions of paragraphs that have already been assigned numbers? The example at the link shows things in ascending consecutive order.
Jim Hu
On Feb 26, 2008, at 7:52 AM, Stephen Bain wrote:
On Tue, Feb 26, 2008 at 11:46 PM, Andrew Garrett andrew@epstone.net wrote:
We already have that - it's our Templates feature.
There's also the existing Labeled Section Transclusion extension:
http://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion
-- Stephen Bain stephen.bain@gmail.com
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
===================================== Jim Hu Associate Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I see. On the page at the link I now notice that there are things like 5A (039). I'm guessing that 5A is the non-stateful and (039) is the stateful/permalink. So if you deleted the paragraph, the one that's currently 5B (040) would become 5A (040), keeping its stateful tag and changing its non-stateful tag. If you inverted the paragraphs you'd get 5A(040) and 5B(039).
But if you edit inside a paragraph, you'd have to decide whether to treat the stateful tag as unaffected or needing replacement. Given the way wikitext evolves, this could be interesting. It gets close to the old question of whether you ever step into the same river twice. Seems like there will be lots of thought provoking edge cases, such as paragraphs that embed templates or extension tags. Thinking about how to do purple numbering on an embedded RSS feed makes my brain explode! It seems like this is most useful for things like Project Gutenberg, where the text is pretty static.
And you can distribute the extension via mediawiki.org without an svn account. A lot of us just link to our own projects.
Jim
On Feb 26, 2008, at 10:20 AM, Viral Gupta wrote:
There are 2 different kinds of tags (stateful, non-stateful). The non-stateful is Hierarchical addressing which captures the relative hieracrhy of the html element within the document. This is rendered just before the viewing the page which is the right time to determine relative hierarchy. The stateful is handled differently. These are more of permanaent tags added to a element. When the element is deleted the tag is removed along with it.
Thanks --Viral
On Tue, Feb 26, 2008 at 10:44 AM, Jim Hu jimhu@tamu.edu wrote:
I think purple is not the same. It's automated and works at a higher level of granularity.
http://www.eekim.com/software/purple/purple.html
I'm curious - how does purple handle insertions and deletions of paragraphs that have already been assigned numbers? The example at the link shows things in ascending consecutive order.
Jim Hu
On Feb 26, 2008, at 7:52 AM, Stephen Bain wrote:
On Tue, Feb 26, 2008 at 11:46 PM, Andrew Garrett andrew@epstone.net wrote:
We already have that - it's our Templates feature.
There's also the existing Labeled Section Transclusion extension:
http://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion
-- Stephen Bain stephen.bain@gmail.com
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
===================================== Jim Hu Associate Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
===================================== Jim Hu Associate Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054
On Wed, Feb 27, 2008 at 12:21 AM, Jim Hu jimhu@tamu.edu wrote:
And you can distribute the extension via mediawiki.org without an svn account. A lot of us just link to our own projects.
Getting an SVN account is a good idea. It reduces the chances that your extension will break and allows much easier localization. You do have to get approved for it, of course.
Can you throw some light on "Whom to get approval from?"
Thanks --Viral
On Wed, Feb 27, 2008 at 12:01 PM, Simetrical Simetrical+wikilist@gmail.com wrote:
On Wed, Feb 27, 2008 at 12:21 AM, Jim Hu jimhu@tamu.edu wrote:
And you can distribute the extension via mediawiki.org without an svn account. A lot of us just link to our own projects.
Getting an SVN account is a good idea. It reduces the chances that your extension will break and allows much easier localization. You do have to get approved for it, of course.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Feb 27, 2008 at 6:44 PM, Viral Gupta viralgupta0@gmail.com wrote:
Can you throw some light on "Whom to get approval from?"
Brion Vibber.
Jim Hu <jimhu@...> writes:
I see. On the page at the link I now notice that there are things like 5A (039). I'm guessing that 5A is the non-stateful and (039) is the stateful/permalink. So if you deleted the paragraph, the one that's currently 5B (040) would become 5A (040), keeping its stateful tag and changing its non-stateful tag. If you inverted the paragraphs you'd get 5A(040) and 5B(039).
But if you edit inside a paragraph, you'd have to decide whether to treat the stateful tag as unaffected or needing replacement. Given the way wikitext evolves, this could be interesting. It gets close to the old question of whether you ever step into the same river twice. Seems like there will be lots of thought provoking edge cases, such as paragraphs that embed templates or extension tags. Thinking about how to do purple numbering on an embedded RSS feed makes my brain explode! It seems like this is most useful for things like Project Gutenberg, where the text is pretty static.
And you can distribute the extension via mediawiki.org without an svn account. A lot of us just link to our own projects.
Jim
Jim,
When we say that a purple number is stateless (HID), we mean it is not stored in database. Its generated every time page is rendered unlike NID which are stateful and are stored in database along with the wiki page. When a user edits a line in paragraph, nid's dont change, but when a new paragraph (or any other element) is added a new NID (unique to the page) is generated for that paragraph or when a paragraph is deleted, its corresponding NID is also deleted.
One reason we dont want to change NID associated with the paragraph every time it is edited is because we are also implementing transclusion at HID / NID level and we want to show the latest data that the transcluded node has.
Tejas Parikh
On 2/26/08, Viral Gupta viralgupta0@gmail.com wrote:
1.* High resolution addressability in a wiki page:* With Purple Numbers, MediaWiki user can have high resolution addressibility to a wiki page. The purpose of Purple Numbers is simple: to produce HTML documents that can be addressed with high resolution (also called "fine granularity"). It does this by automatically creating name anchors with static (nidÿÿs) and hierarchical (hidÿÿs) addresses at the beginning of each node, and by displaying these addresses as links at the end of each node.
Also, I just realised after rereading that that that's just a fancy way of describing our heading / table of contents system.
wikitech-l@lists.wikimedia.org