Re: design consideratins for a simple (semantic) contact management app

If P2P rather than client server would make it, then most of the 
requirements you can solve with DBin [1] today and no programming. Plus 
you get other things for free like digital signatures, handling of data 
attachments, multiplatform, Ecllipse based plugin model etc

Just add your favorite ontologies and mash together a UI with a bit of 
XML to create your domain  "Brainlet" [2].
To create such thing big suggestion is download the lastest DBin and 
modify one of the brainlets we ship.
Still not the earlist thing in the world to create but.. we're here to 
help! :-) (and working hard to make this process as simple as possible).

Giovanni

[1] http://dbin.org  
[2] Brainlets: "instant" Semantic Web applications
Giovanni Tummarello, Christian Morbidoni, Michele Nucci, Onofrio 
Panzarino http://www.semanticscripting.org/SFSW2006/Paper5.pdf

Eric Hoffer wrote:
> I too am looking to do something similar, so if there have been 
> private responses that you could share, that would be of interest to 
> me as well - though we are looking for something that is scalable, so 
> performance would matter.
>
> From an architectural standpoint, in the context of an integrated 
> system which incorporates social networking aspects as well as 
> collaborative workspaces, in addition to the questions posed by Aldo, 
> I would also like to get some guidance on the best approaches for its 
> semantic enablement - i.e. whether at this stage it should be 
> intrinsically semantic, or enabled via semantic layer.
>
> Thanks in advance for your thoughts.
> Eric
>
> */Aldo Bucchi <aldo.bucchi@gmail.com>/* wrote:
>
>
>     hi all,
>
>     as a simple excercise i would like to build a simple contact
>     management app ( domain: generic business... contacts, accounts,
>     employees, relations, etc ) as follows.
>
>     *a central server with a triple store
>     ** inference engine
>     ** contexts / named graphs
>     *several user accounts
>     *a user interface that allows users to
>     ** create / delete statements
>     *** contexts are used to keep track of provenance of statements
>     ** sparql and simple browsing
>     *an ontology ( plus inference layer ) that allows me to, at least:
>     ** use or define some common inverse functional properties ( ssn /
>     email / internal id / phone extension ) and perform smushing.
>     ** define basic contact info plus some relationships ( hierarchy,
>     relation to an organization, etc. transitivity would be nice in
>     hierarchical relationships )
>
>     what storage / inference stack would you use?
>     any recommended ontologies?
>     design considerations / ideas?
>     dev workflow?
>
>     doesn't need to be performant at all. we're talking very small
>     numbers here.
>
>     thx ;)
>     aldo
>
>     -- 
>     ::::: Aldo Bucchi :::::
>     mobile (56) 8 429 8300
>
>
>
>
> Eric Hoffer
> 973.494.1073
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Next-gen email? Have it all with the all-new Yahoo! Mail Beta. 
> <http://us.rd.yahoo.com/evt=40788/*http://advision.webevents.yahoo.com/handraisers>

Received on Wednesday, 19 July 2006 18:40:23 UTC