From: Moore, D. <dm...@vt...> - 2010-03-26 22:25:33
|
For example, I have a type of page called a Proposal, which has a standard template, form, and category. To group them, I have been adding additional categories for localities or subject areas for proposals. So I have [[Category:Radford]] and/or [[Category:Health]] that are also added to those pages. I would then used DynamicPageList to summarize the pages by the intersections of these categories. Now I want to use properties [[In locality::Radford]] [[Has sector::Health]] (both Type:Page) and use #ask: queries to select the pages I want to list. The question is, should I have these new properties point at pages in the main namespace [[Radford]] or [[[Health]] or would it be better to point them to [[Category:Radford]] [[Category:Health]]. I could avoid the whole issue by making the new properties Type:String, but that seems like a cop out. David Moore Virginia Tech Institute for Policy and Governance 205 W. Roanoke Street (0489) Blacksburg, VA 24061-0489 540-230-6914 (cell) 540-231-6775 (office) NEW 540-231-6722 (fax) dm...@vt... www.ipg.vt.edu -----Original Message----- From: Krabina Bernhard [mailto:kr...@kd...] Sent: Friday, March 26, 2010 3:29 AM To: Moore, David Cc: Semantic MediaWiki Subject: Re: [Semediawiki-user] [SD] Is this a good idea or not Hi David, you should not abandon categories at all. You probably only should use them differently. Think of a category as a placeholder for a certain type of pages that can hold their specific properties, have their specific semantic form or have their drilldown interface. Maybe this [1] can help you further (whether you use Semantic Forms yet or not). Can you describe with an example on how you use categories currently? regards, Bernhard [1] http://www.mediawiki.org/wiki/Extension:Semantic_Forms#Data_design_issues -- Mag. Bernhard Krabina KDZ - Zentrum für Verwaltungsforschung Centre for Public Administration Research Guglgasse 13, 1110 Wien Telefon: +43 1 8923492-27, Fax: +43 1 8923492-20 Mobil: +43 676 849579-27 mailto:kr...@kd... - http://www.kdz.or.at - Plattform Verwaltungskooperation: http://www.verwaltungskooperation.at - RISER: Europäische Meldeauskunft http://www.kdz.or.at/riser ----- "David Moore" <dm...@vt...> schrieb: > I am working on a site and am expanding it to user semantic mediawiki > properties beside existing categories. In many cases the value for > the property is the same as the existing category name (I am assigning > both in a template updated by a partial semantic form). This is > seeming a little redundant (but I don't want to abandon the categories > quite yet). Anyway, Since I use Type:Page for most of these new > properties I was wondering if I should point them at the existing > category pages (instead of having redlink pointing to equivalent pages > in the main namespace). Maybe that enhances semantic drilldown > possibilities in the future. Maybe it's a big mistake. Halfway > through, I'm doubting myself. Is this considered good design or bad > design as far as semantic mediawiki migration is concerned. > > David Moore > Virginia Tech Institute for Policy and Governance > 205 W. Roanoke Street (0489) > Blacksburg, VA 24061-0489 > 540-230-6914 (cell) > 540-231-6775 (office) NEW > 540-231-6722 (fax) > dm...@vt... > www.ipg.vt.edu > > > -----Original Message----- > From: Moore, David [mailto:dm...@vt...] > Sent: Thursday, March 25, 2010 10:10 AM > To: Philipp Zaltenbach > Cc: Semantic MediaWiki > Subject: Re: [Semediawiki-user] Ontoskin3 issues with IE7 > > Which SMW+ extensions depend on the Ontoskins? There are a few > extensions that I want to use, but I also want to stick with the > monobook skin for my users. HaloACL and Collaboration are the main > ones I want to use and I think I have seen that HaloACL needs the > skin. What about Collaboration? > > David Moore > Virginia Tech Institute for Policy and Governance > 205 W. Roanoke Street (0489) > Blacksburg, VA 24061-0489 > 540-230-6914 (cell) > 540-231-6775 (office) NEW > 540-231-6722 (fax) > dm...@vt... > www.ipg.vt.edu > > > -----Original Message----- > From: Philipp Zaltenbach [mailto:zal...@on...] > Sent: Thursday, March 25, 2010 6:19 AM > To: Neill Mitchell > Cc: Sem...@li... > Subject: Re: [Semediawiki-user] Ontoskin3 issues with IE7 > > Hi Neil, > > I have adjusted the requirements for Halo / SMW+ described at > http://wiki.ontoprise.com/smwforum/index.php/Download . > So we recommend Firefox 3.x or IE 8 when using Halo / SMW+. We are > aware > that browsers like IE 6/7 are still wide-spread, but currently do not > > have the resources to ensure that they work properly with our > extensions. > > regards, > Philipp > > Am 25.03.2010 10:20, schrieb Neill Mitchell: > > Hi Jesse. > > > > Thanks for getting back to me. Yes, it is definitely OntoSkin3 that > > kills exhibit with IE. It looks like it's the same issue as Maps > being > > killed - the prototype engine OntoSkin3 uses. If I switch to > Monobook > > then everything is fine. Thanks to Fabian Howahl for his help with > Exhibit. > > > > Best regards > > Neill. > > > > On 25/03/10 06:35, Jesse Wang wrote: > > > >> Hi, Neil, can you provide more details about your problem? If > you're > >> only talking about SRF Exhibit format not working on IE7 on > OntoSkin3, > >> it may not be OntoSkin3's problem. Have you tried other skins and > the > >> Exhibit SRF works fine there? Simile|Exhibit is a MIT project > >> (http://simile.mit.edu/wiki/Exhibit) and not really part of > OntoSkin3 > >> and it is known for compatibility issues with older IE versions. > >> > >> If you're sure it is an OntoSkin3 problem, please send me a link > and I > >> can help you here. > >> > >> Regards, > >> > >> Jesse > >> > >> On Mon, Mar 22, 2010 at 5:14 AM, Neill > Mitchell<ne...@nl... > >> <mailto:ne...@nl...>> wrote: > >> > >> Hi. > >> > >> It appears that OntoSkin3 has serious issues with IE7. For > >> example, the > >> SRF exhibit format does not work at all with IE7. > >> > >> Whilst IE7 is an appaling browser, it unfortunately has many > >> millions of > >> users who aren't going to upgrade soon. Corporates and > Government are > >> way behind when it comes to this. > >> > >> Is there work underway to improve IE7 support? If not, then I > >> think you > >> should state very clearly in your installation guide that > certain > >> aspects do not work at all on IE7. This will save a lot of > people > >> a lot > >> of stress. > >> > >> Cheers > >> Neill. > >> > >> > ------------------------------------------------------------------------------ > >> Download Intel® Parallel Studio Eval > >> Try the new software tools for yourself. Speed compiling, find > bugs > >> proactively, and fine-tune applications for parallel > performance. > >> See why Intel Parallel Studio got high marks during beta. > >> http://p.sf.net/sfu/intel-sw-dev > >> _______________________________________________ > >> Semediawiki-user mailing list > >> Sem...@li... > >> <mailto:Sem...@li...> > >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > >> > >> > >> > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > -- > Philipp Zaltenbach > Halo Team > ontoprise GmbH - know how to use Know-how > - - - > Halo Extension - Want to get involved? > http://smwforum.ontoprise.com/development > - - - > An der RaumFabrik 29; 76227 Karlsruhe; Germany > Tel.: +49 721 509809-0; Fax: +49 721 509809-11 > mailto:zal...@on..., www: http://www.ontoprise.com > Registered Office: Karlsruhe, Germany, HRB 109540 > Managing Directors: Prof. Dr. Juergen Angele, Hans-Peter Schnurr > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user |