W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

New ResourceMe Version

From: bergi <bergi@axolotlfarm.org>
Date: Fri, 06 Jan 2012 23:46:19 +0100
Message-ID: <4F0779BB.6030005@axolotlfarm.org>
To: WebID XG <public-xg-webid@w3.org>, public-rww@w3.org
Finally I have launched a new version of ResourceMe [1]. First you will
see an optical difference. The design is now based on Twitter Bootstrap.
But more important is what has changed internal and is visible to you,
if you login. Any user with a login (WebID, Google+, Facebook) can now
reply to my blog posts. This is implemented in a very generic way. The
TripleAccessControl ontology [2] is used to describe which user can
write new blog posts, which can reply to existing blog posts and which
can just read them. Smarty [3] is used to render the content. The
buttons to open the forms for creating new data are dynamically
enabled/disabled via JavaScript code. An Ajax interface is used to check
whether a user has access to write the triples for the post or not. With
little effort also other data can be handled.


Some thoughts/questions that came up during development:

URI/URL for global existing things like anonymous agent:
I'm using a anonymous group for users without login and anybody for any
user with a login. Your are automatically member of one or the other
group. Which URI/URL should be used for cases like theses? Currently I'm
using http://localhost/agents#?.

Login-button behavior:
In a later version the login dropdown button should try to used WebID to
login via Ajax. Only if there was a problem the dropdown menu should appear.

Session information:
I'm using now an Ajax interface to ask for the current session
informations (login). Can/should these informations be stored in the
HTML file as RDFa data? Which subject should be used? This would avoid
one round-trip.

Semantic web applications in PHP and threads:
Multithreading is not a must for semantic web applications. More
important for a fast page load is JavaScript code that extends the page
with additional information via Ajax. For example the HTML code of my
blog posts first contains only the URL of the creator, later JavaScript
code replaces the URL with the nick. I'm using this especially for data
that must be fetched from another server. Later I read that even Google+
is doing this [4].


[1] https://resourceme.bergnet.org/
[2] http://ns.bergnet.org/tac/0.1/triple-access-control
[3] http://www.smarty.net/
[4] https://plus.google.com/115060278409766341143/posts/ViaVbBMpSVG
Received on Friday, 6 January 2012 22:46:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 6 January 2012 22:46:50 GMT