From: S P. <ski...@ea...> - 2006-09-28 07:36:26
|
I implemented Type:Boolean, complete with garbled fr and de translations. It accepts true/false, 1/0, and language-specific strings. Attribute:HotOrNot [[has type::Type:Boolean]] User:Skierpage [[HotOrNot:=not]] I'd check it in, but the public key I sent Markus and Denny for skierpage isn't accepted at svn.wikimedia.org. Can someone set this up, or does someone want to accept a patch from me? Here is my id_dsa.pub: ssh-dss AAAAB3NzaC1kc3MAAACBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9EAMMeP4C2USZpRV1AIlH7WT2NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f6AR7ECLCT7up1/63xhv4O1fnxqimFQ8E+4P208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RSAHHAAAAFQCXYFCPFSMLzLKSuYKi64QL8Fgc9QAAAIEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+ZxBxCBgLRJFnEj6EwoFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTxvqhRkImog9/hWuWfBpKLZl6Ae1UlZAFMO/7PSSoAAACBAJF3E1jf7QDrrk4HwKwjTSwihlb1CNEM9os7IY7Hfp1LZynCeDMCU2NOU+J/rs8ai+TH5cp/w0NQaGk1iVAx95m+QdmOJO+wnHEZPxvnOqOZhOQSUVjKpRD8nCuJWlp5VYMVx4cfwCKYLu3mCdINIbgBQLJQmiIm2nbHGmQaeTlD DSA-1024 -- =S |
From: Markus <ma...@ai...> - 2006-09-30 18:52:01
|
On Thursday 28 September 2006 09:36, S Page wrote: > I implemented Type:Boolean, complete with garbled fr and de translations. > It accepts true/false, 1/0, and language-specific strings. > > Attribute:HotOrNot > [[has type::Type:Boolean]] > > > User:Skierpage > [[HotOrNot:=3Dnot]] > > > I'd check it in, but the public key I sent Markus and Denny for > skierpage isn't accepted at svn.wikimedia.org. Can someone set this up, > or does someone want to accept a patch from me? Thanks. I will happily upload it if you send me your changes. You new key h= as=20 been submitted and I hope you will get access to SVN soon. =2D- Markus > > Here is my id_dsa.pub: > > ssh-dss > AAAAB3NzaC1kc3MAAACBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9EAMMeP4C2USZpRV1AIlH7W= T2 >NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f6AR7ECLCT7up1/63xhv4O1fnxqimFQ8E+= 4P >208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RSAHHAAAAFQCXYFCPFSMLzLKSuYKi64QL8Fgc9= QA >AAIEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+ZxBxCBgLRJFnEj6= Ew >oFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTxvqhRkImog9/hW= uW >fBpKLZl6Ae1UlZAFMO/7PSSoAAACBAJF3E1jf7QDrrk4HwKwjTSwihlb1CNEM9os7IY7Hfp1LZ= yn >CeDMCU2NOU+J/rs8ai+TH5cp/w0NQaGk1iVAx95m+QdmOJO+wnHEZPxvnOqOZhOQSUVjKpRD8n= Cu >JWlp5VYMVx4cfwCKYLu3mCdINIbgBQLJQmiIm2nbHGmQaeTlD DSA-1024 > > -- > =3DS > > ------------------------------------------------------------------------- > 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=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Semediawiki-devel mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel =2D-=20 Markus Kr=F6tzsch Institute AIFB, University of Karlsruhe, D-76128 Karlsruhe ma...@ai... phone +49 (0)721 608 7362 www.aifb.uni-karlsruhe.de/WBS/ fax +49 (0)721 693 717 |
From: Markus <ma...@ai...> - 2006-10-02 07:37:00
|
Sorry for the confusion, but I have to withdraw the statements I made in my= =20 last email on this issue. I still have to be convinced that we need a Boole= an=20 type. The reason is that instead of a Boolean type, you could simply use a Catego= ry.=20 I.e. instead of [[HotOrNot:=3Dtrue]] you would write [[Category:Hot]]. So w= hy=20 does one need Booleans? The problem with Booleans is that you could still use categories to achieve= =20 similar results. And people would probably end up doing both and then findi= ng=20 out later that they are incompatible. It is a similiar problem as with the= =20 infamous Relation:is_a that some people perpetually re-introduce on=20 ontoworld.org: it just mimics the functionality of categories but is not=20 compatible with normal Category annotation. With Boolean, we might even get= =20 [[Category:City]], [[is a::City]], and [[is City:=3Dtrue]] with the only effect that either one cannot possibly make a query that retu= rns=20 all cities, or that one has to write all three within each single article.= =20 Everone who runs a wiki with many contributors should be worried about the= =20 effort needed to refactor this mess. In addition, Boolean might also look=20 somewhat strange when printed in the article: you don't write "His Hot-Or-N= ot=20 value is [[HotOrNot:=3Dtrue]]". On the other hand, a more general "enum" datatype could be useful. E.g. you= =20 could have an attribute "status" with possible values only=20 being "alpha", "beta", and "stable". But as this introduces all the problem= s=20 I just mentioned, I am unsure whether it really is worth the trouble (e.g.= =20 you can already have articles "Alpha version" etc. to implement "status" as= a=20 relation). The more possibilities we introduce for saying the same thing in= =20 the wiki, the harder it will be to combine the annotations different people= =20 add. Cheers, Markus On Saturday 30 September 2006 20:51, Markus Kr=F6tzsch wrote: > On Thursday 28 September 2006 09:36, S Page wrote: > > I implemented Type:Boolean, complete with garbled fr and de translation= s. > > It accepts true/false, 1/0, and language-specific strings. > > > > Attribute:HotOrNot > > [[has type::Type:Boolean]] > > > > > > User:Skierpage > > [[HotOrNot:=3Dnot]] > > > > > > I'd check it in, but the public key I sent Markus and Denny for > > skierpage isn't accepted at svn.wikimedia.org. Can someone set this up, > > or does someone want to accept a patch from me? > > Thanks. I will happily upload it if you send me your changes. You new key > has been submitted and I hope you will get access to SVN soon. > > -- Markus > > > Here is my id_dsa.pub: > > > > ssh-dss > > AAAAB3NzaC1kc3MAAACBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9EAMMeP4C2USZpRV1AIlH= 7W > >T2 > > NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f6AR7ECLCT7up1/63xhv4O1fnxqimFQ= 8E > >+4P > > 208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RSAHHAAAAFQCXYFCPFSMLzLKSuYKi64QL8F= gc > >9QA > > AAIEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+ZxBxCBgLRJFn= Ej > >6Ew > > oFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTxvqhRkImog9= /h > >WuW > > fBpKLZl6Ae1UlZAFMO/7PSSoAAACBAJF3E1jf7QDrrk4HwKwjTSwihlb1CNEM9os7IY7Hfp= 1L > >Zyn > > CeDMCU2NOU+J/rs8ai+TH5cp/w0NQaGk1iVAx95m+QdmOJO+wnHEZPxvnOqOZhOQSUVjKpR= D8 > >nCu JWlp5VYMVx4cfwCKYLu3mCdINIbgBQLJQmiIm2nbHGmQaeTlD DSA-1024 > > > > -- > > =3DS > > > > -----------------------------------------------------------------------= =2D- > > 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=3Djoin.php&p=3Dsourceforge&CID= =3DDEVDEV > > _______________________________________________ > > Semediawiki-devel mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel =2D-=20 Markus Kr=F6tzsch Institute AIFB, University of Karlsruhe, D-76128 Karlsruhe ma...@ai... phone +49 (0)721 608 7362 www.aifb.uni-karlsruhe.de/WBS/ fax +49 (0)721 693 717 |
From: S P. <ski...@ea...> - 2006-10-13 09:30:17
|
Markus Krötzsch wrote: > I still have to be convinced that we need a Boolean type. > SMWBooleanTypeHandler is only 60 lines of code. I don't yet feel strongly about adding it because I haven't seen Wikipedia pages with an obvious Boolean property in them. I'll make my patch available for Markus and others to evaluate. > The reason is that instead of a Boolean type, you could simply use a Category. > I.e. instead of [[HotOrNot:=true]] you would write [[Category:Hot]]. So why > does one need Booleans? > a) You care about RDF output, and want the boolean datatype: <attribute:HotOrNot rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">false</attribute:HotOrNot> rather than the more opaque: <rdf:type rdf:resource="&thing;Category-3AHot"/> b) You really want to represent a boolean property. Category:Hot and Category:NotHot don't imply a boolean value and its "opposite"; I think the closest you can get is to state an owl:disjointWith relation between them. c) It seems hard to do an inline query that displays one column for the category and its opposite. d) It's easier to write a template that assigns a value to a boolean attribute than one that categorizes to one category or its opposite. > With Boolean, we might even get > > [[Category:City]], [[is a::City]], and [[is City:=true]] > And also a string attribute [[Geographic locus:=City/Town/Village/Suburb/...]] Cleaning up a wiki is hard because humans have a large vocabulary; I don't think providing multiple semantics to express properties makes it significantly harder. > In addition, Boolean might also look > somewhat strange when printed in the article: you don't write "His Hot-Or-Not > value is [[HotOrNot:=true]]". > I write Is he hot? [[HotOrNot:=no]] and it looks fine. > On the other hand, a more general "enum" datatype could be useful. E.g. you > could have an attribute "status" with possible values only > being "alpha", "beta", and "stable". That's technically cool and I think fairly easy to implement! If anyone wants enum, file an enhancement request! I can see just a few benefits over a plain string datatype: a) input validation -- you'd see Status [Oops! "pre-release" is not an allowed value for Status, it can only be one of "alpha", "beta", "stable"]. in the fact box. b) the enum values would have a sort order and support greater than/less than comparisons (by putting a sequence number in smw_attributes.value_num). Regards, -- =S |
From: Thomas B. <bl...@in...> - 2006-10-16 09:47:09
|
* S Page <ski...@ea...> [2006-10-13 11:30]: > Markus Kr=F6tzsch wrote: > > I still have to be convinced that we need a Boolean type. >=20 > > The reason is that instead of a Boolean type, you could simply use a = Category.=20 > > I.e. instead of [[HotOrNot:=3Dtrue]] you would write [[Category:Hot]]= . So why=20 > > does one need Booleans? > > =20 > b) You really want to represent a boolean property. Category:Hot and=20 > Category:NotHot don't imply a boolean value and its "opposite"; I think= =20 > the closest you can get is to state an owl:disjointWith relation betwee= n=20 > them. I think you would only use one category. Either a page is in a category, or it's not. > c) It seems hard to do an inline query that displays one column for th= e=20 > category and its opposite. I think my proposal for an extended table view should solve this: https://sourceforge.net/mailarchive/forum.php?thread_id=3D30539561&forum_= id=3D46648 > > On the other hand, a more general "enum" datatype could be useful. E.= g. you=20 > > could have an attribute "status" with possible values only=20 > > being "alpha", "beta", and "stable". > That's technically cool and I think fairly easy to implement! If anyon= e=20 > wants enum, file an enhancement request! I can see just a few benefits= =20 > over a plain string datatype: > a) input validation -- you'd see > Status [Oops! "pre-release" is not an allowed value for Status,= =20 > it can only be one of "alpha", "beta", "stable"]. > in the fact box.=20 > b) the enum values would have a sort order and support greater than/les= s=20 > than comparisons (by putting a sequence number in smw_attributes.value_= num). I'd like to see that, too. Thomas |