Hello Steve,
One thought is to enable SMW for footnoted, multilingual properties: one defines Property:Foo as Type:Text, and is able to then reference Foo@eng for instance in SMW's parser functions.  An inline annotation could follow this format:
    [[propname@langcode ^f1,...,fn :: propvalue]]

with these additional two new parser functions: 
 
{{#footnote-keep:fn|dc:source=xxxxxx|other footnote params}}
    {{#footnote-show:f1,...fn}}
Ideally the footnote reference would be formatted within the text (possibly, in multiple citations) where the property value is being set.

Existing parser functions would be modified to support language designations:
  {{#set: propname@eng = propvalue}} ... propvalue being set is that in the English language
  {{#ask: [[propname@eng :: propvalue]] }} ... propvalue queried is that in the English language

The factbox, browse and maybe other SMW utilities I don't know about right now, would need to be tweaked as well.
Last point: clearly, Type:Code properties would not be language-aware.

Thanks for your inquiry!
John
On 11/6/2013 7:22 AM, Chenoweth, Stephen V wrote:

Everyone,

 

Any ideas for a serious class project, like in PHP, perhaps, that also would be useful to SMW?

 

I have 23 talented junior CS majors who built a SMW-based Wiki this fall.  When populated with data, it will show the flow of concepts related to our courses, etc. at Rose-Hulman Institute of Technology.

 

This same class is next heading into a course in software design.  I would love to give them a design and programming project to do, which could benefit this particular Wiki they built, but which also would be of interest to you, the SMW community.  I suggested PHP, above, because a key goal of the design course is for the students to become adept at software patterns and other OO skills.

 

As a student project, this should not be something critical in your development path, but, ideally, if they produced a high quality result, it is something that might end up rolled into the general product or might become an extension.  In previous classes, we have ended up submitting results back into SourceForge.

 

So, do you have specific ideas that come to mind?  Or, do you have a “wish list” already, that they could go look at, and choose for themselves?

 

We would love to have this class be the test case for an ongoing relationship.

 

Your recommendations are greatly appreciated!

 

Steve Chenoweth

Assoc Prof, CSSE

RHIT

 



------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk


_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel