Knowledge sharing developers

After Boston and the introduction of Long term Drupal, the semantic web has been getting a lot of attention. Kristof suggest expert meeting for semantic web in a recent post. I like the idea much, although I would not restricted it to semantic web (but as every one will be interested in it, it will be the focal point any way). I think a list of short goals (Drupal7 or Drupal8) versus long term goals are needed. The long term goals will require more than two years and experiments may get organized more collaborative than has been the case in the past.

Currently I'm taking up contact with the FP7 contact points to see if we can setup expert meetings. If you check the FP7 site, you'll notice it can fit many of the pillars in general but non in particular. Some creativity will be needed according to the contact point. ... To be continued

At the heart of our mission is developing the state of the art means to share knowledge- particularly bridging the providers of sustainability strategies and solutions to those who can implement on their real estate projects. We would be eager to discuss what may be the most powerful ways to achieve our objectives.

Thanks,
Jeff
www.skysiteproperty.com

It has been a long time since I looked at this group and I belief its about time to give some updates.

First the topic is brought and is starting to split up in several sub-topics:
usage of content types:
Depending on the structure, functions and interface content-type can become "good practices" for specific needs. For example forms to get answer to questions, blogs to state your opinion. In relation with our development with cck and node access we could make more powerful content-types like a private-message, a content type that stimulates user2user interaction. At the moment we see a development to create all kind of new content-types this has litle to do with code-development and all with web/community-service

It's exciting to read about the Social Networking Analysis (SNA) Tool that is 1 of 14 2006 Summer of Code projects selected to write Drupal code with the financial support of Google.

Kudos to Robert Douglass and Angela Byron for all their excellent work in helping put together the 2006 SOC!

The basic SNA module is an analysis tool that will map and analyze how nodes and users are interlinked. It is useful for knowledge management in organizations because it provides an insight on what nodes have greatest value and which users are frequently tapped by other users for knowledge. Since node analysis (eg most popular nodes) is already existent in other modules, we will focus here on an analysis of user networks.

At the moment we have members of a group. But notice its not the only place to have members. Take a project, several people participate in a project and of-course you can have projects in groups, but you can have inter-disciplinary projects as well. The common solution is to create a group for that projects, but this approach is actually reducing the principle of a group. A group are people who have a common thought. I just realized today that you could see contacts a a kind of member too: a member to your identity-space. So it may be interesting to have 'member' feature where you have a type (group, project, user) a user id an a cluster id (where the id depends on the type).

Well all the conceptualisation is interesting, but lets get practical. The first important idea coming out of the sprint is a Drupal way to enhance the 'private/public' idea in the system, the idea creates all kind of implication but I will restrict my post to how it has influenced the way we did create data. There is a strong relation with managing data I leave for the next post. There is also an interesting discussion on the nature of a groupagain it looks better to have it in a separated post.

One of the first things we would like is a private/public where groups can have some private content. At the moment you can write controle acess in several ways. Depening on the module or via the 'db_rewrite_sql' and the access-table. With the node_access we can't realy do what we want and the access-table is way to much of a "wild card" for our purpose. Now we really wanted a nice Drupal way to fix our problem, for one we my want to expand the public/private idea to the whole system (for example not only for groups but also for dyadic/contacts), meaning we should be handling it at the individual node level => node-table. At the moment you can find 2 fields in the node table 'publish' and 'moderation' and the two concepts are kind of ambigue at the moment.