Hi, I don't follow OG development but as host operator a few things are
coming up. The machine's load is gradually climbing over time and some
of that is OG.
Despite a relatively low hit rate on OG it is consuming quite a bit of
resource. If OG started taking off it would take the machine down.
First up: index.cgi requires 0.35s to perform a `perl -c` syntax check.
Any thoughts on putting OG on a mod_perl server? I have mod_perl running
here of course and we'd need to coordinate some apache.conf stuff.
Second: the supersearch.cgi gulps down CPU, often for seconds at a time.
It is a frequent resident of `top` output. This isn't really
acceptable. I'm going to request this feature be turned off unless an
effective optimisation plan or some other way to reduce its impact
here is constructed pretty soon. Sorry about this but it's encroaching
Third: I wonder if there's some way to instruct robots not to spider
parts of your wiki. This ought to speak for itself:
$ grep crawl /var/log/apache/london.openguides.org-access.log | grep 'action=edit' | wc -l
Finally: I posted about a DoS and was wondering what the status of a
solution was. http://openguides.org/mail/openguides-dev/2004-October/000542.html
Paul (any overbearing tone unintentional ;-)
Paul Makepeace .............................. http://paulm.com/inchoate/
"If my elbow was straight, then I'll show oyu mine!"
i've been visiting Berlin a lot and would like to start a Guide so i
can write about the funny and useful places that i find or am shown.
but i don't speak any German and i want to keep it that way - it's an
awful language. ( http://www.crossmyt.com/hc/linghebr/awfgrmlg.html )
i thought about asking for best practise / prior art on multilingual
Guides. the thing is i am not worried about having translations, and i
would sort of rather have any language that people feel like writing
in, squashed onto one page, than separate stuff out, in a way which
might make different language communities feel unwelcome or lapse into
i could do quite a lot with silly icons, and categories can have names in
any language, that's fine, and i'm not worried about knowing what
language category names are in - people will understand or not understand
- and one day we can do some magic with http://omegawiki.org if we like.
how is the OG collective hosting situation? it would rock my world if
i could park this somewhere i would not be subsequently responsible
for breaking and upgrading ;)
Some of you who are more into Semantic Web, Microformats, or Mashups
might be interested in this workshop. Note that for those people not
into writing academic papers, there is also a Scripting Challenge
(with prize) that doesn't require attendance at the workshop and only
requires a short paper for submission. Please pass on to anyone you
think may be interested.
CALL FOR PAPERS
3rd Workshop on Scripting for the Semantic Web
4th European Semantic Web Conference
June 6, 2007, Innsbruck, Austria
and ActionScript are playing a central role in current development
towards flexible, lightweight web applications following the AJAX and
REST design paradigms. These languages are the tools of a generation
of web programmers who use them to quickly create server and
client-side web applications. Many deployed Semantic Web applications
from the FOAF, RSS/ATOM, blog and wiki communities, as well as many
innovative mashups from the Web 2.0 and Open Data movements are using
scripting languages and it is likely that the process of RDF-izing
existing database-backed websites, wikis, weblogs and CMS will largely
rely on scripting languages.
The workshop aims to bring together developers of the RDF base
infrastructure for scripting languages with practitioners building
applications using these languages. Last years Scripting for the
Semantic Web workshop in Budva, Montenegro focused on giving an
overview about the support for Semantic Web technologies within
scripting languages. The special focus of this year's workshop is the
role of scripting languages in the process of populating the Web with
linked RDF data as well as to showcase innovative scripting
applications that consume RDF data from the Web. The second focus of
the workshop is to show how Web 2.0 applications and mashups can
benefit from Semantic Web technologies.
The workshop will include a scripting challenge (conducted for the 2nd
time) which will award a prize to the most innovative scripting
TOPICS OF INTEREST
Topics of interest include, but are not limited to:
* Semantic Web frameworks and APIs for scripting languages
* RDF repositories and query languages implemented using scripting languages
* Reasoning engines implemented using scripting languages
* Semantic Web publishing and data syndication frameworks
* Approaches to crawling Web data and querying distributed data on the Web
* Semantic Web applications using scripting languages
* Approaches to RDF-izing existing applications, such as RDFa and GRDDL
* Mashups that provide RDF views on Web 2.0 data sources such as Google,
Yahoo, Amazon or eBay
* Wikis, weblogs and data syndication systems using RDF
* RDF/OWL editors and authoring environments
* Scripting applications for visualizing Web data.
* Semantic Web Mining and Social Network Analysis
* Mashups that demonstrate the novel capabilities of Semantic Web technologies
* Rapid development techniques for the Semantic Web
* Employment of scripting language characteristics for Semantic Web development
* Scalability and benchmarks of Semantic Web scripting applications
The workshop includes a scripting challenge which will award a prize
(an Apple iPod Video or alternatively Euro 200 cash) to the most
innovative small scripting application or mashup. The application must
be implemented using a scripting language and Semantic Web
technologies. It should access, visualize or combine information from
different sources in new unforeseen ways. Authors of Scripting
Challenge submissions are not required to attend the workshop
personally. Please refer to Tom Heath for further information about
the Scripting Challenge.
Submission deadline: March 30, 2007
Notication of acceptance: April 28, 2007
Camera-ready paper submission: May 7, 2007
Workshop date: June 6, 2007
* Chris Bizer, Freie Universität Berlin, Germany
* Sören Auer, Universität Leipzig, Germany and University of Pennsylvania, USA
* Gunnar Aastrand Grimnes, DFKI Knowledge Management Lab, Germany
* Tom Heath, Knowledge Media Institute (KMi), United Kingdom
We seek three kinds of submissions:
* Full papers - should not exceed ten pages in length.
* Short papers - are expected up to 5 pages.
* Scripting Challenge Submissions - 2 page description of the
application, ideally accompanied with the source code and a link to an
* David Aumüller, Universität Leipzig, Germany
* Danny Ayers, Independent Author, Italy
* Dave Beckett, Yahoo!, USA
* Uldis Bojars, DERI, Ireland
* Dan Brickley, Semantic Web Vapourware, UK
* Richard Cyganiak, Freie Universität Berlin, Germany
* Stefan Decker, DERI, Ireland
* Leigh Dodds, Ingenta, UK
* Edd Dumbill, Useful Information Company, UK
* Frank Fuchs-Kittowski, Frauenhofer Gesellschaft - ISST, Germany
* Daniel Krech, University of Maryland, USA
* Peter Mika, Vrije Universiteit Amsterdam, The Netherlands
* Libby Miller, @Semantics, UK
* Benjamin Nowack, appmosphere web applications, Germany
* Alberto Reggiori, @Semantics, UK
* Sebastian Schaffert, salzburg research, Austria
* Vlad Tanasescu, KMi, The Open University, UK
* Denny Vrandecic, AIFB, Universität Karlsruhe, Germany
* Gregory Williams, University of Maryland, USA
Updated information about the workshop is found on the workshop website
For further information, please send email to sfsw(a)semanticscripting.org
Good idea Ivor.
> > 4. Working the Metatags even further. At the moment the contents of
> > our (as in the OGMK) description tags is pretty sparse, and wholly
> > dependent on the contents of the "Description of this node" field.
> > Pumping the first 150 chars of the article content into the
> > description metatag after whatever the "description of this node"
> > field contains, would give search engines more to go on.
> This is what the page summary is for, no?
Indeed. However loads of ours are blank, or too short to make really
good description metatag content. Something like: If the page summary
is less than X chars long, then making it up to 150 chars using page
content and with a ... at the end to signify truncation" would be a
bonus I'm sure.
Thanks for the suggestions.
I think we should, where possible, raise trac tickets and enhance svn with changes, so everyone will benefit.
See my comments below
> -----Original Message-----
> From: openguides-dev-bounces(a)lists.openguides.org
> [mailto:firstname.lastname@example.org]On Behalf Of Tom
> Sent: 09 January 2007 13:11
> To: OpenGuides software developers' list
> Subject: Re: [OGDev] Fun SEO tricks wanted
> Hi folks,
> Agreed that some URL writing amazon style would be worthwhile, ditto
> inward linking from other sites with high page-rank. Some other
> suggestions from me would be:
> 1. Page order matters. In the standard templates the actual page
> content doesn't start until halfway through the source code. The rest
> of the stuff above that is just the standard navigation that appears
> on the right in many Guides, such as Recent Changes. This ordering
> should ideally be swapped in the templates, with page content first,
> following by any generic stuff. Obviously the actual positioning of
> the elements visually can be done with CSS. At the moment we have the
> worst of both worlds(*): content positioned on the left, but actually
> further down in the code than the stuff that's positioned on the
> * actually London has this sorted - credit where credits due ;)
Raised ticket #170: http://dev.openguides.org/ticket/170
> 2. Titles Attributes on Links. Especially for things like Categories
> and Locales. This should be a 1minute hack, and can't do any harm.
Raised ticket #171: http://dev.openguides.org/ticket/171
> 3. Inter-guide Linking. Not even anything fancy like wiki-links across
> guides, but maybe even just links in footers to other guides nearby.
> We all have good pagerank, so lets use it.
This is ticket #76: http://dev.openguides.org/ticket/76
> 4. Working the Metatags even further. At the moment the contents of
> our (as in the OGMK) description tags is pretty sparse, and wholly
> dependent on the contents of the "Description of this node" field.
> Pumping the first 150 chars of the article content into the
> description metatag after whatever the "description of this node"
> field contains, would give search engines more to go on.
This is what the page summary is for, no?
> 5. More site-wide navigation. I like what OGL has done with the
> category-style navigation on the Node List pages. Something like this
> on every page would be great from a SEO and usability perspective.
This is probably guide specific. However, if someone could think of a generalised
way of doing it, we could ship a suitable navbar template.