[doap-interest] doap:user?

On 12/19/06, Benjamin Nowack wrote:

> any chance I could talk you into adding a "user" property
> to DOAP? I'm building an RDFy social networking system
> where members will be able to list the tools they are using
> (for community building bla). As the software descriptions
> are DOAP-based, it would be great to have such a property
> in the core vocab as well, e.g.
>
> [[
>
>
> user
> User of the software of the
> project.

>
>
>

> ]]

We discussed a similar idea on #sioc IRC channel. I would suggest to
start with the other direction for this relation first - software
which a foaf:Person is using.

A DOAP profile can't possibly list all users of a software tool or
keep it up-to-date but if information on software used by people is
attached to their FOAF profiles you can always aggregate them and
discover who is using what.

That'd be good use case - to see what tools your friends are using.

As an experiment in this direction Christoph Gorn added a new property
to his FOAF-X vocabulary which would allow to describe this relation
(what software is somebody using). He also added an example
description to his FOAF profile (one this I remember is that he's
using VIM :), but I don't see it now.

Christoph, could you tell a bit more about it?

Best,
Uldis

[ http://captsolo.net/info/ ]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[doap-interest] doap:user?

Hey all,
I did something similar as Benjamin is trying to do. I blogged
about at several posts. [1], [2] My main intention was to say "please
contact me via this media" Which is in general a attribution of a
OnlineAccount. The same method may be used to attribute a doap
software packages. There have been discussions why subclassing is not
so good as "attribution", which is a general design decision.

Hope that helps, Christoph

[1] http://b4mad.net/datenbrei/archives/2005/10/18/expressing-my-
preferred-method-of-contact-initiation/
[2] http://b4mad.net/datenbrei/archives/2006/08/01/declarative-living-
indicating-the-preferred-contact-channel/

> ---------- Forwarded message ----------
> From: Uldis Bojars
> Date: Dec 20, 2006 12:22 AM
> Subject: Re: [doap-interest] doap:user?
> To: Benjamin Nowack
> Cc: doap-interest@lists.gnomehack.com, SIOC-Dev > dev@googlegroups.com>
>
>
> On 12/19/06, Benjamin Nowack wrote:
>
>> any chance I could talk you into adding a "user" property
>> to DOAP? I'm building an RDFy social networking system
>> where members will be able to list the tools they are using
>> (for community building bla). As the software descriptions
>> are DOAP-based, it would be great to have such a property
>> in the core vocab as well, e.g.
>>
>> [[
>>
>>
>> user
>> User of the software of the
>> project.

>>
>>
>>

>> ]]
>
> We discussed a similar idea on #sioc IRC channel. I would suggest to
> start with the other direction for this relation first - software
> which a foaf:Person is using.
>
> A DOAP profile can't possibly list all users of a software tool or
> keep it up-to-date but if information on software used by people is
> attached to their FOAF profiles you can always aggregate them and
> discover who is using what.
>
> That'd be good use case - to see what tools your friends are using.
>
> As an experiment in this direction Christoph Gorn added a new property
> to his FOAF-X vocabulary which would allow to describe this relation
> (what software is somebody using). He also added an example
> description to his FOAF profile (one this I remember is that he's
> using VIM :), but I don't see it now.
>
> Christoph, could you tell a bit more about it?
>
> Best,
> Uldis
>
> [ http://captsolo.net/info/ ]
>

--
Christoph Görn
http://B4mad.Net/FOAF/goern.rdf#goern

Usability schmusability... where's the part where we talk about how
this helps users kick ass?

[doap-interest] doap:user?

On 12/20/06, Benjamin Nowack wrote:
> On 20.12.2006 00:22:22, Uldis Bojars wrote:
> >We discussed a similar idea on #sioc IRC channel. I would suggest to
> >start with the other direction for this relation first - software
> >which a foaf:Person is using.

> See [1], the direction generally doesn't matter. With a DOAP-related
> prop however, it may actually matter, but should be from the project
> to the user: DOAP does a neat trick and integrates both projects

Direction does not matter for properties that are inverse of one another.

The case of "the software a person uses" is different - you may be
using software that does not have a DOAP profile yet. You could use a
FOAF property that points to a URI (e.g., a DOAP profile) or to a web
page of this software project.

If all you want to describe is "John is using OmniGraffle" then John
creating a DOAP profile for OmniGraffly may be an unwelcome overhead.
And he may not know all the information about a project. Pointing to a
web page (or a DOAP profile) is as simple as it gets.

Your use case is DOAP specific and would benefit from addition of this
property to DOAP. Main thing I want to say is that the scope of these
properties is different, they are not exact inverse of one another and
we would benefit from both of them.

Note: A property "FOAF -> DOAP" is what I had in mind when writing the
initial response. Then your comment of one direction being sufficient
would hold true. After thinking about it a bit more I came to an
understanding that by restricting this property to DOAP we'd be
limiting ourselves and therefore broadened the scope of this property.

Happy New Year !!! :)

Uldis

[ http://captsolo.net/info/ ]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---