From: "S Page" <[EMAIL PROTECTED]> Sent: Monday, August 13, 2007 2:56 PM
> Eep² wrote: > > OK, I added my response there ( > > http://ontoworld.org/wiki/Talk:N-ary_relations#Too_complicated.2Fconfusing_and_just_unnecessary > > ), with more info and an > > example. > > Most of your feedback isn't to do with N-ary relations or unification. I > responded on that ontoworld page but here as well since > more people read the mailing list than watch ontoworld pages. > >> I know this thread is kind of old but I have some suggestions to streamline >> this a bit. The relationships/attributes/properties >> (whatever) are too wordy. > > Wiki editors decide; maybe those on ontoworld.org are long-winded ;-) . > Longer names tend to be more descriptive, and they read > better when in the factbox and the Special:Browse. E.g. > is president of United States > reads better than > president United States Not really. The gap between the text makes it unnecessary to use wordy identifiers. There should really be a colon (:) between the relationship/attribute/property and the value anyway: president: United States >> Instead, these are shorter and more grammatically correct, shorter, less >> syllables, faster to type, etc: > > If/when editing assistance arrives, longer names wouldn't hurt typing. "Assistance" wouldn't be necessary (or at least not as much) if the syntax wasn't so esoteric in the first place... >> has president -> president > > Note that you have to distinguish "has president" from its inverse "is > president of". Likewise "is location of" versus "located > in", etc. Unnecessary as well; "has president" is the same as "is president of", as is "is location of" and "located in". "Paris is location of capital of France" is the same as "Paris is located in France". Much easier to tag Paris is "capital::France" than "is location of::capital of France", "located in::France" or whatever. It's obvious by being the capital of a country that the capital is located in the country... >> Also, with the new property, er, property (attribute? option? parameter?), >> will it work like relationships do now with >> [[relationship::name]] where the "::" (double colons) create a link whereas >> [[attribute:=name]] doesn't create a link? > > Markus Krötzsch proposed in http://www.mail-archive.com/[EMAIL > PROTECTED]/msg00270.html that you always write > [[property:=value]], and if the property is of Type:Wikipage it'll appear as > a link to the page. But that was back in March. > That would require having a type for every property, which isn't always necessary. >> I ask because I need that functionality for both parameters ("relationship" >> and "attribute" in SMW .7) > > You can use templates to insert linked text together with attributes into > Wiki pages. Example? > Please can you give examples of when you would need to link an attribute > value in factboxes and search results? > * It doesn't make sense for most numbers. > * Maybe parts of dates should turn into links, but that's arguably a bug -- > SMW should respect MediaWiki's $wgUseDynamicDates > setting. > * Note that if your attribute is of Type:String and has Wikitext in it, the > behavior is a little undefined, e.g. > [[address:=Michael Jackson ''claims'' to still live at [[Neverland Ranch]] > but has been seen in [[Las Vegas]] for months]] > > It might be appropriate to have Type:String and Type:Wikitext. And maybe the > current hack of specifying a "unit" for dates and > booleans could be replaced with a display format specifier for attributes > that would let you say what parts become links. For > example, Wikipedia physical values sometimes display the power of 10 and the > unit as links. > Well, for my 3D game comparison, in comparing various features, I want to have [[effect::weather]] and then [[weather effect::rain]] appear under "effect::weather" (preferably as a type of it without having to specify yet another relationship that appears alphabetically instead of intuitively under the parent relationship, forcing me to use [[effect weather::rain]] instead). The problem is types only apply to attributes which don't create links (which is why I have to use relationships and am asking if the upcoming "property" can be displayed as links too). See http://www.tnlc.com/wiki/index.php?title=4x4_Evolution for an example of how this becomes unruly with just a few relationships. >> Last, if "property" can also accept just "prop" that would would make it >> easier to use (and type)--"rel" and "att" could be >> shortened forms of the current parameter names too. > > I find I'm often typing property names and :: and :=, but very rarely do I > type "Relation" or "Attribute". If you really want you > can edit getNamespaceArray in the language file. > Right; nevermind about that--I was thinking too literally; relationship/attribute/property names vary. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Semediawiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
