From: Markus <ma...@ai...> - 2006-06-25 20:51:34
|
Hi all, after 48 hours of coding (*puh*), I have uploaded an intermediate release o= f=20 SMW on SourceForge. If you want to upgrade, you need to recreate your=20 SMW_LocalSettings.php, since some variables have changed there. The release addresses a number of issues and limitations with the current=20 Inline Query mechanism, in particular: * Inline queries are much more efficient.=20 ** Typical queries can be executed in linear space (assuming that the DB is= =20 not dump and eliminates duplicate rows eagerly). ** Subqueries now have a much better behaviour and should not strongly=20 increase the required resources. ** If the query performance still does not scale up to your use case, there= =20 are added variables you can set to further restrict them in a meaningful wa= y. * Inline queries are more powerful. There are quite some new features for=20 output formatting and searching: ** If you want to search for all articles that have *some* annotation for a= =20 given property, use the syntax [[relation::+]] or [[attribute:=3D+]]. ** If you say [[relationname::*]] or [[attributename:=3D*]], all values of = these=20 annotations are printed, no matter how many there are. ** You can also print the immediate categories given to the selected articl= es=20 by [[Category:*]]. ** You can restrict the search to a certain namespace. E.g. [[Relation:+]]= =20 searches only in the Relation namespace. The main namespace is usually=20 [[:+]]. For searching for categories, use [[:Category:+]]. This feature can= be=20 combined with disjunctions, e.g [[Help:+||:+]] for searching in Help and=20 Main. ** You can now use all output formats with all kinds of results, i.e. not o= nly=20 'table' can be used to print more than one "column". E.g. a query could=20 return a list of names of some persons with their assigned email addresses= =20 printed in parentheses. ** If you don't want the names of the relations, attributes, etc. to be=20 printed (e.g. if you do not have a table output and only one non-subject=20 value), you can set the parameter <ask headers=3D"hide">. As before, you ca= n=20 also select the label for some output by writing [[relation::*|your label]]= =20 etc. ** You can give a label to the first entry of each result (the subject) by= =20 setting the parameter <ask mainlabel=3D"Your label goes here.">. By this, y= ou=20 can also force the subject to be shown in cases where it is normally hidden= =20 (for queries where one or more subjects where specified explicitly by using= =20 [[Subject_article_name]]). * The code for inline queries now is more readable and can easier be extend= ed=20 in the future. There also have been quite some internal cleanups in the=20 datatype parsing code, but these should not have major effects on usage.=20 However, you can now quite savely switch on the reporting of Notices in PHP. * There are some bugs less now. (And maybe some more in other places ;-) Of course, the release has not been tested extensively, so there might be s= ome=20 bugs lurking here and there. But in general inline queries 0.4.3 are a larg= e=20 improvement over inline queries 0.4.1. The official documentation for the n= ew=20 queries still has to be done. Cheers, Markus =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-06-25 21:05:11
|
P.S.: If you find some really bad bugs, you can always switch back to the=20 previous version by just moving the original folder back to the installatio= n=20 directory. No database changes and the like are introduced for 0.4.3. =2D- Markus On Sunday 25 June 2006 22:45, Markus Kr=F6tzsch wrote: > Hi all, > > after 48 hours of coding (*puh*), I have uploaded an intermediate release > of SMW on SourceForge. If you want to upgrade, you need to recreate your > SMW_LocalSettings.php, since some variables have changed there. > > The release addresses a number of issues and limitations with the current > Inline Query mechanism, in particular: > > * Inline queries are much more efficient. > ** Typical queries can be executed in linear space (assuming that the DB = is > not dump and eliminates duplicate rows eagerly). > ** Subqueries now have a much better behaviour and should not strongly > increase the required resources. > ** If the query performance still does not scale up to your use case, the= re > are added variables you can set to further restrict them in a meaningful > way. > > * Inline queries are more powerful. There are quite some new features for > output formatting and searching: > ** If you want to search for all articles that have *some* annotation for= a > given property, use the syntax [[relation::+]] or [[attribute:=3D+]]. > ** If you say [[relationname::*]] or [[attributename:=3D*]], all values of > these annotations are printed, no matter how many there are. > ** You can also print the immediate categories given to the selected > articles by [[Category:*]]. > ** You can restrict the search to a certain namespace. E.g. [[Relation:+]] > searches only in the Relation namespace. The main namespace is usually > [[:+]]. For searching for categories, use [[:Category:+]]. This feature c= an > be combined with disjunctions, e.g [[Help:+||:+]] for searching in Help a= nd > Main. > ** You can now use all output formats with all kinds of results, i.e. not > only 'table' can be used to print more than one "column". E.g. a query > could return a list of names of some persons with their assigned email > addresses printed in parentheses. > ** If you don't want the names of the relations, attributes, etc. to be > printed (e.g. if you do not have a table output and only one non-subject > value), you can set the parameter <ask headers=3D"hide">. As before, you = can > also select the label for some output by writing [[relation::*|your label= ]] > etc. > ** You can give a label to the first entry of each result (the subject) by > setting the parameter <ask mainlabel=3D"Your label goes here.">. By this,= you > can also force the subject to be shown in cases where it is normally hidd= en > (for queries where one or more subjects where specified explicitly by usi= ng > [[Subject_article_name]]). > > * The code for inline queries now is more readable and can easier be > extended in the future. There also have been quite some internal cleanups > in the datatype parsing code, but these should not have major effects on > usage. However, you can now quite savely switch on the reporting of Notic= es > in PHP. > > * There are some bugs less now. (And maybe some more in other places ;-) > > > Of course, the release has not been tested extensively, so there might be > some bugs lurking here and there. But in general inline queries 0.4.3 are= a > large improvement over inline queries 0.4.1. The official documentation f= or > the new queries still has to be done. > > Cheers, > > Markus =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: Hans O. <se...@el...> - 2006-06-25 21:44:50
|
I'll try it out over the coming week. Looks very promising! --Hans Oesterholt Markus Kr=F6tzsch schreef: > P.S.: If you find some really bad bugs, you can always switch back to t= he=20 > previous version by just moving the original folder back to the install= ation=20 > directory. No database changes and the like are introduced for 0.4.3. > > -- Markus > > On Sunday 25 June 2006 22:45, Markus Kr=F6tzsch wrote: > =20 >> Hi all, >> >> after 48 hours of coding (*puh*), I have uploaded an intermediate rele= ase >> of SMW on SourceForge. If you want to upgrade, you need to recreate yo= ur >> SMW_LocalSettings.php, since some variables have changed there. >> >> The release addresses a number of issues and limitations with the curr= ent >> Inline Query mechanism, in particular: >> >> * Inline queries are much more efficient. >> ** Typical queries can be executed in linear space (assuming that the = DB is >> not dump and eliminates duplicate rows eagerly). >> ** Subqueries now have a much better behaviour and should not strongly >> increase the required resources. >> ** If the query performance still does not scale up to your use case, = there >> are added variables you can set to further restrict them in a meaningf= ul >> way. >> >> * Inline queries are more powerful. There are quite some new features = for >> output formatting and searching: >> ** If you want to search for all articles that have *some* annotation = for a >> given property, use the syntax [[relation::+]] or [[attribute:=3D+]]. >> ** If you say [[relationname::*]] or [[attributename:=3D*]], all value= s of >> these annotations are printed, no matter how many there are. >> ** You can also print the immediate categories given to the selected >> articles by [[Category:*]]. >> ** You can restrict the search to a certain namespace. E.g. [[Relation= :+]] >> searches only in the Relation namespace. The main namespace is usually >> [[:+]]. For searching for categories, use [[:Category:+]]. This featur= e can >> be combined with disjunctions, e.g [[Help:+||:+]] for searching in Hel= p and >> Main. >> ** You can now use all output formats with all kinds of results, i.e. = not >> only 'table' can be used to print more than one "column". E.g. a query >> could return a list of names of some persons with their assigned email >> addresses printed in parentheses. >> ** If you don't want the names of the relations, attributes, etc. to b= e >> printed (e.g. if you do not have a table output and only one non-subje= ct >> value), you can set the parameter <ask headers=3D"hide">. As before, y= ou can >> also select the label for some output by writing [[relation::*|your la= bel]] >> etc. >> ** You can give a label to the first entry of each result (the subject= ) by >> setting the parameter <ask mainlabel=3D"Your label goes here.">. By th= is, you >> can also force the subject to be shown in cases where it is normally h= idden >> (for queries where one or more subjects where specified explicitly by = using >> [[Subject_article_name]]). >> >> * The code for inline queries now is more readable and can easier be >> extended in the future. There also have been quite some internal clean= ups >> in the datatype parsing code, but these should not have major effects = on >> usage. However, you can now quite savely switch on the reporting of No= tices >> in PHP. >> >> * There are some bugs less now. (And maybe some more in other places ;= -) >> >> >> Of course, the release has not been tested extensively, so there might= be >> some bugs lurking here and there. But in general inline queries 0.4.3 = are a >> large improvement over inline queries 0.4.1. The official documentatio= n for >> the new queries still has to be done. >> >> Cheers, >> >> Markus >> =20 > > =20 > -----------------------------------------------------------------------= - > > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job = easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > =20 > -----------------------------------------------------------------------= - > > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > =20 |
From: Hans Oesterholt-D. <hoe...@be...> - 2006-07-07 21:42:24
|
I;ve just installed the 0.4.3.2 version. And it's definitly very good! Thanks! --hans Hans Oesterholt schreef: > I'll try it out over the coming week. Looks very promising! > > --Hans Oesterholt > > > Markus Kr=F6tzsch schreef: > =20 >> P.S.: If you find some really bad bugs, you can always switch back to = the=20 >> previous version by just moving the original folder back to the instal= lation=20 >> directory. No database changes and the like are introduced for 0.4.3. >> >> -- Markus >> >> On Sunday 25 June 2006 22:45, Markus Kr=F6tzsch wrote: >> =20 >> =20 >>> Hi all, >>> >>> after 48 hours of coding (*puh*), I have uploaded an intermediate rel= ease >>> of SMW on SourceForge. If you want to upgrade, you need to recreate y= our >>> SMW_LocalSettings.php, since some variables have changed there. >>> >>> The release addresses a number of issues and limitations with the cur= rent >>> Inline Query mechanism, in particular: >>> >>> * Inline queries are much more efficient. >>> ** Typical queries can be executed in linear space (assuming that the= DB is >>> not dump and eliminates duplicate rows eagerly). >>> ** Subqueries now have a much better behaviour and should not strongl= y >>> increase the required resources. >>> ** If the query performance still does not scale up to your use case,= there >>> are added variables you can set to further restrict them in a meaning= ful >>> way. >>> >>> * Inline queries are more powerful. There are quite some new features= for >>> output formatting and searching: >>> ** If you want to search for all articles that have *some* annotation= for a >>> given property, use the syntax [[relation::+]] or [[attribute:=3D+]]. >>> ** If you say [[relationname::*]] or [[attributename:=3D*]], all valu= es of >>> these annotations are printed, no matter how many there are. >>> ** You can also print the immediate categories given to the selected >>> articles by [[Category:*]]. >>> ** You can restrict the search to a certain namespace. E.g. [[Relatio= n:+]] >>> searches only in the Relation namespace. The main namespace is usuall= y >>> [[:+]]. For searching for categories, use [[:Category:+]]. This featu= re can >>> be combined with disjunctions, e.g [[Help:+||:+]] for searching in He= lp and >>> Main. >>> ** You can now use all output formats with all kinds of results, i.e.= not >>> only 'table' can be used to print more than one "column". E.g. a quer= y >>> could return a list of names of some persons with their assigned emai= l >>> addresses printed in parentheses. >>> ** If you don't want the names of the relations, attributes, etc. to = be >>> printed (e.g. if you do not have a table output and only one non-subj= ect >>> value), you can set the parameter <ask headers=3D"hide">. As before, = you can >>> also select the label for some output by writing [[relation::*|your l= abel]] >>> etc. >>> ** You can give a label to the first entry of each result (the subjec= t) by >>> setting the parameter <ask mainlabel=3D"Your label goes here.">. By t= his, you >>> can also force the subject to be shown in cases where it is normally = hidden >>> (for queries where one or more subjects where specified explicitly by= using >>> [[Subject_article_name]]). >>> >>> * The code for inline queries now is more readable and can easier be >>> extended in the future. There also have been quite some internal clea= nups >>> in the datatype parsing code, but these should not have major effects= on >>> usage. However, you can now quite savely switch on the reporting of N= otices >>> in PHP. >>> >>> * There are some bugs less now. (And maybe some more in other places = ;-) >>> >>> >>> Of course, the release has not been tested extensively, so there migh= t be >>> some bugs lurking here and there. But in general inline queries 0.4.3= are a >>> large improvement over inline queries 0.4.1. The official documentati= on for >>> the new queries still has to be done. >>> >>> Cheers, >>> >>> Markus >>> =20 >>> =20 >> =20 >> ----------------------------------------------------------------------= -- >> >> Using Tomcat but need to do more? Need to support web services, securi= ty? >> Get stuff done quickly with pre-integrated technology to make your job= easier >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Gero= nimo >> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&da= t=3D121642 >> =20 >> ----------------------------------------------------------------------= -- >> >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> =20 >> =20 > > > Using Tomcat but need to do more? Need to support web services, securit= y? > Get stuff done quickly with pre-integrated technology to make your job = easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > =20 --=20 ir. Hans Oesterholt-Dijkema, Be Value Apeldoorn, mail: hoe...@be... tel : +31 (6) 46383913; skype: hansoesterholt web : http://www.be-value.nl,=20 http://www.it4humans.org, http://www.elemental-programming.org |
From: S P. <ski...@ea...> - 2006-06-26 23:53:38
|
Markus Krötzsch wrote: > after 48 hours of coding (*puh*), I have uploaded an intermediate release of > SMW on SourceForge. Great! It seems that some of this is in place on http://wiki.ontoworld.org/ > * Inline queries are more powerful. There are quite some new features for > output formatting and searching: > ** If you want to search for all articles that have *some* annotation for a > given property, use the syntax [[relation::+]] or [[attribute:=+]]. > ** If you say [[relationname::*]] or [[attributename:=*]], all values of these > annotations are printed, no matter how many there are. Queries on wiki.ontoworld.org are doing this, e.g. <ask>[[Is located in::*]]</ask> returns every page. So several pages on ontoworld have big tables in them now. If I change it to <ask>[[Is located in::+]]</ask> I don't get a table with article links and the property values, I just get a comma-separated list of articles. <ask format="table"> brings back table format, but still no property values. I added http://wiki.ontoworld.org/index.php/Help:Inline_queries#All_Values_vs._Any_Values to reflect the change. I'm sure Markus is aware of this, just letting y'all know. -- =S |
From: Markus <ma...@ai...> - 2006-06-27 12:38:51
|
On Tuesday 27 June 2006 01:50, S Page wrote: > Markus Kr=F6tzsch wrote: > > after 48 hours of coding (*puh*), I have uploaded an intermediate relea= se > > of SMW on SourceForge. > > Great! It seems that some of this is in place on > http://wiki.ontoworld.org/ > > > * Inline queries are more powerful. There are quite some new features f= or > > output formatting and searching: > > ** If you want to search for all articles that have *some* annotation f= or > > a given property, use the syntax [[relation::+]] or [[attribute:=3D+]].= ** > > If you say [[relationname::*]] or [[attributename:=3D*]], all values of > > these annotations are printed, no matter how many there are. > > Queries on wiki.ontoworld.org are doing this, e.g. > <ask>[[Is located in::*]]</ask> > returns every page. So several pages on ontoworld have big tables in > them now. > > If I change it to > <ask>[[Is located in::+]]</ask> Yes, sorry, this needs to be documented. But it is very simple: There are two kinds of statements that you can put into an inline query: (1) conditions that state which articles you are interested in, and (2) print-out requests, that state what further information about your=20 selected articles should be displayed. Most conditions are of type (1). Type (2) statements are exactly those with= a=20 "*" in them. So [[is located in::*]] is type (2), stating that you want to= =20 get the "is located in" property value for all the articles you selected.=20 But if you do not give further statements, you select all articles (of whic= h=20 you will only see the first 50 or so ;). Now [[is located in::+]] is a type= =20 (1) statement that selects all articles which have some value for the "is=20 located in" property, but it does not state that you want to get this=20 property printed. So to achieve someting that is similar to the former <ask>[[is located=20 in::*]]</ask>, you now have to write <ask>[[is located in::+]] [[is located= =20 in::*]]</ask>. This is the only place where things become more complex than= =20 they used to be. But the advantage is that you can now also print the=20 locations of all cities, whether or not they actually have one: <ask>[[Category:Cities]] [[is located in::*]]</ask> This was not possible before. Adding further print-out statements such as=20 [[features:=3D*]] does not make your table shorter -- you still get all cit= ies=20 =2D- but it gives you additional information in some cases.=20 =46or instance, in our group-intenal wiki, we use attributes to store email= =20 addresses, telephone numbers, messenging accounts, etc. for all group=20 members. In the old version, you could not print this data in one table: if= =20 you wanted to display people's ICQ-numbers, you would automatically restric= t=20 to those people who have an ICQ account at all. If you would print telephon= e=20 numbers and emails in one table, a person with 2 emails and 3 phone numbres= =20 would get 6 rows in the table, since the join was computed. The new version= =20 solves this task easily, and doing less joins makes it more efficient as=20 well. So whenever you meet one of the old condition-less *-queries at ontoworld,= =20 please add a suitable condition (like the +-version) to make the query=20 meaningful again. Cheers, Markus > > I don't get a table with article links and the property values, I just > get a comma-separated list of articles. <ask format=3D"table"> brings > back table format, but still no property values. > > I added > http://wiki.ontoworld.org/index.php/Help:Inline_queries#All_Values_vs._An= y_ >Values to reflect the change. > > I'm sure Markus is aware of this, just letting y'all know. > -- > =3DS =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-06-27 14:12:30
|
Update: version 0.4.3 contained (at least ;) one bug that prevented searche= s=20 for non-numeric attribute values to work properly. The problem is fixed in = a=20 recent minor-minor-release 0.4.3.1 which can now be found at SourceForge. Have fun, Markus On Sunday 25 June 2006 22:45, Markus Kr=F6tzsch wrote: > Hi all, > > after 48 hours of coding (*puh*), I have uploaded an intermediate release > of SMW on SourceForge. If you want to upgrade, you need to recreate your > SMW_LocalSettings.php, since some variables have changed there. > > The release addresses a number of issues and limitations with the current > Inline Query mechanism, in particular: > > * Inline queries are much more efficient. > ** Typical queries can be executed in linear space (assuming that the DB = is > not dump and eliminates duplicate rows eagerly). > ** Subqueries now have a much better behaviour and should not strongly > increase the required resources. > ** If the query performance still does not scale up to your use case, the= re > are added variables you can set to further restrict them in a meaningful > way. > > * Inline queries are more powerful. There are quite some new features for > output formatting and searching: > ** If you want to search for all articles that have *some* annotation for= a > given property, use the syntax [[relation::+]] or [[attribute:=3D+]]. > ** If you say [[relationname::*]] or [[attributename:=3D*]], all values of > these annotations are printed, no matter how many there are. > ** You can also print the immediate categories given to the selected > articles by [[Category:*]]. > ** You can restrict the search to a certain namespace. E.g. [[Relation:+]] > searches only in the Relation namespace. The main namespace is usually > [[:+]]. For searching for categories, use [[:Category:+]]. This feature c= an > be combined with disjunctions, e.g [[Help:+||:+]] for searching in Help a= nd > Main. > ** You can now use all output formats with all kinds of results, i.e. not > only 'table' can be used to print more than one "column". E.g. a query > could return a list of names of some persons with their assigned email > addresses printed in parentheses. > ** If you don't want the names of the relations, attributes, etc. to be > printed (e.g. if you do not have a table output and only one non-subject > value), you can set the parameter <ask headers=3D"hide">. As before, you = can > also select the label for some output by writing [[relation::*|your label= ]] > etc. > ** You can give a label to the first entry of each result (the subject) by > setting the parameter <ask mainlabel=3D"Your label goes here.">. By this,= you > can also force the subject to be shown in cases where it is normally hidd= en > (for queries where one or more subjects where specified explicitly by usi= ng > [[Subject_article_name]]). > > * The code for inline queries now is more readable and can easier be > extended in the future. There also have been quite some internal cleanups > in the datatype parsing code, but these should not have major effects on > usage. However, you can now quite savely switch on the reporting of Notic= es > in PHP. > > * There are some bugs less now. (And maybe some more in other places ;-) > > > Of course, the release has not been tested extensively, so there might be > some bugs lurking here and there. But in general inline queries 0.4.3 are= a > large improvement over inline queries 0.4.1. The official documentation f= or > the new queries still has to be done. > > Cheers, > > Markus =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-06-27 17:43:26
|
Well, I am starting to do hourly releases ;-) I have quick-fixed another ti= ny=20 bug that prevented the important "limit" parameter in <ask> from working.=20 (That is the advantage of immediately using your software on your own=20 production sites -- you are the first who meets the bugs. ;-)=20 New release (0.4.3.2) is up. Cheers, Markus On Tuesday 27 June 2006 16:05, Markus Kr=F6tzsch wrote: > Update: version 0.4.3 contained (at least ;) one bug that prevented > searches for non-numeric attribute values to work properly. The problem is > fixed in a recent minor-minor-release 0.4.3.1 which can now be found at > SourceForge. > > Have fun, > > Markus > > On Sunday 25 June 2006 22:45, Markus Kr=F6tzsch wrote: > > Hi all, > > > > after 48 hours of coding (*puh*), I have uploaded an intermediate relea= se > > of SMW on SourceForge. If you want to upgrade, you need to recreate your > > SMW_LocalSettings.php, since some variables have changed there. > > > > The release addresses a number of issues and limitations with the curre= nt > > Inline Query mechanism, in particular: > > > > * Inline queries are much more efficient. > > ** Typical queries can be executed in linear space (assuming that the DB > > is not dump and eliminates duplicate rows eagerly). > > ** Subqueries now have a much better behaviour and should not strongly > > increase the required resources. > > ** If the query performance still does not scale up to your use case, > > there are added variables you can set to further restrict them in a > > meaningful way. > > > > * Inline queries are more powerful. There are quite some new features f= or > > output formatting and searching: > > ** If you want to search for all articles that have *some* annotation f= or > > a given property, use the syntax [[relation::+]] or [[attribute:=3D+]].= ** > > If you say [[relationname::*]] or [[attributename:=3D*]], all values of > > these annotations are printed, no matter how many there are. > > ** You can also print the immediate categories given to the selected > > articles by [[Category:*]]. > > ** You can restrict the search to a certain namespace. E.g. > > [[Relation:+]] searches only in the Relation namespace. The main > > namespace is usually [[:+]]. For searching for categories, use > > [[:Category:+]]. This feature can be combined with disjunctions, e.g > > [[Help:+||:+]] for searching in Help and Main. > > ** You can now use all output formats with all kinds of results, i.e. n= ot > > only 'table' can be used to print more than one "column". E.g. a query > > could return a list of names of some persons with their assigned email > > addresses printed in parentheses. > > ** If you don't want the names of the relations, attributes, etc. to be > > printed (e.g. if you do not have a table output and only one non-subject > > value), you can set the parameter <ask headers=3D"hide">. As before, you > > can also select the label for some output by writing [[relation::*|your > > label]] etc. > > ** You can give a label to the first entry of each result (the subject) > > by setting the parameter <ask mainlabel=3D"Your label goes here.">. By > > this, you can also force the subject to be shown in cases where it is > > normally hidden (for queries where one or more subjects where specified > > explicitly by using [[Subject_article_name]]). > > > > * The code for inline queries now is more readable and can easier be > > extended in the future. There also have been quite some internal cleanu= ps > > in the datatype parsing code, but these should not have major effects on > > usage. However, you can now quite savely switch on the reporting of > > Notices in PHP. > > > > * There are some bugs less now. (And maybe some more in other places ;-) > > > > > > Of course, the release has not been tested extensively, so there might = be > > some bugs lurking here and there. But in general inline queries 0.4.3 a= re > > a large improvement over inline queries 0.4.1. The official documentati= on > > for the new queries still has to be done. > > > > Cheers, > > > > Markus =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: itsme213 <its...@ho...> - 2006-06-27 19:12:35
|
Markus, This may be an artifact of using Outlook Express, but all your posts show up here with the content as an attachment such as "att7652.txt". Perhaps you are posting as html, or some other setting? Cheers. ----- Original Message ----- From: "Markus Krötzsch" <ma...@ai...> To: "S Page" <ski...@ea...> Cc: <sem...@li...>; <sem...@li...> Sent: Tuesday, June 27, 2006 7:32 AM Subject: Re: [Semediawiki-user] SMW 0.4.3 bonus release is out! > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > -------------------------------------------------------------------------------- > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Markus <ma...@ai...> - 2006-06-28 10:00:12
|
On Tuesday 27 June 2006 21:11, itsme213 wrote: > Markus, > > This may be an artifact of using Outlook Express, but all your posts show > up here with the content as an attachment such as "att7652.txt". Perhaps > you are posting as html, or some other setting? I assume that this is my digital email signature. It is also encoded as a=20 simple text, but not as text/plain as the ending ".txt" that your mailer=20 makes up suggests. The correct mimetype is application/pgp-signature (and=20 this is what is written in the emails -- see the source). Maybe Outlook=20 Express needs some plugin to understand this MimeType properly? It still is= =20 strange if it really converts unknown attachement types to text/plain! As f= ar=20 as Windows users tell me, the free clients Thunderbird and The Bat! would b= e=20 a more sensible choice for reading and managing emails under this OS. Note that there is are two other real text/plain attachements to every mail= on=20 this list: the ads inserted by SourceForge, and the list signature (also by= =20 SourceForge). =2D- Markus > > Cheers. > > ----- Original Message ----- > From: "Markus Kr=F6tzsch" <ma...@ai...> > To: "S Page" <ski...@ea...> > Cc: <sem...@li...>; > <sem...@li...> > Sent: Tuesday, June 27, 2006 7:32 AM > Subject: Re: [Semediawiki-user] SMW 0.4.3 bonus release is out! > > > Using Tomcat but need to do more? Need to support web services, securit= y? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache > > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > > -------------------------------------------------------------------------= =2D- >----- > > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > 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 |