[EMAIL PROTECTED] wrote: > I have installed WikiMedia, SMW and enabled templates. I am attempting > to create a model page from one of many similar entries. I am > attempting to duplicate the OpenType specification record into a > collaborative, super-indexed site. > > http://www.opentypology.org
That is very cool. > So far, I have focused on creating one "good" page because the > information will be similar for most of the pages. Most pages will > document OpenType "tags". I have run into several quandries so far: > > Is the "Facts about..." a template? No, it's generated by code in SMWSemanticData::printFactbox(), which invokes methods printRelations(), printAttributes(), and printSpecialProperties(). It might be nice if it were more flexible and reusable; we would need specific use cases to help guide a redesign. How do you want to change it? > Is this editable? Some of the strings are modifiable, but other changes would require modifying PHP code. Some attributes have some control over their display in the factbox. > I would like to > have it run down a right column, like a wikipedia taxobox. Is that > done with a CSS float? I believe you could create a style for <div class="smwfact"> to make it appear elsewhere in the layout. > To create the semantic data, I wrote a narrative section, then tagged. > I would rather have most of the semantic data presented in ONLY the > "Facts about.." box (although others could still tag elsewhere). Is > this possible? You can hide the inline display of facts using blank alternative text to display, e.g. [[Recommended Default:=true| ]] You might also want to use a template to standardize the semantic properties, see e.g. http://ontoworld.org/wiki/Template:Person (Note that many of the templates on ontoworld.org rely on the ParserFunctions MediaWiki extension.) Templates tend to produce a box of information; I agree it's kind of weird to then repeat the information in the factbox. So your template could instead produce invisible attributes and relations using the "| " trick rather than a visible table. > The current method includes Categories. However, every major category > is also an Attribute. Why? You can query on categories, and they are exported in RDF. So why do you need both [[Category:Feature Tags]] and [[Tag Class:=Feature Tag]] ? Also, inline queries will find pages in subcategories, so you don't have to categorize a page in both Tags and Feature Tags. > Is there a way to replace category pages with > Specially formated "saved searches" that are predefined, with > Category-like names? It doesn't seem easy to change the display of a kind of page, hence the manually-inserted {{ask}} template all over ontoworld.org that produces inline queries that show use of the topic of that page. You could do something similar on your site with a {{info about pages in this category}} template. What is it you want to achieve? Looking at http://www.opentypology.org/wiki/index.php?title=Liga ... If Lookup method and Lookup type have a small set of possible values, then they could usefully be relations rather than attributes, so they will link to pages that document what values like "GSUB" and "4" mean. E.g. the [[Liga]] page would have [[Lookup method::Lookup method/GSUB|GSUB]] and the page [[Lookup method/GSUB]] documents "GSUB". Hmm, and if it's strictly limited, then maybe SMW should provide a way to restrict the possible values of the relation "Lookup method", just as we are considering for enumerated attributes. I think you'll learn a lot if you make a second "good" page, and then create a page with inline queries that display information from both pages. I put a test inline query in http://www.opentypology.org/wiki/index.php?title=Category:Feature_Tags for grins, if you like it make it a template. I see you want Type:Boolean for Attribute:Recommended Default Status, that's a vote for implementing the boolean feature in a future release :-) Good luck, -- =S Page (a talkative, yet junior, SMW developer :-) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Semediawiki-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/semediawiki-user
