The meshup combines and
integrates social software and the content that gets
generated. The social software applications and the content
from the participants form the Open Community Information Commons
meshup. Meshup=many pieces loosely
joined.
Guiding
Principles:
-
Seeds before trees
-
Build from what exists
-
Build along the path
|
|
The conference will use a variety of identifiers
for authentication, accountability, privacy controlled data
exchange. |
|
|
|
|
- A
conference attendee will be able to use an identifier that they are
already have to log into the conference mesh up.
|
|
- A
conference attendee will be able to get an identifier to use at the
conference.
|
|
|
|
|
- A
minimum of just a password.
|
|
The Conference Toolkit will let attendees
experiment with a number of different identity resources. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Authentication, authorization and access control
is a core identity services. We want to demonstrate a number
of different approaches.
We are planning to use Yadis for
this. |
|
|
|
|
- Using an
existing or a new identifier the attendee will have their log in
authenticated.
|
|
|
|
|
- An
authentication resource that permits a number of identifiers to be
accepted.
|
|
- The way
that personal information can be stored and shared. This is a
major component of the Higgins Framework.
|
|
We will create and host wiki pages for each
participant, track and session. |
|
|
|
|
-
Conference attendee will be able to access wiki pages for each
participant as well as each topic.
- The
topics are derived from the tracks and the sessions.
|
|
-
Attendees will be able to create a topic page that can be shared
with the other participants.
|
|
|
|
|
|
|
|
|
|
|
For each session, within each track, we will
publish a Session Map. The maps are created prior to the
conference and contain links to the participants conference pages
and to content related to the session topics. Here is an
example:
|
|
|
|
|
- For each
session within the four tracks, we will create a session
map.
- The maps
will identify the participants and contain resources related to the
session topic.
-
Attendees will have access to the session maps from the Wiki topic
page.
- The maps
can be used for note taking at each session.
|
|
|
|
|
-
Mindmanager is a great tool to create and publish the maps.
- It is
not interactive.
- It is
proprietary.
|
|
|
|
|
|
|
|
-
Attendees will be able to access podcasts of the sessions that take
place.
- They
will be able to listen to sessions they missed or relisten to
sessions they attended.
- They
will be able to link to the podcasts from the topic Wiki
pages.
|
|
|
|
|
|
|
|
|
|
|
Each conference attendee will have a Blog
application they can use of they can publish the existing Blog feed
into the conference mesh-up. Participants can post and comment on
posts. Pick a tag for the conference now and broadcast. |
|
|
|
|
- Each
attendee can choose to blog about the conference.
- We can
give them a conference specific blog or they can point to their
existing blog.
|
|
|
|
|
|
|
|
For each track and for open space we will create
a discussion forum. Participants can create a topic that others can
reply to. |
|
|
|
|
-
Attendees can offer feedback on conference and session topics.
-
Attendees can start threads and reply to others threads.
- These
forums ought to be accessible from the topic pages.
|
|
|
|
|
|
|
|
|
|
|
One possibility is that the participants can
create a decision network. |
|
|
|
|
-
Attendees will be able to participate in collective decision
making.
-
Attendees can propose and/or vote on issues relevant to the
group,
- For
example, attendees can vote on session topics for day three.
|
|
|
|
|
|
|
|
We will create a conference tag and a tag cloud
for sharing links and images. We want to connect my radar and
your radar.
We should pick some good tags around topics and
issues |
|
|
|
|
-
Attendees will be invited to tag content that they deem relevant to
the conference topics.
- We will
come up with a set of tags and definitions that will act as a
starting point.
-
Attendees ought to access a tag cloud from their My Conference
Page.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Collective visualization and display. We will
create "affinity groups" so people can find each other during
meals, before and after sessions.
Attendr - find the guys
Also Ken Jordan is going to be pulling together a
Drupal thing for |
|
|
|
|
- Each
attendee will be able to create Private and Public profiles.
-
Attendees Public Profiles will be made available to other
attendees.
|
|
- Social
networking software will help attendees visualize the network and
answer questions such as: who's here? who has shared
interests? who is open to meeting?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Books We
Like
Browser
Button |
|
|
|
|
-
Attendees will be offered the opportunity to make purchases that
are recommended by other attendees or benefit social causes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We can create "conference rooms" that
participants can join.
You should think about using a web based tool so
that those who are IRC illiterate can play (they can also sign in
with their handle for the conference)
ALSO there should be an onsite techie desk to get
these new fandangeld things going for newbies |
|
|
|
|
-
Attendees can chat with other attendees during the
conference. This is the "back channel" that is now part of
the face to face conference experience.
|
|
|
|
|
|
|
|
The conference WiFi site can be a "placesite"
that participants connect to.
Does it have a way to do ambient IM |
|
|
|
|
-
Attendees will be able to discover information about the other
attendees when they log into the wiki network.
|
|
|
|
|
|
|
|
|
|
|
1. Conference Creators
