Where do we go from here?
Nancyd
done (and what can be done). To make sure I "get it", I'm trying to
make a simple foaf application for facebook as well as a "foaf
repository" google app engine application (saves me sorting hosting
issues for now). I have not made particularly impressive progress,
but there's a fair bit of stuff that's new to me, so I'm not
surprised. The foaf application will serve as a template for the
IntentMap application, but with foaf, at least I have specs now :-)
I'll probably need some help testing facebook integration at some
point.
I'm also open to other hosting options - Google App Engine is
convenient, but it can tie you to a particular platform, so I'm trying
to make sure I don't code myself into a corner.
How do want to go about fleshing out the IntentMap spec? use the
aboutus.org page?
Est-ce qu'on continue la discussion en français? It's all the same to
me.
Marc-Antoine Parent
Second, GAE specialization may be an issue. Question: are you using Django? Because that might gain us some level of platform-independence.
Guess not, since you have more java than python experience. But I would not worry too much about it. We're more interested in format than technology.
What matters are clean APIs.
The Aboutus.org is as good a starting point as any. I added some references there yesterday.
Actually, I think we should decide on a time to all trash it out together, and have a good videoconference/collective editing session (using Google Wave? That's what it's for)
(If you all agree, let's make a doodle.)
Français/English: We're all francophones now. Dunno if anybody anglophone may join at some point. I (unfortunately) vote for English, because code/design documents should be in English, and discussing them in French will just turn to a linguistic mush.
Cheers,
Marc-Antoine
Nancyd
already wrote the magic; I only have to bend it to my will... not here
yet). That's keeping me from figuring out the details of GAE
persistence (yay) and it should keep thing somewhat neutral (yay).
Scheduling: well, I don't know about you, but day job + family leaves
me only a little bit of time, often in 10 minutes here and 30 minutes
there increments, so it may be difficult to find a a good time (unless
you're all up at 5:30 or 6:00. AM.
French/English: I code/think in English, so that works for me
RDF: what I've found so far is that "it's just XML" so that's not too
bad; still, if you have specific reading suggestions, I'll take them
(it's never "just XML" :)
Marc-Antoine Parent
Le 2010-07-01 à 09:53, Nancyd a écrit :
> I'm doing it using grails/groovy, with a JPA layer (someone else
> already wrote the magic; I only have to bend it to my will... not here
> yet). That's keeping me from figuring out the details of GAE
> persistence (yay) and it should keep thing somewhat neutral (yay).
Sounds good on both counts.
> Scheduling: well, I don't know about you, but day job + family leaves
> me only a little bit of time, often in 10 minutes here and 30 minutes
> there increments, so it may be difficult to find a a good time (unless
> you're all up at 5:30 or 6:00. AM.
I could be...
> RDF: what I've found so far is that "it's just XML" so that's not too
> bad; still, if you have specific reading suggestions, I'll take them
> (it's never "just XML" :)
Very true. I guess you've read the primers? They were good enough to get me started. But I sense you may already be past that stage.
http://www.w3.org/TR/rdf-primer/
http://www.w3.org/TR/xhtml-rdfa-primer/
Another intro:
http://www.rdfabout.com/quickintro.xpd
Also good further reading:
http://www.w3.org/TR/cooluris/
To go further, we may have to get into specific needs.
Cheers,
Marc-Antoine
Seb Paquet
I've updated the page on http://www.aboutus.org/IntentMap.org,
including a link to the live paper notes we took at the initial
session. Feedback and edits are welcome; we need to make sure we
remain on the same page as far as overall vision and goals go. For now
let's use it as the home page for the project, and this mailing list
to follow what we're up to.
At this stage, I think it is very worth it for each of us to review
prior art (section 4).
* The DOAP links should be given careful scrutiny, as we're pretty
much envisioning a generalization of DOAP. (I'm not sure yet whether
we should aim for backward compatibility, though).
* 43things (thanks Yves Otis for the tip!) is also worth looking at;
it is super-understandable and usable, but isn't based on any
standard, AFAIK. (It has an API, though: http://www.43things.com/about/view/web_service_api)
A fuzzy description of "What we're building" might be: a cluefully-
designed hybrid of DOAP and 43things that is at the state of the art
of personal social web technology.
Assuming that this much is assimilated, I think we're probably at the
stage of trying to (at least roughly) agree on the structure of the
intent description. I believe a few core virtues to aim for here are:
simplicity, extensibility, and reuse of structures that already exist
wherever appropriate.
This job is probably best done on a wiki. AboutUs is not really made
for that. Does anybody know if there a wiki out there that is
dedicated to this kind of hashing out of specs? If not, either
someone can set up a wiki or I'll just pop a Wikispace and we'll take
it from there.
Further on the horizon, we will want to start dogfooding, e.g. with a
Wordpress plugin, and write a prototype intent harvester and index, à
la http://projects.apache.org/indexes.html (but much friendlier). We
will probably want to have a wiki page to describe subprojects like
these and indicate our individual interest and commitments
specifically to one or the other.
Cheers
Seb:)
On Jul 1, 10:05 am, Marc-Antoine Parent <mapar...@acm.org> wrote:
> Le 2010-07-01 à 09:53, Nancyd a écrit :
>
> > I'm doing it using grails/groovy, with a JPA layer (someone else
> > already wrote the magic; I only have to bend it to my will... not here
> > yet). That's keeping me from figuring out the details of GAE
> > persistence (yay) and it should keep thing somewhat neutral (yay).
>
> Sounds good on both counts.
>
> > Scheduling: well, I don't know about you, but day job + family leaves
> > me only a little bit of time, often in 10 minutes here and 30 minutes
> > there increments, so it may be difficult to find a a good time (unless
> > you're all up at 5:30 or 6:00. AM.
>
> I could be...
>
> > RDF: what I've found so far is that "it's just XML" so that's not too
> > bad; still, if you have specific reading suggestions, I'll take them
> > (it's never "just XML" :)
>
> Very true. I guess you've read the primers? They were good enough to get me started. But I sense you may already be past that stage.
>
Marc-Antoine Parent
> for that. Does anybody know if there a wiki out there that is
> dedicated to this kind of hashing out of specs? If not, either
> someone can set up a wiki or I'll just pop a Wikispace and we'll take
> it from there.
Actually, google sites is not halfway bad for project design. It would be easy to register a google apps standard site for intentmap.org. Also gives us our own documents, mail, etc.
Just a suggestion.
Marc-Antoine
Sebastien Paquet
> Actually, google sites is not halfway bad for project design. It would be easy to register a google apps standard site for intentmap.org. Also gives us our own documents, mail, etc.
Let's go with that then! Can you register it?
Seb
maparent
I've created a google apps site, and given admin privileges to
everyone here. I've used your gmail handles to create accounts for
you.
I've created a subsite for specs discussions, using the google project
template, which we will have to seriously clean up.
Cheers,
Marc-Antoine
On 2 juil, 11:19, Sebastien Paquet <sebpaq...@gmail.com> wrote: