W3C Wiki - User contributions [en]

Webapps/AppCacheUseCases

Charles — Thu, 02 May 2013 14:57:15 GMT

Charles: Jonas' use cases

=== 1. Initial loading - Yandex ===
Our SERP (and Yandex main page www.yandex.ru) uses embedded styles and
scripts for faster loading than with multiple requests for
styles/scripts/...

But users load them every time they visit the results page, because the
browser doesn't cache it. It would be nice on the first visit to extract
the styles and scripts and store them in the cache.

=== 2. Bundles - Yandex ===
Sometimes we need to load several resources (js/css/json/...) before we
can actually show something to user. Like a dialog, or another complex
control. Or if it's a single page application before change "page". Again,
it's often faster to make one request than several, but it would be even
faster if we could then cache them separately:
HttpCache.store(url1, content1);
HttpCache.store(url2, content2);
...
So that later we can use the files as usual (<script>, <link>...).

=== 3. Diffs (delta updates) - Yandex ===
Every static file (js/css/...) has a version, e.g.
http://yandex.st/mail/1.3.8/mail.js
Whan we release a new version our users have to download it. It could be
hundreds of kilobytes (or more). But the difference between versions is
often not very big. So we want to make delta updates.

It would be nice if we could download the diff, apply it in the browser
and store the update in cache e.g.:

var oldVersion = '1.3.8';
var newVersion = '1.3.9';
var oldContent = HttpCache.get(oldUrl);
var newContent = applyPatch(oldContent, patch);
HttpCache.store(newUrl, newContent);

=== 4. Preloading - Yandex ===
Well, we can use normal xhr for that but maybe we can do more with
HttpCache.

Basically we want methods for loading resources, storing them in cache,
fetching them from cache, checking if something is in the cache, ...

=== Community-content site - Alec Flett ===
Logged-out users have content cached aggressively
offline - meaning every page visited should be cached until told otherwise.
Intermediate caches / proxies should be able to cache the latest version of
a URL. As soon as a user logs in, the same urls they just used should now
have editing controls. (note that actual page contents *may* not have not
changed, just the UI) Pages now need to be "fresh" meaning that users
should never edit stale content. In an ideal world, once a logged in user
has edited a page, that page is "pushed" to users or proxies who have
previously cached that page and will likely visit it again soon.

I know this example in particular seems like it could be accomplished with
a series of If-Modified-Since / 304's, but connection latency is the killer
here, especially for mobile - the fact that you have a white screen while
you wait to see if the page has changed. The idea that you could visit a
cached page, (i.e. avoid hitting the network) and then a few seconds later
be told "there is a newer version of this page available" after the fact,
(or even just silently update the page so the next visit delivers a fresh
but network-free page) would be pretty huge. Especially if you could then
proactively fetch a select set of pages - i.e. imagine an in-browser
process that says "for each link on this page, if I have a stale copy of
the url, go fetch it in the background so it is ready in the cache"

===Small simple game - Jonas ===
The game consists of a set of static resources. A few HTML pages, like
high score page, start page, in-game page, etc. A larger number of
media resources. A few "data resources" which contain level metadata.
Small amount of dynamic data being generated, such as progress on each
level, high score, user info.
In-game performance is critical, all resources must be guaranteed to
be available locally once the game starts.
Little need for network connectivity other than to update game
resources whenever an update is available.

=== Advanced game - Jonas ===
Same as simple game, but also downloads additional levels dynamically.
Also wants to store game progress on servers so that it can be synced
across devices.

=== Wikipedia - Jonas ===
Top level page and its resources are made available offline.
Application logic can enable additional pages to be made available
offline. When such a page is made available offline both the page and
any media resources that it uses needs to be cached.
Doesn't need to be updated very aggressively, maybe only upon user request.

=== Twitter - Jonas ===
A set of HTML templates that are used to create a UI for a database of
tweets. The same data is visualized in several different ways, for
example in the user's default tweet stream, in the page for an
individual tweet, and in the conversation thread view.
Downloading the actual tweet contents and metadata shouldn't need to
happen multiple times in order to support the separate views.
The URLs for watching individual tweets needs to be the same whether
the user is using appcache or not so that linking to a tweet always
works.
It is very important that users are upgraded to the latest version of
scripts and templates very quickly after they become available. The
website likely will want to be able to check for updates on demand
rather than relying on implementation logic.
If the user is online but has appcached the website it should be able
to use the cached version. This should be the case even if the user
navigates to a tweet page for a tweet for which the user hasn't yet
cached the tweet content or metadata. In this case only the tweet
content and metadata should need to be downloaded and the cached
templates should be used.
If the user does not have twitter in the appcache and navigates to the
URL for an individual tweet the website needs to be able to send a
page which inlines resources such as CSS and JS files. This is
important in order to avoid additional round trips.

=== Webmail - Jonas ===
A lot of simularities with the twitter use case. The website is
basically a UI for the database of emails.
However its additionally important that the user can compose emails,
including attach attachments, which are saved and synchronized once
the user goes online.
There are also other actions that the user might have taken while
offline. This means that complicated conflict resolution might need to
be done in order to synchronize with changes that has happened on the
server.

=== Blog reading - Jonas ===
Store the last X days of blog posts locally. Each blog post consists
of the blog text as well as a few images. Other websites can link to
individual posts.
Each post contains a list of comments for the post.
Adding comments should be possible even while offline. Once the user
goes online it should be possible to submit these comments.

=== Blog authoring - jonas ===
Same as blog reading, but probably want to cache a larger set of
posts. Repository of unpublished posts should be available for editing
offline. Once the user goes online these edits are synced to server,
and any posts that were published while offline are automatically
published.
Both adding and removing comments should be possible while offline.
These changes too are published once user goes online.

=== News website - Jonas ===
Front page with links to various articles. Each article as well as
front page contains both text and images/media. Both front page and
articles contains ads. A set of "top" articles are automatically
cached and kept up-to-date. Potentially users can configure additional
areas of interest which would cause additional articles from those
areas to get cached.

Webapps/AppCacheUseCases

Charles — Thu, 02 May 2013 14:54:37 GMT

Charles: Added Alec's case

Charles — Wed, 27 Feb 2013 00:06:43 GMT

Charles: friday stop at lunchtime

TPAC2012/Offline Apps

Charles — Thu, 01 Nov 2012 17:04:04 GMT

Charles: package / data formats

== Offline Apps ==

There were 46 participants in the session.

The minutes are at: http://www.w3.org/2012/10/31-offline-minutes.html

Chaals agreed to summarise methods for packaging applications, and working with data. Here's something of a start on that:

Packaging:
* appcache (list of URLs to be collected)
* widgets (XML)
* Mozilla app packaging proposal (JSON)
* Chrome app packaging format (JSON)

Data sources:
* file system
* Web Storage
* WebSQL
* IndexedDB
* local URLs in packages
* Get stuff by XHR

(It is sometimes but not always possible to open links too. But that's kind of separate)

TPAC2012-Planning

Charles — Sat, 08 Sep 2012 16:17:17 GMT

Charles: /* Notes on the agenda (especially wrt TPAC 2011) */

It is expected that the [[TPAC2012-Committee|TPAC2012 Program Committee]] will use this wiki to plan the [[TPAC2012]] Plenary day.

== Next meeting of Program Committee ==

Next meeting: Friday, 14 Sep at 11am ET.

Agenda ideas for that meeting:

* Resolve to adopt proposed schedule
* Plan to update resources (FAQ, agenda, good practices for session chairs
* Next steps on 1-1 outreach plan for Prog Committee to encourage sessions

== Ideas for TPAC 2012 Agenda ==

=== Ian proposal based on TPAC 2011 Feedback ===

==== Before the Plenary ====

<ul class="show_items">
* June: Invite people to start thinking of breakout sessions ([https://lists.w3.org/Archives/Member/w3c-ac-members/2012AprJun/0066.html email to TPAC attendees]).
* August: Send ([https://lists.w3.org/Archives/Member/w3c-ac-members/2012JulSep/0030.html reminder])
* 17 September: Update TPAC 2012 pages to reflect program committee plans.
* 18 September: Share plenary plan with meeting attendees with third invitation to propose sessions. Explain briefly pre-select process and any process to upgrade to plenary. Point to updated documentation/FAQ. Invite people (using w3c-ac-forum and wiki) to request sessions they'd like to hear about.
* 19 September to 10 October: Program committee 1-on-1 outreach to potential session leads.
** @@More work to do on how the 1-1 outreach will happen
* 19 October: Announce pre-selected breakout sessions and last push for session entries. Also announce that there will be a brief explanation of how the day works 30 minutes before the 30 Oct reception starts.
* 29 October: Make available grid near registration so people see sessions and can start putting their own on Monday and Tuesday
* 30 October: Dress rehearsal (to see that we have all we need). Before the reception show people how it works. (This was great during TPAC 2011 at the bar with the Japanese participants.)
* 31 October: Plenary
</ul>

Notes:
<ul class="show_items">
* Jeff: More outreach to CGs to propose breakout sessions.
</ul>

==== Day of the Plenary (31 October)====

* 08:30-09:00: Jeff Jaffe intro in plenary
* 09:00-09:30: New and upcoming work (wgs, cgs, bgs, workshops). Plenary lightning talks (can mention related breakouts)
* 09:30-10:30: Agenda building.
** Includes Tantek and Ian brief intro 5-10 mins on how the day will go
* 10:30-11:00: Break
* 11:00-11:50: Discussion breakouts
* 12:00-13:30: Lunch
* 13:30-14:50: Discussion breakouts
* 15:00-15:30: Break
* 15:30-15:55: Presentation breakouts [May be combined for 2 hours]
* 16:00-16:50: Presentation breakouts
* 17:00-17:30: Sharing (optional)
* 17:30-17:40: Wrap-up, thanks, next TPAC (Jeff Jaffe)
* 18h30-end: Dinner

Notes:

<ul class="show_items">
* Jeff not convinced of variable time slots. People may not know in advance what they need. Complicates agenda building.
</ul>

==== After the Plenary ====

* Comm Team reviews all the session summaries and builds a comprehensive summary to emphasize integration of the sessions into our broader work plan.

==== Notes on the agenda (especially wrt TPAC 2011) ====

<ul class="show_items">
* Schedule makes explicit travel time between sessions (a comment from TPAC 2011).
* Only two plenary sessions. (TPAC 2011 had three.) Jeff's was appreciated (and is repeated). The other is 30 minutes and will be LTs so people can share info about new work as broadly as possible.
* More discussion time. TPAC 2011 had 3:45. TPAC 2012 has 4:30.
* Scheduled breaks (suggested based on TPAC 2011).
* Different slot lengths for different needs; clearer labeling of slot purpose.
* Sharing session reduced from TPAC 2011's 75 minutes to 30 minutes. There are various ways to share (per Jeff):
** Sharing session (determine number and max allocation at beginning of session)
** At Thursday AC meeting as appropriate
** In a new CG
** Electronically (e.g., recording in wiki, then sharing on mailing lists)
* We have rooms for 28 breakouts.
* There are no pre-selected plenaries. We can, however, choose to guarantee up to 25% of the slots (thus, 7) for those people who request a guaranteed slot (by some date) and who commit to organizing it.
</ul>

See [[TPAC2012#Some_ideas_for_changes_from_TPAC_2011]]

== Room logistics ==

Notes: the plenary is on Forum level, all the TPAC meeting rooms are on the right side on the conference center

<ul class="show_items">
* The plenary room (Weds) will set 156 classroom style and 234 theater style. Classroom style has electricity.
* Rhone 1: 35 people
* Rhone 2: 35 people
* Rhone 3A (combined with 3B): 55 people
* Saint-Clair 1: 20 people
* Saint-Clair 2: 20 people
* Saint-Clair 3A: 20 people
* Saint-Clair 3B: 20 people
* Extra cost: 5 rooms for 15 people (Levels Saint-Clair and Roseraie).
</ul>

Travel times:

<ul class="show_items">
* From plenary to breakouts: 2-4 mins walk
* From breakouts to lunch: 2-4 mins walk (next to plenary room)
</ul>

Notes:
* The plenary is on Forum level, all the TPAC meeting rooms are on the right side on the conference center
* We can hold the breaks next to the breakout rooms, or in front on the Plenary room.

See also [http://www.ccc-lyon.com/uploads/sfSympalBossMediaPlugin/document/7f3fd1786a7211bd86b342eb966afc035a4c5d08.pdf map of the space (PDF)].

== Good practice for session chairs ==

<ul class="show_items">
* When you start
** Announce the nature of your session (presentation or discussion or other)
** Define goals for your session (so people can choose to attend).
** Provide context so that people who are new to the topic can follow.
** Find a scribe who will take notes in the wiki.
** Choose an IRC channel (and invite bots for creating minutes)
** Consider recording names of participants (e.g., by having them "sign in" on IRC)
* At the end
** End '''on time'''
** Try to summarize before the end of the meeting, for inclusion in the wiki and possibly for sharing in plenary:
*** What are the next steps (possibly none)?
*** Who is responsible for carrying them out? (Could be a person from the session, or a group where work is ongoing, or the staff, etc.)
</ul>

== Material requirements ==

<ul class="show_items">
* Place to draw the grid
* Paper stickies and fat markers
</ul>

TPAC2012-Planning

Charles — Sat, 08 Sep 2012 16:16:51 GMT

Charles: /* Good practice for session chairs */ timing

It is expected that the [[TPAC2012-Committee|TPAC2012 Program Committee]] will use this wiki to plan the [[TPAC2012]] Plenary day.

== Next meeting of Program Committee ==

Next meeting: Friday, 14 Sep at 11am ET.

Agenda ideas for that meeting:

* Resolve to adopt proposed schedule
* Plan to update resources (FAQ, agenda, good practices for session chairs
* Next steps on 1-1 outreach plan for Prog Committee to encourage sessions

== Ideas for TPAC 2012 Agenda ==

=== Ian proposal based on TPAC 2011 Feedback ===

==== Before the Plenary ====

<ul class="show_items">
* June: Invite people to start thinking of breakout sessions ([https://lists.w3.org/Archives/Member/w3c-ac-members/2012AprJun/0066.html email to TPAC attendees]).
* August: Send ([https://lists.w3.org/Archives/Member/w3c-ac-members/2012JulSep/0030.html reminder])
* 17 September: Update TPAC 2012 pages to reflect program committee plans.
* 18 September: Share plenary plan with meeting attendees with third invitation to propose sessions. Explain briefly pre-select process and any process to upgrade to plenary. Point to updated documentation/FAQ. Invite people (using w3c-ac-forum and wiki) to request sessions they'd like to hear about.
* 19 September to 10 October: Program committee 1-on-1 outreach to potential session leads.
** @@More work to do on how the 1-1 outreach will happen
* 19 October: Announce pre-selected breakout sessions and last push for session entries. Also announce that there will be a brief explanation of how the day works 30 minutes before the 30 Oct reception starts.
* 29 October: Make available grid near registration so people see sessions and can start putting their own on Monday and Tuesday
* 30 October: Dress rehearsal (to see that we have all we need). Before the reception show people how it works. (This was great during TPAC 2011 at the bar with the Japanese participants.)
* 31 October: Plenary
</ul>

Notes:
<ul class="show_items">
* Jeff: More outreach to CGs to propose breakout sessions.
</ul>

==== Day of the Plenary (31 October)====

* 08:30-09:00: Jeff Jaffe intro in plenary
* 09:00-09:30: New and upcoming work (wgs, cgs, bgs, workshops). Plenary lightning talks (can mention related breakouts)
* 09:30-10:30: Agenda building.
** Includes Tantek and Ian brief intro 5-10 mins on how the day will go
* 10:30-11:00: Break
* 11:00-11:50: Discussion breakouts
* 12:00-13:30: Lunch
* 13:30-14:50: Discussion breakouts
* 15:00-15:30: Break
* 15:30-15:55: Presentation breakouts [May be combined for 2 hours]
* 16:00-16:50: Presentation breakouts
* 17:00-17:30: Sharing (optional)
* 17:30-17:40: Wrap-up, thanks, next TPAC (Jeff Jaffe)
* 18h30-end: Dinner

Notes:

<ul class="show_items">
* Jeff not convinced of variable time slots. People may not know in advance what they need. Complicates agenda building.
</ul>

==== After the Plenary ====

* Comm Team reviews all the session summaries and builds a comprehensive summary to emphasize integration of the sessions into our broader work plan.

==== Notes on the agenda (especially wrt TPAC 2011) ====

<ul class="show_items">
* Schedule makes explicit travel time between sessions (a comment from TPAC 2011).
* Only two plenary sessions. (TPAC 2011 had three.) Jeff's was appreciated (and is repeated). The other is 30 minutes and will be LTs so people can share info about new work as broadly as possible.
* More discussion time. TPAC 2011 had 3:45. TPAC 2012 has 4:30.
* Scheduled breaks (suggested based on TPAC 2011).
* Different slot lengths for different needs; clearer labeling of slot purpose.
* Sharing session reduced from TPAC 2011's 75 minutes to 30 minutes. There are various ways to share (per Jeff):
** Sharing session (determine number and max allocation at beginning of session)
** At Thursday AC meeting as appropriate
** In a new CG
** Electronically (e.g., recording in wiki, then sharing on mailing lists)
* We have rooms for 28 breakouts.
* There are no pre-selected plenaries. We can, however, choose to guarantee 25% of the slots (thus, 7) for those people who request a guaranteed slot (by some date) and who commit to organizing it.
</ul>

See [[TPAC2012#Some_ideas_for_changes_from_TPAC_2011]]

== Room logistics ==

Notes: the plenary is on Forum level, all the TPAC meeting rooms are on the right side on the conference center

<ul class="show_items">
* The plenary room (Weds) will set 156 classroom style and 234 theater style. Classroom style has electricity.
* Rhone 1: 35 people
* Rhone 2: 35 people
* Rhone 3A (combined with 3B): 55 people
* Saint-Clair 1: 20 people
* Saint-Clair 2: 20 people
* Saint-Clair 3A: 20 people
* Saint-Clair 3B: 20 people
* Extra cost: 5 rooms for 15 people (Levels Saint-Clair and Roseraie).
</ul>

Travel times:

<ul class="show_items">
* From plenary to breakouts: 2-4 mins walk
* From breakouts to lunch: 2-4 mins walk (next to plenary room)
</ul>

Notes:
* The plenary is on Forum level, all the TPAC meeting rooms are on the right side on the conference center
* We can hold the breaks next to the breakout rooms, or in front on the Plenary room.

See also [http://www.ccc-lyon.com/uploads/sfSympalBossMediaPlugin/document/7f3fd1786a7211bd86b342eb966afc035a4c5d08.pdf map of the space (PDF)].

== Good practice for session chairs ==

<ul class="show_items">
* When you start
** Announce the nature of your session (presentation or discussion or other)
** Define goals for your session (so people can choose to attend).
** Provide context so that people who are new to the topic can follow.
** Find a scribe who will take notes in the wiki.
** Choose an IRC channel (and invite bots for creating minutes)
** Consider recording names of participants (e.g., by having them "sign in" on IRC)
* At the end
** End '''on time'''
** Try to summarize before the end of the meeting, for inclusion in the wiki and possibly for sharing in plenary:
*** What are the next steps (possibly none)?
*** Who is responsible for carrying them out? (Could be a person from the session, or a group where work is ongoing, or the staff, etc.)
</ul>

== Material requirements ==

<ul class="show_items">
* Place to draw the grid
* Paper stickies and fat markers
</ul>

Webapps/TPAC2012Meeting

Charles — Wed, 29 Aug 2012 10:48:45 GMT

Charles: /* Potential Topics */

This is the Meeting Page including Agenda for the Web Applications WG (WebApps) f2f meeting in Lyon France on Monday October 29 and Tuesday October 30 2012. This meeting is being held in conjunction with the W3C's annual [http://www.w3.org/2012/10/TPAC/ 2012 Technical Plenary] meeting week (aka simply ''TPAC'').

'''This Meeting Page, in particular the Agenda, is a WorkInProgress and Will Change!'''

== Meeting Logistics ==

* Meeting Host = W3C (as part of the [http://www.w3.org/2012/10/TPAC/ TPAC 2012 Meeting Week])
* Voice Conference: bridge will be available; PIN = @TBD
* IRC channel = #webapps; irc.w3.org:6665
* Dates = Monday and Tuesday October 29-30 2012
* Time = See below; all times are local time zone
* Location = Lyon France
* Meeting Room = @TBD

== Meeting Registration ==

'''Pre-registration for this meeting is Mandatory''' via the [http://www.w3.org/2012/10/TPAC/#Registration TPAC 2012 Meeting Registration] service.

For a list of registrants see [https://www.w3.org/2002/09/wbs/35125/TPAC2012/registrants#Webap WebApps' registrant list] (Member-only link).

== Specifications, Documents and References ==

* [http://www.w3.org/2008/webapps/wiki/PubStatus#API_Specifications Specification List including Publication Status]
* [http://www.w3.org/2008/webapps/wiki/WorkMode Group's Work Mode]
* [http://www.w3.org/2008/webapps/wiki/WorkMode#CVS_and_Mercurial CVS and Mercurial repositories]
* [http://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG Bugzilla]
* [http://www.w3.org/2008/webapps/track/products Tracker]

== Potential Topics ==

Potential agenda topics, listed in alphabetical order. '''Note that none of these topics are confirmed, please feel free to add suggestions/requests.'''

* [http://dvcs.w3.org/hg/web-intents/raw-file/tip/spec/Overview.html Web Intents] spec. DAP WG is meeting on Thur/Fri and will discuss the spec in detail, the purpose of discussion in webapps is to raise issues and feed the DAP meeting. Suggested 30-60 minutes.

* Joint Meetings
** Joint Meeting with CSS WG re [http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html Fullscreen] spec?
** Joint Meeting with WebAppSec WG re [http://dev.w3.org/2006/waf/access-control/ CORS] spec?

== Agenda Monday October 29 ==

* 09:00 - 09:30 Rearranging the room
* 09:30 - 10:00 Tweak agenda à la an [http://en.wikipedia.org/wiki/Unconference unconference style meeting]
* 10:00 - 11:00
* 11:00 - 11:30 Break
* 11:30 - 12:30
* 12:30 - 13:30 Lunch
* 13:30 - 14:30
* 14:30 - 15:30
* 15:30 - 15:45 Break
* 15:45 - 16:45
* 16:45 - 17:45

== Agenda Tuesday October 30 ==

* 09:00 - 09:30 Tweak agenda à la an [http://en.wikipedia.org/wiki/Unconference unconference style meeting]
* 09:30 - 10:30
* 10:30 - 11:00 Break
* 11:00 - 11:45
* 11:45 - 12:30
* 12:30 - 13:30 Lunch
* 13:30 - 14:30
* 14:30 - 15:30
* 15:30 - 15:45 Break
* 15:45 - 17:45 Web Intents: update, status, Q&A with Web Intents Task Force members

== Minutes ==

* [@TBD October 29]
* [@TBD October 30]

GuideBook

Charles — Tue, 14 Aug 2012 16:18:23 GMT

Charles: /* Facet 1: Timeline */ tweaking

__NOTOC__
This is a ''proposal'' for a reorganization of the [http://www.w3.org/Guide/ Art of Consensus Guide] into different faceted documents

== About the Guide ==

This Guidebook is intended to complement the [http://www.w3.org/Consortium/Agreement/Appendix W3C Membership Agreement] and the [http://www.w3.org/Consortium/Process/ W3C Process]. This index page is ''Member-only'', although some of the resources in the Guidebook are public.

You are expected to be familiar with the parts of this Guidebook that affect your work. Working Group chairs should get a "tour" from their team contact. Then take a look again, for example, if you're going to hold a face-to-face meeting; read the section on meetings.

== Facet 1: Timeline ==

=== Create a Group ===

* [http://www.w3.org/2000/09/submission how to send a Member Submission Request] which may prompt the creation of a group
* New group [http://www.w3.org/Guide/Charter.html charter] [http://www.w3.org/2006/02/chartergen generator]
* Alternatively, create a [http://www.w3.org/community community or business group]

=== Setting up systems tools ===

* Your group will already have a mailing list. If you think you should have more lists, @@
* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* set up collaborative tools: [http://www.w3.org/Guide/blog blog], [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki]
* start issues tracking with [http://www.w3.org/2005/06/tracker/ tracker] or [http://www.w3.org/Bugs/ bugzilla]
* set up [http://www.w3.org/2005/06/tracker/ tracker] for issue and action items management

=== Using systems tools ===
* run a meeting on IRC
** [http://dev.w3.org/2002/scribe/scribedoc.htm#Quick_Start_Guide Quick start guide] for setting up tools for managing an agenda, generating minutes, and updating issues lists
** [http://www.w3.org/2008/04/scribe.html Scribe 101]: Taking meeting minutes using W3C IRC tools
** Individual IRC tools ("bots"):
*** [http://www.w3.org/2001/12/zakim-irc-bot.html Zakim] for bridge management
*** [http://www.w3.org/2002/03/RRSAgent RRSAgent] for minutes management
*** [http://www.w3.org/2005/06/tracker/irc Trackbot] for issue management (using [http://www.w3.org/2005/06/tracker/ Tracker]) during an IRC-based meeting
* Face-to-face meetings
** Send face-to-face meeting information to calreq@w3.org; that information appears on the [http://www.w3.org/Member/Eventscal Member events calendar]
** [http://www.w3.org/Guide/hosting.htm Host a face-to-face meeting]. Note the [http://www.w3.org/2004/06/NoNDAPolicy.html Policy Regarding Non-Disclosure Agreements and W3C Meetings]
* find editors
* the staff contact gets editors an [http://www.w3.org/Systems/Accounts/w3t/ account (jigedit or CVS)] to edit the w3.org website
* editors can work with
** [http://www.w3.org/Guide/Jigedit JigEdit],
** [http://www.w3.org/Guide/Jigedit/Webdav WebDAV],
** or (for experts) [http://www.w3.org/Project/CVSdoc/ CVS]
* start testing. get dev.w3.org accounts for participants to work on a test suite

=== Maturing Group ===
* how to handle REC track transitions: [http://www.w3.org/Guide/transitions Transition requirements] (for First Public Draft, Last Call, CR, PR, REC, etc.)
* promoting the spec with a [http://www.w3.org/Guide/blog blog], [http://www.w3.org/2004/09/SubmitTalk Talks]
* [http://www.w3.org/2004/12/testimonial_pr-guidelines.htmlPress release testimonial guidelines]
* use the [http://www.w3.org/2006/02/lc-comments-tracker/ Last Call comments tracker] to track public comments on specifications and build a disposition of comments
* if you used [http://www.w3.org/Bugs/ Bugzilla] for issues tracking, [http://www.w3.org/2007/02/bugs2html/ bugs2html] can let you create a disposition of comments
* implementation report

=== Maintenance mode ===
* Publishing Errata, resolving to publish a new edition or a new version.

=== Closing a group ===
* [http://www.w3.org/2005/Incubator/XGR/about.html Publishing a final XG Report]

== Facet 2: by Role ==

=== About W3C Roles ===

* [http://www.w3.org/Guide/chair-roles.html Chair's role]
* [http://lists.w3.org/Archives/Member/chairs/1999JanMar/0056 Editor's role]
* [http://www.w3.org/Signature/Contributor.html Editor, Author, Contributor Policies]
* [http://www.w3.org/Guide/staff-contact.html Staff Contact's role]
* [http://www.w3.org/Guide/liaison-role Liaison's role] ('''Note''': Per [http://www.w3.org/2005/10/Process-20051014/liaisons section 10 of the Process Document], liaisons MUST be coordinated by the Team due to requirements for public communication; patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.)

=== Every WG Participant ===
* [http://www.w3.org/2004/01/pp-impl/ Join a group] (see also [http://www.w3.org/2004/08/invexp.html Invited Expert Policy])
* consider taking on roles: editor, test lead, etc.

=== Chair and Scribe ===

* Guidance: [http://www.w3.org/Guide/reagles-experiences.html On Chairing a group]
* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* organising a Face-to-face meetings
** Send face-to-face meeting information to calreq@w3.org; that information appears on the [http://www.w3.org/Member/Eventscal Member events calendar]
** [http://www.w3.org/Guide/hosting.htm Host a face-to-face meeting]. Note the [http://www.w3.org/2004/06/NoNDAPolicy.html Policy Regarding Non-Disclosure Agreements and W3C Meetings]
* [http://dev.w3.org/2002/scribe/scribedoc.htm#Quick_Start_Guide Quick start guide] for setting up tools for managing an agenda, generating minutes, and updating issues lists
* [http://www.w3.org/2008/04/scribe.html Scribe 101]: Taking meeting minutes using W3C IRC tools
* Individual IRC tools ("bots"):
** [http://www.w3.org/2001/12/zakim-irc-bot.html Zakim] for bridge management
** [http://www.w3.org/2002/03/RRSAgent RRSAgent] for minutes management
** [http://www.w3.org/2005/06/tracker/irc Trackbot] for issue management (using [http://www.w3.org/2005/06/tracker/ Tracker]) during an IRC-based meeting
* [http://lists.w3.org/Archives/Member/chairs/2002JanMar/0041 Guidance for Chairs] on Staff participation
* XG Chairs: For an account to let you or select XG participants write to w3.org, please contact Ian Jacobs
* [http://www.w3.org/Guide/transitions Transition requirements] (for First Public Draft, Last Call, CR, PR, REC, etc.)

=== Staff Contact ===

* work with systems team to set up [http://www.w3.org/Systems/Mail/ListRequest mailing-list], [http://www.w3.org/Guide/blog blog], [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki]
* Get editors an [http://www.w3.org/Systems/Accounts/w3t/ account (jigedit or CVS)] to edit the w3.org website
* [http://www.w3.org/Guide/pubrules Publication Rules] (a.k.a Pubrules) and links to related policies (e.g., [a href="http://www.w3.org/2005/07/13-nsuri namespaces] [http://www.w3.org/2002/06/registering-mediatype MIME type registration], and [http://www.w3.org/2005/05/tr-versions version management])

=== Editor ===

* information about [http://www.w3.org/Project/CVSdoc/ CVS]
* [http://www.w3.org/Guide/pubrules Publication Rules] (a.k.a Pubrules) and links to related policies (e.g., [a href="http://www.w3.org/2005/07/13-nsuri namespaces] [http://www.w3.org/2002/06/registering-mediatype MIME type registration], and [http://www.w3.org/2005/05/tr-versions version management])
* [http://www.w3.org/2003/Editors/ W3C Editors home page]
* Discussion about specifications on [http://lists.w3.org/Archives/Public/spec-prod/ spec-prod@w3.org]
* [http://www.w3.org/2001/06/manual/ W3C Manual of Style]

=== Test lead ===
* information about [http://www.w3.org/Project/CVSdoc/ CVS]

=== Liaison ===

== Facet 3: activities of a group ==

=== Build Consensus ===

* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* learn how to set up an ad-hoc meeting with zakim
* start a mailing-list
* get a [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki] for collaborative editing

=== Develop specification ===

* Know the rules
** [http://www.w3.org/Guide/pubrules Publication Rules] (a.k.a Pubrules) and links to related policies (e.g., [a href="http://www.w3.org/2005/07/13-nsuri namespaces] [http://www.w3.org/2002/06/registering-mediatype MIME type registration], and [http://www.w3.org/2005/05/tr-versions version management])
** [http://www.w3.org/Guide/transitions Transition requirements] (for First Public Draft, Last Call, CR, PR, REC, etc.)
** [http://www.w3.org/2002/05/rec-tips Tips for getting to Recommendation faster]
** [http://www.w3.org/2003/10/UseOfExtTech.html Use of W3C or Other Technologies within W3C Recommendations]
* Get editor(s), write drafts
** [http://www.w3.org/2003/Editors/ W3C Editors home page]
** Discussion about specifications on [http://lists.w3.org/Archives/Public/spec-prod/ spec-prod@w3.org]
** [http://www.w3.org/2001/06/manual/ W3C Manual of Style]
** You can write a spec using the [http://www.w3.org/2002/xmlspec/">W3C XML Specification DTD (XMLspec)], well-supported by Norman Walsh.
* Write better specs: QA resources
** [http://www.w3.org/TR/qaframe-spec/ Specification Guidelines]
** [http://www.w3.org/TR/qa-handbook/ Handbook for QA in groups] and [http://www.w3.org/QA/WG/qaframe-primer QA Framework primer]
** See also "testing" stuff
* Draft review, issue tracking
** get [http://www.w3.org/2005/06/tracker/ Tracker] for issues tracking
** alternatively [http://www.w3.org/Bugs bugzilla] can be used to track issues in a specification
*** … and create a disposition of comments with [http://www.w3.org/2007/02/bugs2html/ bugs2html]
* [http://www.w3.org/2005/06/tracker/irc Trackbot], an IRC-based interface to tracker
** [http://lists.w3.org/Archives/Member/chairs/2007JulSep/0117.html Tips on securing document reviews]

=== Patent Stuff ===
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Commentary: [http://www.w3.org/2003/12/22-pp-faq.html FAQ], [http://www.w3.org/2004/02/05-patentsummary.html Summary] and [http://www.w3.org/2004/03/pp-points-20040210.html Business Benefits]
* [http://www.w3.org/2004/01/pp-impl/ Implementation (IPP)]
* [http://www.w3.org/2004/08/25-chairs-pp.html What's in it for Chairs?]
* [http://www.w3.org/2004/10/27-testcases Policies for Contribution of Test Cases]
* ...more questions? Contact the [http://www.w3.org/2004/pp/psig/ W3C Patents and Standards Interest Group (PSIG)]

=== Test and Implement ===

* [http://www.w3.org/QA/WG/2005/01/test-faq Test Development FAQ]
* [http://dev.w3.org/cvsweb/2007/mobile-test-harness/ Mobile Web Test Harness] Web-based harness for browsers test suites
* test license @@

=== Promote your work ===

* Set up a Working-Group [http://www.w3.org/Guide/blog blog]
* Use the [http://www.w3.org/2004/09/SubmitTalk Upcoming Talks form]; talks publicized on the [http://www.w3.org/ W3C home page], [http://www.w3.org/Member/Newsletter/ Member Newsletter], [http://lists.w3.org/Archives/Public/w3c-announce/Public Weekly News] (approximately 8000 subscribers)
* [http://www.w3.org/2004/12/testimonial_pr-guidelines.htmlPress release testimonial guidelines]
* Give a [http://www.w3.org/2004/01/member-testimonials-hp.html testimonial] about how W3C participation has been beneficial to your organization. ([http://www.w3.org/Consortium/Member/Testimonial/ Current testimonials])
* [http://www.w3.org/Talks/Tools/Slidy/ HTML Slidy] for slide presentations
* [http://www.w3.org/2004/11/accessible-present Notes on Accessible Presentations]

== Facet 4: by Tool ==

=== blog ===
* Set up a Working-Group [http://www.w3.org/Guide/blog blog]

=== mailing-list ===

* [http://www.w3.org/Systems/Mail/ListRequest request the creation of a list]
* manage participants: [http://www.w3.org/Member/Mail/AuditForm Mailing List Audit] (who is subscribed, information about lists), [http://cgi.w3.org/member-bin/list_mgnt.pl List Management Tool], [http://www.w3.org/Guide/RemoteMaintainers SmartList Remote Maintainers Guide]
* No spam: [http://www.w3.org/2002/11/spam-filtering Spam filtering options]
* [http://www.w3.org/Search/Mail/Member Mailing Lists Search service]

=== wiki ===

* get a [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki] for collaborative editing
* manage a wiki

=== tracking tools ===

* [http://www.w3.org/2005/06/tracker/ Tracker] for issues and action items tracking
* [http://www.w3.org/2005/06/tracker/irc Trackbot], an IRC-based interface to tracker
* [http://www.w3.org/Bugs bugzilla] can be used to track issues in a specification, and bugs in software/test suite

=== Polls and Questionaire ===

* [http://www.w3.org/2002/09/wbs/showwb WBS] is a web-based polling and questionaire system

=== IRC ===

* [http://dev.w3.org/2002/scribe/scribedoc.htm#Quick_Start_Guide Quick start guide] for setting up tools for managing an agenda, generating minutes, and updating issues lists
* [http://www.w3.org/2008/04/scribe.html Scribe 101]: Taking meeting minutes using W3C IRC tools
* Individual IRC tools ("bots"):
** [http://www.w3.org/2001/12/zakim-irc-bot.html Zakim] for bridge management
** [http://www.w3.org/2002/03/RRSAgent RRSAgent] for minutes management
** [http://www.w3.org/2005/06/tracker/irc Trackbot] for issue management (using [http://www.w3.org/2005/06/tracker/ Tracker]) during an IRC-based meeting

=== teleconference bridge ===

* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* zakim help

GuideBook

Charles — Tue, 14 Aug 2012 16:15:08 GMT

Charles: s/XG/CG or BG/

__NOTOC__
This is a ''proposal'' for a reorganization of the [http://www.w3.org/Guide/ Art of Consensus Guide] into different faceted documents

== About the Guide ==

This Guidebook is intended to complement the [http://www.w3.org/Consortium/Agreement/Appendix W3C Membership Agreement] and the [http://www.w3.org/Consortium/Process/ W3C Process]. This index page is ''Member-only'', although some of the resources in the Guidebook are public.

You are expected to be familiar with the parts of this Guidebook that affect your work. Working Group chairs should get a "tour" from their team contact. Then take a look again, for example, if you're going to hold a face-to-face meeting; read the section on meetings.

== Facet 1: Timeline ==

=== Create a Group ===

* [http://www.w3.org/2000/09/submission how to send a Member Submission Request] which may prompt the creation of a group
* New group [http://www.w3.org/Guide/Charter.html charter] [http://www.w3.org/2006/02/chartergen generator]
* Alternatively, create a [http://www.w3.org/community community or business group]
* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* set up collaborative tools: [http://www.w3.org/Guide/blog blog], [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki], @@Tracker

=== Early life of a group ===

* start issues tracking with [http://www.w3.org/2005/06/tracker/ tracker] or [http://www.w3.org/Bugs/ bugzilla]
* set up [http://www.w3.org/2005/06/tracker/ tracker] for action items management
* run a meeting on IRC
** [http://dev.w3.org/2002/scribe/scribedoc.htm#Quick_Start_Guide Quick start guide] for setting up tools for managing an agenda, generating minutes, and updating issues lists
** [http://www.w3.org/2008/04/scribe.html Scribe 101]: Taking meeting minutes using W3C IRC tools
** Individual IRC tools ("bots"):
*** [http://www.w3.org/2001/12/zakim-irc-bot.html Zakim] for bridge management
*** [http://www.w3.org/2002/03/RRSAgent RRSAgent] for minutes management
*** [http://www.w3.org/2005/06/tracker/irc Trackbot] for issue management (using [http://www.w3.org/2005/06/tracker/ Tracker]) during an IRC-based meeting
* Face-to-face meetings
** Send face-to-face meeting information to calreq@w3.org; that information appears on the [http://www.w3.org/Member/Eventscal Member events calendar]
** [http://www.w3.org/Guide/hosting.htm Host a face-to-face meeting]. Note the [http://www.w3.org/2004/06/NoNDAPolicy.html Policy Regarding Non-Disclosure Agreements and W3C Meetings]
* find editors
* the staff contact gets editors an [http://www.w3.org/Systems/Accounts/w3t/ account (jigedit or CVS)] to edit the w3.org website
* editors can work with
** [http://www.w3.org/Guide/Jigedit JigEdit],
** [http://www.w3.org/Guide/Jigedit/Webdav WebDAV],
** or (for experts) [http://www.w3.org/Project/CVSdoc/ CVS]
* start testing. get dev.w3.org accounts for participants to work on a test suite

=== Maturing Group ===
* how to handle REC track transitions: [http://www.w3.org/Guide/transitions Transition requirements] (for First Public Draft, Last Call, CR, PR, REC, etc.)
* promoting the spec with a [http://www.w3.org/Guide/blog blog], [http://www.w3.org/2004/09/SubmitTalk Talks]
* [http://www.w3.org/2004/12/testimonial_pr-guidelines.htmlPress release testimonial guidelines]
* use the [http://www.w3.org/2006/02/lc-comments-tracker/ Last Call comments tracker] to track public comments on specifications and build a disposition of comments
* if you used [http://www.w3.org/Bugs/ Bugzilla] for issues tracking, [http://www.w3.org/2007/02/bugs2html/ bugs2html] can let you create a disposition of comments
* implementation report

=== Maintenance mode ===
* ???

=== Closing a group ===
* [http://www.w3.org/2005/Incubator/XGR/about.html Publishing a final XG Report]

== Facet 2: by Role ==

=== About W3C Roles ===

* [http://www.w3.org/Guide/chair-roles.html Chair's role]
* [http://lists.w3.org/Archives/Member/chairs/1999JanMar/0056 Editor's role]
* [http://www.w3.org/Signature/Contributor.html Editor, Author, Contributor Policies]
* [http://www.w3.org/Guide/staff-contact.html Staff Contact's role]
* [http://www.w3.org/Guide/liaison-role Liaison's role] ('''Note''': Per [http://www.w3.org/2005/10/Process-20051014/liaisons section 10 of the Process Document], liaisons MUST be coordinated by the Team due to requirements for public communication; patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.)

=== Every WG Participant ===
* [http://www.w3.org/2004/01/pp-impl/ Join a group] (see also [http://www.w3.org/2004/08/invexp.html Invited Expert Policy])
* consider taking on roles: editor, test lead, etc.

=== Chair and Scribe ===

* Guidance: [http://www.w3.org/Guide/reagles-experiences.html On Chairing a group]
* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* organising a Face-to-face meetings
** Send face-to-face meeting information to calreq@w3.org; that information appears on the [http://www.w3.org/Member/Eventscal Member events calendar]
** [http://www.w3.org/Guide/hosting.htm Host a face-to-face meeting]. Note the [http://www.w3.org/2004/06/NoNDAPolicy.html Policy Regarding Non-Disclosure Agreements and W3C Meetings]
* [http://dev.w3.org/2002/scribe/scribedoc.htm#Quick_Start_Guide Quick start guide] for setting up tools for managing an agenda, generating minutes, and updating issues lists
* [http://www.w3.org/2008/04/scribe.html Scribe 101]: Taking meeting minutes using W3C IRC tools
* Individual IRC tools ("bots"):
** [http://www.w3.org/2001/12/zakim-irc-bot.html Zakim] for bridge management
** [http://www.w3.org/2002/03/RRSAgent RRSAgent] for minutes management
** [http://www.w3.org/2005/06/tracker/irc Trackbot] for issue management (using [http://www.w3.org/2005/06/tracker/ Tracker]) during an IRC-based meeting
* [http://lists.w3.org/Archives/Member/chairs/2002JanMar/0041 Guidance for Chairs] on Staff participation
* XG Chairs: For an account to let you or select XG participants write to w3.org, please contact Ian Jacobs
* [http://www.w3.org/Guide/transitions Transition requirements] (for First Public Draft, Last Call, CR, PR, REC, etc.)

=== Staff Contact ===

* work with systems team to set up [http://www.w3.org/Systems/Mail/ListRequest mailing-list], [http://www.w3.org/Guide/blog blog], [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki]
* Get editors an [http://www.w3.org/Systems/Accounts/w3t/ account (jigedit or CVS)] to edit the w3.org website
* [http://www.w3.org/Guide/pubrules Publication Rules] (a.k.a Pubrules) and links to related policies (e.g., [a href="http://www.w3.org/2005/07/13-nsuri namespaces] [http://www.w3.org/2002/06/registering-mediatype MIME type registration], and [http://www.w3.org/2005/05/tr-versions version management])

=== Editor ===

* information about [http://www.w3.org/Project/CVSdoc/ CVS]
* [http://www.w3.org/Guide/pubrules Publication Rules] (a.k.a Pubrules) and links to related policies (e.g., [a href="http://www.w3.org/2005/07/13-nsuri namespaces] [http://www.w3.org/2002/06/registering-mediatype MIME type registration], and [http://www.w3.org/2005/05/tr-versions version management])
* [http://www.w3.org/2003/Editors/ W3C Editors home page]
* Discussion about specifications on [http://lists.w3.org/Archives/Public/spec-prod/ spec-prod@w3.org]
* [http://www.w3.org/2001/06/manual/ W3C Manual of Style]

=== Test lead ===
* information about [http://www.w3.org/Project/CVSdoc/ CVS]

=== Liaison ===

== Facet 3: activities of a group ==

=== Build Consensus ===

* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* learn how to set up an ad-hoc meeting with zakim
* start a mailing-list
* get a [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki] for collaborative editing

=== Develop specification ===

* Know the rules
** [http://www.w3.org/Guide/pubrules Publication Rules] (a.k.a Pubrules) and links to related policies (e.g., [a href="http://www.w3.org/2005/07/13-nsuri namespaces] [http://www.w3.org/2002/06/registering-mediatype MIME type registration], and [http://www.w3.org/2005/05/tr-versions version management])
** [http://www.w3.org/Guide/transitions Transition requirements] (for First Public Draft, Last Call, CR, PR, REC, etc.)
** [http://www.w3.org/2002/05/rec-tips Tips for getting to Recommendation faster]
** [http://www.w3.org/2003/10/UseOfExtTech.html Use of W3C or Other Technologies within W3C Recommendations]
* Get editor(s), write drafts
** [http://www.w3.org/2003/Editors/ W3C Editors home page]
** Discussion about specifications on [http://lists.w3.org/Archives/Public/spec-prod/ spec-prod@w3.org]
** [http://www.w3.org/2001/06/manual/ W3C Manual of Style]
** You can write a spec using the [http://www.w3.org/2002/xmlspec/">W3C XML Specification DTD (XMLspec)], well-supported by Norman Walsh.
* Write better specs: QA resources
** [http://www.w3.org/TR/qaframe-spec/ Specification Guidelines]
** [http://www.w3.org/TR/qa-handbook/ Handbook for QA in groups] and [http://www.w3.org/QA/WG/qaframe-primer QA Framework primer]
** See also "testing" stuff
* Draft review, issue tracking
** get [http://www.w3.org/2005/06/tracker/ Tracker] for issues tracking
** alternatively [http://www.w3.org/Bugs bugzilla] can be used to track issues in a specification
*** … and create a disposition of comments with [http://www.w3.org/2007/02/bugs2html/ bugs2html]
* [http://www.w3.org/2005/06/tracker/irc Trackbot], an IRC-based interface to tracker
** [http://lists.w3.org/Archives/Member/chairs/2007JulSep/0117.html Tips on securing document reviews]

=== Patent Stuff ===
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Commentary: [http://www.w3.org/2003/12/22-pp-faq.html FAQ], [http://www.w3.org/2004/02/05-patentsummary.html Summary] and [http://www.w3.org/2004/03/pp-points-20040210.html Business Benefits]
* [http://www.w3.org/2004/01/pp-impl/ Implementation (IPP)]
* [http://www.w3.org/2004/08/25-chairs-pp.html What's in it for Chairs?]
* [http://www.w3.org/2004/10/27-testcases Policies for Contribution of Test Cases]
* ...more questions? Contact the [http://www.w3.org/2004/pp/psig/ W3C Patents and Standards Interest Group (PSIG)]

=== Test and Implement ===

* [http://www.w3.org/QA/WG/2005/01/test-faq Test Development FAQ]
* [http://dev.w3.org/cvsweb/2007/mobile-test-harness/ Mobile Web Test Harness] Web-based harness for browsers test suites
* test license @@

=== Promote your work ===

* Set up a Working-Group [http://www.w3.org/Guide/blog blog]
* Use the [http://www.w3.org/2004/09/SubmitTalk Upcoming Talks form]; talks publicized on the [http://www.w3.org/ W3C home page], [http://www.w3.org/Member/Newsletter/ Member Newsletter], [http://lists.w3.org/Archives/Public/w3c-announce/Public Weekly News] (approximately 8000 subscribers)
* [http://www.w3.org/2004/12/testimonial_pr-guidelines.htmlPress release testimonial guidelines]
* Give a [http://www.w3.org/2004/01/member-testimonials-hp.html testimonial] about how W3C participation has been beneficial to your organization. ([http://www.w3.org/Consortium/Member/Testimonial/ Current testimonials])
* [http://www.w3.org/Talks/Tools/Slidy/ HTML Slidy] for slide presentations
* [http://www.w3.org/2004/11/accessible-present Notes on Accessible Presentations]

== Facet 4: by Tool ==

=== blog ===
* Set up a Working-Group [http://www.w3.org/Guide/blog blog]

=== mailing-list ===

* [http://www.w3.org/Systems/Mail/ListRequest request the creation of a list]
* manage participants: [http://www.w3.org/Member/Mail/AuditForm Mailing List Audit] (who is subscribed, information about lists), [http://cgi.w3.org/member-bin/list_mgnt.pl List Management Tool], [http://www.w3.org/Guide/RemoteMaintainers SmartList Remote Maintainers Guide]
* No spam: [http://www.w3.org/2002/11/spam-filtering Spam filtering options]
* [http://www.w3.org/Search/Mail/Member Mailing Lists Search service]

=== wiki ===

* get a [http://lists.w3.org/Archives/Member/w3c-tools/2006JulSep/0000 wiki] for collaborative editing
* manage a wiki

=== tracking tools ===

* [http://www.w3.org/2005/06/tracker/ Tracker] for issues and action items tracking
* [http://www.w3.org/2005/06/tracker/irc Trackbot], an IRC-based interface to tracker
* [http://www.w3.org/Bugs bugzilla] can be used to track issues in a specification, and bugs in software/test suite

=== Polls and Questionaire ===

* [http://www.w3.org/2002/09/wbs/showwb WBS] is a web-based polling and questionaire system

=== IRC ===

* [http://dev.w3.org/2002/scribe/scribedoc.htm#Quick_Start_Guide Quick start guide] for setting up tools for managing an agenda, generating minutes, and updating issues lists
* [http://www.w3.org/2008/04/scribe.html Scribe 101]: Taking meeting minutes using W3C IRC tools
* Individual IRC tools ("bots"):
** [http://www.w3.org/2001/12/zakim-irc-bot.html Zakim] for bridge management
** [http://www.w3.org/2002/03/RRSAgent RRSAgent] for minutes management
** [http://www.w3.org/2005/06/tracker/irc Trackbot] for issue management (using [http://www.w3.org/2005/06/tracker/ Tracker]) during an IRC-based meeting

=== teleconference bridge ===

* [http://www.w3.org/Guide/1998/08/TeleconferenceHowTo schedule a recurring teleconference]
* zakim help

TPAC2012/SessionIdeas

Charles — Tue, 19 Jun 2012 05:45:28 GMT

Charles: /* Chair face-to-face */

We encourage attendees to start brainstorming [[TPAC2012]] session ideas in advance of the meeting.

== Sessions You Volunteer to Do ==

Please provide:
<ul class="show_items">
* session name (as a === subhead === )
* session proposer (optional: name a desired session leader, can be yourself)
* one sentence session summary
* 1+ paragraph session description
* type of session: (e.g.: talk, panel, open discussion, etc.)
* additional speakers/panelists
</ul>

== Sessions You Want Someone Else to Organize ==

Please provide:
<ul class="show_items">
* session topic (as a === subhead === )
* your name
* one sentence session summary
* 1+ paragraph session description
* If you support this session idea and are not the original proponent, please put your name and any supporting rationale. (Or, if you think this is not a good idea, please explain why.)
</ul>

== W3C staff notes on some suggestions ==

===Chair face-to-face===

* Part of a day. Suggested by TLR and with strong support of Membership (see May 2012 chairs thread).
* Some topics
** How do we find more quality editors?
** How much Process do we need to apply?
** How can we get things moving faster?
** What's the best place to have "Make It So, Team Contact" t-shirts printed?
** How do we make our work and documents more nimble?
** What parts of the Patent Policy are often ignored but particularly useful?
** Which of the gavel or bullwhip is most effective?
** Share your practical tricks (logistic, edito, document, great minutes ...) ?
** How to integrate the W3C transversal topics in deliverables(privacy, accessibility, ...) ?
** What about a standard WG dashboard for reporting our activities ?

==== session proposal ====
I ([[User:Charles|chaals]]) volunteer to run a single session on effective ways to manage a meeting. This is an action item from the AB, anyway.
Agenda:
#get volunteer co-chair
#brainstorm techniques
#review/select techniques
#review chairing process

===Community Groups===

* Breakouts based on CGs?

===Intro Day===

* I would like to see an Intro Day at TPAC, How to be a WG Participant (Liam)

===Process updates===

* Follow-on to May 2012 AC meeting

User:Charles

Charles — Tue, 19 Jun 2012 05:41:46 GMT

Charles: Created page with "I've been involved in W3C since the 90's. There are [http://chaals.com traces of me] all over the web and a lot of them point back to W3C, where I am co-chair of [http://www.w3.o…"

I've been involved in W3C since the 90's. There are [http://chaals.com traces of me] all over the web and a lot of them point back to W3C, where I am co-chair of [http://www.w3.org/2008/webapps/ webapps], and a member of the Advisory Board, inter alia.

TPAC2011

Charles — Thu, 03 Nov 2011 21:57:03 GMT

Charles: added pointer to 'revising process' CG

[http://www.w3.org/2011/11/TPAC/ TPAC 2011] (a [[Events|W3C event]]) takes place 31 Oct to 4 Nov 2011 in Santa Clara, California. The Plenary Day is 2 November.

This year the [[TPAC2011-Committee|TPAC2011 Program Committee]] has adopted a plenary day structure that encourages meeting participants to drive the agenda. Most of the day will consist of sessions chosen and led by participants. We encourage people to share their ideas in this wiki. This wiki also provides more operational information about the day.

[[TPAC2011/FAQ| FAQ: Questions?]]

==Plenary Day Structure==

The [[TPAC2011-Committee|TPAC2011 Program Committee]] is using a [[TPAC2011-Planning]] workspace to further develop the details.

{| border="1" cellpadding="5" cellspacing="0" width="80%"
|-
! Time
! Activity
! Notes
|-
| 08:30-09:00
| Jeff Jaffe on [[TPAC2011/Successes and Challenges|Successes and Challenges]] ([http://www.w3.org/2011/Talks/jj-tpac-20111102.pdf slides in PDF])
|
|-
| 09:00-09:30
| Plenary topic #1: [[TPAC2011/Web and Television|Web and Television]]
| Mark Vickers ([http://www.w3.org/2011/Talks/webtv-tpac-20111102.pdf combined slides with Clarke]), Chair; Giuseppe Pascale, Opera ([http://www.w3.org/2011/Talks/gp-hntf-usecases.html slides]); Clarke Stevens (CableLabs)
|-
| 09:30-10:00
| Plenary topic #2: [[TPAC2011/Web Content Interoperability|Web Content Interoperability]]
| Bryan Sullivan, Chair; Wilhelm Joys Andersen (Opera), Claudio Venezia (TIM), Soonho Lee (SK Telecom), Kai-Dietrich Scheppe (Deutsche Telekom)
|-
| 10:00-11:15
| Agenda building
| 10 min explanation of BarCamp-style intros, session proposing, participant-driven schedule grid.
|-
| 11:15-12:00
| Breakout 1
| 8 Rooms available for the day.
|-
| 12:00-13:30
| Lunch
|
|-
| 13:30-14:30
| Breakout 2
| (8 rooms - see below for breakout grid details)
|-
| 14:30-15:30
| Breakout 3
| (8 rooms)
|-
| 15:30-16:30
| Breakout 4
| (8 rooms)
|-
| 16:30-17:15
| Sharing and advocacy plenary
| Allow 15 more minutes?
|-
| 17:15-17:30
| Tim Berners-Lee Wrap-up plenary
|
|}

==Plenary Day Agenda Ideas==

The program committee has pre-selected the cross-group plenary topics and a small handful of breakout session proposals:

* [[TPAC2011/PlenaryBreakouts]] has the list of selected breakouts

Attendees were encouraged to brainstorm session ideas in advance of the meeting, both for cross-group plenary topics and for the breakout sessions:

* [[TPAC2011/SessionIdeas]] has the full list of proposals

We invite you to leave comments in the wiki in support of sessions or suggesting modifications. For the most part, actual breakout sessions will be determined by those present the day of the event, who will be free to propose sessions they've developed or new ideas. Please see the session page for more information about schedule and selection.

==Session Grid==
BarCamp/BreakOut Session Grid

'''This is a ''copy'' of the physical grid in the Plenary Room.''' Proposals are posted/managed on the physical grid. Please update this table only to reflect the actual physical grid.

* Note: (*) means pre-selected.
* Chairs, please identify a scribe and take notes in a new wiki page for your session. We encourage you to present that summary at the end of the day in the sharing plenary session.

{| border="1" cellpadding="5" cellspacing="0" width="80%"
|-
! time
! Grand Ballroom A (GBA)
! GBB
! GBC
! GBD
! GBE
! California Ballroom 1 (CB1)
! CB2
! CB3
|-
| 11:15-12:00
|[[TPAC2011/API Design Approaches and the Rationales for Them]] (*) [http://irc.w3.org/?channels=#apidesign #apidesign]
| [http://www.w3.org/wiki/TPAC2011/TestingBreakout Testing in web browsers]. James Graham and PLH [http://irc.w3.org/?channels=#testing #testing] [http://www.w3.org/2011/11/02-testing-minutes.html minutes];
| [http://www.w3.org/2011/11/02-global-minutes.html Global participation] [http://irc.w3.org/?channels=#global #global] [http://www.w3.org/2011/11/02-global-minutes.html minutes] [http://www.w3.org/wiki/TPAC2011/GlobalParticipationBreakout wiki notes]
| [http://www.w3.org/2011/11/02-webdocs-minutes.html Developer documentation]. Molly and Doug. [http://irc.w3.org/?channels=#webdocs #webdocs] [http://www.w3.org/2011/11/02-webdocs-minutes.html minutes]
| [http://www.w3.org/wiki/TPAC2011/Adjusting_to_explosion_of_input_methods Adjusting to explosion of input methods]. Judy and Kim. [http://irc.w3.org/?channels=#inputtypes #inputtypes]
| Social Business Jam. Alan and Steve. [http://irc.w3.org/?channels=#socialbizjam #socialbizjam] [http://www.w3.org/2011/11/02-socialbizjam-minutes.html minutes]
| Challenge of identity in Web. M. Mani. [http://irc.w3.org/?channels=#identity #identity] [http://www.w3.org/2011/11/02-identity-minutes.html minutes]
| [[TPAC2011/Semantic Syntaxes]] (*)
|-
| 13:30-14:30
| [http://www.w3.org/wiki/TPAC2011/SessionIdeas#Publishing_and_Linking_on_the_Web Is there a right to link?] Dan Appelquist [http://irc.w3.org/?channels=#righttolink #righttolink] [http://www.w3.org/2011/11/02-righttolink-minutes.html minutes]
| [[TPAC2011/Building Apps in the Cloud]] (*)
| Internet of things [http://irc.w3.org/?channels=#iot #iot] [http://www.w3.org/2011/11/02-iot-minutes.html minutes]
| [[TPAC2011/Agile Standardization]] [http://irc.w3.org/?channels=#agile #agile] [http://www.w3.org/2011/11/02-agile-minutes.html minutes]
| Content protection. Mark. [http://irc.w3.org/?channels=#webcp #webcp] [http://www.w3.org/2011/11/02-webcp-minutes.html minutes]
| Accessibility Q&A and Tips. Char. [http://irc.w3.org/?channels=#a11y #a11y]
| [[TPAC2011/Advances in Social Network Standardization]] (*)
| HTML WG decision policy. PLH. [http://irc.w3.org/?channels=#html-wg #html-wg]
|-
| 14:30-15:30
| [http://www.w3.org/2011/11/02-jquery-minutes.html What jquery and js developers want from web stds]. Paul and Yehuda. [http://irc.w3.org/?channels=#jquery #jquery] [http://www.w3.org/2011/11/02-jquery-minutes.html minutes]
| [http://www.w3.org/community/declarative3d/ Declarative 3D]. Johannes and Don and Kristen. [http://irc.w3.org/?channels=#dec3d #dec3d]
| [[TPAC2011/Web-based Digital Signage]] Toru [http://irc.w3.org/?channels=#signage #signage] [http://www.w3.org/2011/11/02-signage-minutes.html minutes]
| HTML5 AV Club. Kevin [http://irc.w3.org/?channels=#htmlav #htmlav] [http://www.w3.org/2011/11/02-htmlav-minutes.html minutes]
| [[TPAC2011/Linked data]]. Alexandre. [http://irc.w3.org/?channels=#linkeddata #linkeddata] [http://www.w3.org/2011/11/02-linkeddata-minutes.html minutes]
| [[TPAC2011/Revisiting how W3C creates standards]] #process (*) Kai and Marcos; [http://www.w3.org/2011/11/02-process-minutes.html Minutes], [http://www.w3.org/community/w3process/ Revising W3C Process CG]
| [http://www.w3.org/wiki/TPAC2011/web_as_operating_system_challenges Web operating system challenges] N.V.Balaji. [http://irc.w3.org/?channels=#wosch #wosch] [http://www.w3.org/wiki/TPAC2011/web_as_operating_system_challenges minutes]
|
|-
| 15:30-16:30
| [http://www.w3.org/2011/11/02-winteract-minutes.html Web Apis and Accessibility]. Raman and Charles. [http://irc.w3.org/?channels=#winteract #winteract] [http://www.w3.org/2011/11/02-winteract-minutes.html minutes]
|
| [[TPAC2011/Fixing schedule delays | Fixing schedule delays]]. Jeff Jaffe. [http://irc.w3.org/?channels=#schedule #schedule] [http://www.w3.org/2011/11/02-schedule-minutes.html minutes]; [http://www.w3.org/2011/11/02-schedule-minutes.html Minutes]
| [[TPAC2011/HTML5 and Games]] (*) [http://irc.w3.org/?channels=#games #games] [http://www.w3.org/2011/11/02-games-minutes.html minutes]
| [[TPAC2011/W3C Publications Ecosystem]] (*) [http://irc.w3.org/?channels=#pubs #pubs] [http://www.w3.org/2011/11/02-pubs-minutes.html minutes]
| Crypto API and Identity WG chartering - Privacy and Security issues. Nick/Halpin/Roessler. [http://irc.w3.org/?channels=#privacy #privacy] [http://www.w3.org/2011/11/02-privacy-minutes.html minutes]
| Demos. [http://irc.w3.org/?channels=#demos #demos]
| [[TPAC2011/Open Gov Data]]. Hadley. [http://irc.w3.org/?channels=#opendata #opendata] [http://www.w3.org/2011/11/02-opendata-minutes.html minutes]
|-
|}

==Overflow sessions==

{| border="1" cellpadding="5" cellspacing="0" width="80%"
|-
! time
! Other rooms
! Bar 104
! Lobby
! Poolside
|-
! 11:15-12:00
|
|
|
|
|-
! 13:30-14:30
| [http://wiki.whatwg.org/index.php?title=Component_Model Web Component Model]. #webapps in Room 1234
|
|
! Swim!
|-
! 14:30-15:30
| Web communication. Kepend Li. #webcomm
| HTML5 UI mapping to platform accessibility APIs [http://dev.w3.org/html5/html-api-map/overview.html]. #aapi. Cynthia
| Converge address book ... Web TV. #cab
| Measuring the Web. Steve Bratt. #windex
|-
! 15:30-16:30
|
| [[Web first]]. Downsize the W3C, spin out sem web. Alex Russell. #webfirst
| [[Multi-screen Web]]. Hiroyuki Aizu. #multiscreen
| Registries. Debbie Dahl. #registries.
|}
<ul class="show_items">
* Grand Ballrooms hold ~40
* California Ballrooms hold ~35
</ul>

SVG/Debugging

Charles — Sat, 22 May 2010 19:41:01 GMT

Charles: meh, use the SVGIG wiki

This page has been shifted into the [http://www.w3.org/Graphics/SVG/IG/wiki/Editor_wishlist SVG-IG editor wishlist]

SVG/Debugging

Charles — Sat, 22 May 2010 17:38:21 GMT

Charles: Grr. wiki marku ;(

Tools for debugging SVG, what we would like to see in them.

For browser-based debugging tools like Dragonfly (Opera) or Firebug (Firefox):

* A bounding-box view for the current element (analagous to the box model for CSS, which isn't relevant to SVG)
* A graphic editing tool

SVG/Debugging

Charles — Sat, 22 May 2010 17:37:42 GMT

Charles: created.

Tools for debugging SVG, what we would like to see in them.

For browser-based debugging tools like Dragonfly (Opera) or Firebug (Firefox):

+ A bounding-box view for the current element (analagous to the box model for CSS, which isn't relevant to SVG)
+ A graphic editing tool

RdfCalendarMeetings

Charles — Thu, 05 Feb 2004 00:05:55 GMT

Charles: added details for meeting that just happened

__NOTOC__
meetings on [[RdfCalendar]]...

see also: [[ScheduledTopicChat]]

The [http://lists.w3.org/Archives/Public/www-rdf-calendar/2001Apr/0001.html www-rdf-calendar announcement] of April 2001 followed an [http://www.w3.org/2001/02/rdfig-f2f/ RDF Interest Group meeting] at which several of us realised we shared an interest in this area. There is also a [http://www.xml.com/lpt/a/2001/07/25/rdfcalendar.html writeup on xml.com], July 2001, that provides a bit more background.

Following a workshop in Bristol, and discussion on [http://lists.w3.org/Archives/Public/www-rdf-calendar/ www-rdf-calendar] we set up an
[http://www.w3.org/2002/12/cal/ RDF Calendar Workspace]
to manage an [[RdfCalendarSchema]] and test collection (see [http://ilrt.org/discovery/chatlogs/rdfig/2003-06-11#T16-18-38 2003-06-11 #rdfig] for more historical background).

== Meetings ==


We hold the occasional [[ScheduledTopicChat]], announced
to [http://lists.w3.org/Archives/Public/www-rdf-calendar/ www-rdf-calendar]
and held in [irc://irc.freenode.net:6667/rdfig #rdfig on freenode] (''oops... [[ChannelsAreResourcesToo]]'').
The IRC [http://ilrt.org/discovery/chatlogs/rdfig/ logs] and [http://rdfig.xmlhack.com weblogs] generally serve as meeting records, though
summaries are sometimes mailed out.

Another meeting is scheduled for 4 February 2004, 22:00 UTC @@put more useful pointer here

=== 2004 ===

* something in late feb - watch this space and the [http://lists.w3.org/Archives/Public/www-rdf-calendar www-rdf-calendar list]
* 5 Feb: [http://rdfig.xmlhack.com/2004/02/04/2004-02-04.html#1075931374.996699 summary], [http://www.ilrt.bris.ac.uk/discovery/chatlogs/rdfig/2004-02-04.html#T22-09-10 irc log]

=== 2003 ===
* 10th Sept: [http://rdfig.xmlhack.com/2003/09/10/2003-09-10.html weblog]
* 20th Aug: [http://rdfig.xmlhack.com/2003/08/20/2003-08-20.html weblog]
* 30th Jul: [http://rdfig.xmlhack.com/2003/07/30/2003-07-30.html weblog]
* 9 Jul: finishing up prodid and x-properties, tangible progress on round-trip testing. [http://rdfig.xmlhack.com/2003/07/09/2003-07-09.html#1057762684.880168 weblog]
* 25 Jun: prodid and x-properties, round-trip testing, [[EmailVocabulary]] [http://rdfig.xmlhack.com/2003/06/25/2003-06-25.html#1056550875.665269 weblog]
* 11 Jun: chandler [http://rdfig.xmlhack.com/2003/06/11/2003-06-11.html#1055344744.381612 weblog]
* 14 May: [http://rdfig.xmlhack.com/2003/05/14/2003-05-14.html weblog]
* 23 Apr: [[EventDiscovery]] and a few other things [http://rdfig.xmlhack.com/2003/04/23/2003-04-23.html#1051109485.240329 weblog, attendance, agenda, minutes/actions]
* 9 Apr: mixing calendar with geo stuff. [http://rdfig.xmlhack.com/2003/04/09/2003-04-09.html weblog], including [http://rdfig.xmlhack.com/2003/04/09/2003-04-09.html#1049887025.577460 list of attendees]
* 26 Mar: mostly about wiki stuff. [http://rdfig.xmlhack.com/2003/03/26/2003-03-26.html#1048697881.388674 weblog].
* 12 Mar: license foo, business hours usecase [http://lists.w3.org/Archives/Public/www-rdf-calendar/2003Mar/0028.html summary]
* 26 Feb: prodid etc. [http://rdfig.xmlhack.com/2003/02/26/2003-02-26.html weblog]
* ... [http://www.w3.org/2002/12/cal/#mtg earlier meetings]

We try to eat our own dogfood:
[http://www.w3.org/2002/12/cal/test/20030423mtg.rdf calendar, 2003-04-23]
[http://www.w3.org/2002/12/cal/test/20030409mtg.rdf calendar, 2003-04-09]
[http://www.w3.org/2002/12/cal/test/20030326mtg.rdf calendar, 2003-03-26]
[http://www.w3.org/2002/12/cal/test/20030312mtg.rdf calendar, 2003-03-12]
[http://www.w3.org/2002/12/cal/test/20030226mtg.rdf calendar, 2003-02-26]
[http://www.w3.org/2002/12/cal/test/20030212mtg.rdf calendar, 2003-02-12]
[http://www.w3.org/2002/12/cal/test/20030205mtg.rdf calendar, 2003-02-05]
[http://www.w3.org/2002/12/cal/test/20030122mtg.rdf calendar, 2003-01-22]
[http://www.w3.org/2002/12/cal/test/20030115mtg.rdf calendar, 2003-01-15]
[http://www.w3.org/2002/12/cal/test/mtg.rdf calendar, 2003-01-08]

agenda requests for upcoming meetings:

* mixing in [[GeoInfo]]; e.g. [[TravelTools]]. [http://rdfig.xmlhack.com/2003/03/28/2003-03-28.html#1048862913.413335 SVG geo stuff], [http://ilrt.org/discovery/chatlogs/rdfig/2003-03-28#T14-57-00 danbri on zool making connections] - we discussed this 2003-04-23 meeting [http://ilrt.org/discovery/chatlogs/rdfig/2003-04-09.html logs] [http://rdfig.xmlhack.com/2003/04/09/2003-04-09.html weblog]. Work will continue in a Geo-themed meeting, [http://www.timeanddate.com/worldclock/fixedtime.html?day=16&month=4&year=2003&hour=14&min=0&sec=0&p1=0 2003-04-16, 1400UTC], see Agenda draft on [[GeoInfo]], [http://www.w3.org/2002/12/cal/test/20030416geomtg.rdf RDF schedule].

WWW2004

Charles — Sun, 04 Jan 2004 23:03:15 GMT

Charles:

__NOTOC__
some thoughts on community coverage of WWW2004...

[http://www.www2004.org WWW2004] will be held in New York City in May. Between digital cameras, chumpbots, RDF, and wireless connectivity, it ought to be more feasiable than ever to provide interesting, searchable documentation of the conference.

Let's build a semantic photo archive and other community-based documentation.

See also: [[ConnectingAudiences]].

== Rough Ideas ==

* Compare to [http://www2003.xmlhack.com/ WWW2003 community coverage]
* [http://ilrt.org/discovery/chatlogs/rdfig/2003-11-03#T15-39-52 discussion] on 2003-11-03
* make a chump, irc, blog, photoblog
* describe people, locations, things, photos, movies, audio files
* link historical info - early computers, experiments
* trying not to make it all too fragile; semweb tech to make that happen:
** foaf for people
** rss 1.0 for feeds, and
** other vocabs for photos, geo
* harvest the bits up and present them in different ways - photo view, news view
* geo-location view:
** integration of RDF-cal, WMS maps of registered users, rooms and so on like for [http://demo.asemantics.com/biz/buda/ www2003] in budapest or similars
** [http://www.asemantics.com/showcase/wms.html WMS] maps of users, developers, companies as RDF or Web [http://www.asemantics.com/showcase/zoom.html layers], well do one for the [[FoaF Attendee]] attendee list when there are some names to show ([http://cvs.apache.org/~dirkx/sgala.html this] is what we are thinking off (showing the apache committers)).

== Interested People ==

People interested in getting involved, please add your name here - or even better - add it to this [[FoaF Attendee]] list.

[[GregElin]] - on the ground in New York City and interested in incorporating http://www.fotonotes.net to make annotating images easy.

[[Dave Beckett]] - helped out with the [http://www2003.xmlhack.com/ WWW2003 community coverage] and irc last year.

[http://foaf.asemantics.com/alberto Alberto Reggiori], [http://foaf.asemantics.com/dirkx Dirk Willem van Gulik] - http://www.asemantics.com

Paul Cowles - http://www.semaview.com - will publish conference calendar with Sherpa (RDF output) and attendees may subscribe (ala iCal) to the published RDF schedule for free (tool is free to consume cals). Others may extend the RDF to include GEO, FOAF etc.

[[Bryce Benton]] - can help with php/mysql and front-end interfaces.

== WWW conference photo archive ==

A project to gather together photos from various WWW conferences and annotate them with depiction data.

=== Meetings and actions ===

* [http://www.timeanddate.com/worldclock/fixedtime.html?day=6&month=1&year=2004&hour=15&min=0&sec=0&p1=0 next meet (provisional) 2004-01-06, 15:00 UTC]
* [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071846235.658126 2003-12-19 IRC meet] (see agenda items on page)

Actions:
* Greg: [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071847723.308502 write a high-level description of the system]
* Greg: [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071847422.440217 talk to Ben, Mike, Stu about hosting]
* Libby: [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071846689.181751 ask Aaron about licensing issues] ([http://lists.w3.org/Archives/Public/www-archive/2003Dec/0040.html request made])
* danbri: [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071846657.226390 request w3c list / archive for this project]
* libby/danbri/nick/steve: [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071846632.524330 to work on an account of the data we'd want. it may not need a new schema at all]
* jim/nick/steve: [http://rdfig.xmlhack.com/2003/12/19/2003-12-19.html#1071846632.524330 focus first on conference data]
* [http://rdfig.xmlhack.com/2003/12/18/2003-12-18.html#1071760457.693080 2003-12-18 IRC meet]

=== notes about WWW2004 conference photo archive ===

Nick's 4 main areas of work:

1) ontology for annotation and metadata
2) infrastructure (scutters, rdf stores, etc)
3) annotation tools and
4) publication tools (searching, browsing, exploring, etc)

Some ideas from libby - feel free to edit/expand:

* deciding the sorts of information we are interested in, and
documenting how to do this (for tool developers and perhaps early users)
* creating some means for creators to tell us about their images and metadata (could be as simple as the [http://rdfweb.org/topic/FOAFBulletinBoard foaf bulletin board])
* creating or adapting existing tools (like [http://www.ldodds.com/foaf/foaf-a-matic foaf-a-matic], for example), which just generate the RDF metadata, but don't upload it --CMN: I have been pondering the idea of using [http://www.w3.org/2001/Annotea Annotea] to annotate an email address as a way of uploading FOAF data.
* adapting and using tools to harvest, store and query RDF (including
provenance tracking, deleting)
* creating generic uploading and editing RDF document facilities withaccess control for the images and metadata (e.g. something like [http://sw1.ilrt.org/discovery/2003/11/ilrt-interests/ ILRT interests database])
* designing the user interface for browsing and searching the photos

also

* the user should be able to point at the same instances of (say) Libby Miller that other people have referred to when annotating a photo, so that the data all joins up - tricky
* think of a CC license for the photos (libby talk to Aaron?)
* investigate legal issues? privacy? removing photos on request?
* how open should it be?
* where should the photos and RDF be kept?
* what sort of pictures are we interested in? small or large group pictures, informal/formal, individuals?
* what things do we want to describe?
** (Greg)
creator of photo
location of photo
date of photo

* (nick)
DC for photo, papers
depictions of things in the photo
other things about people

* (libby)
location, event (incl date) photos taken at
description of photo
depictions - mostly people, id'd by hashed email
annotator, date annotated
creator
CC info

AboutThisService

Charles — Thu, 19 Jun 2003 15:48:36 GMT

Charles:

__NOTOC__
[[DanBri]] set up an ESW Wiki using TWiki, January 2002 ([http://esw.w3.org/mt/esw/archives/000017.html weblog notes]; [http://esw.w3.org/mt/esw/archives/000027.html upgrade announcement]).

After researching some infelicities, we decided to migrate to [[MoinMoin]]
([[ToDo]]: grab rationale, [[LinkMe]]: discussion in #rdfig about lost updates and such).

[[SandroHawke]] installed [[MoinMoin]], and DanC did the migration;
see [http://lists.w3.org/Archives/Public/www-archive/2003Mar/0084.html imported ESW twiki stuff into moinmoin] Wed, Mar 26 2003.

<code><nowiki>/t/view/TopicName</nowiki></code> (older TWiki URIs) are now redirected to <code><nowiki>/topic/TopicName</nowiki></code>.

Remaining TWiki migration issues: moin doesn't like wikinames to begin with acronyms. So PPR:[[HowToRenameWikiPages]] may be useful. It wasn't! Nothing useful in there. Hmm.

----

We need clear license terms... e.g. a [[CreativeCommons]] logo
right next to the 'save' button on the edit page.

----

oops... is the output of this service not XHTML happy? evidently not.

----

wow! [[DanConnolly]] thought you had to start new pages my making
links from existing pages... wants a "making new islands is
not cool" blurb in the "you can create this page now" text.

----

a concern about the preservation of the information here... should we archive the HTML
version as well? else we need [[MoinMoin]] to reconstruct it; who knows if that'll be
feasible in 20 years.

''You can use `moin-dump` to create a static HTML version, tar that and store it away, by using a cron job. Also, you won't have to wait 20 years till you can do the same and create an XML dump.''

----

Needless URL duplication? why have ?action=view instead of just a link to the
topic itself. The 'clear comment' link you see after editing, in particular, encourages two URLs to get deployed for each Wiki topic.

----

[[MoinMoin]] is a Python Wiki:[[WikiClone]], based on Wiki:[[PikiPiki]]. The name is a common German slang expression explained on the [[MoinMoin]] page. If you run a Wiki using [[MoinMoin]], please add it to the [[MoinMoin]]:[[MoinMoinWikis]] page. Contributed code is on the [[MoinMoin]]:[[MacroMarket]], [[MoinMoin]]:[[ActionMarket]] and [[MoinMoin]]:[[ParserMarket]] pages.

----

Eeek! the ?action=subscribe thingy is an unsafe GET! (see [http://www.w3.org/2001/tag/doc/get7 W3C TAG finding] for why we should care).

----

= Testing Basic Internationalization =
This is a test to see how well this Wiki deals with non-ASCII characters: Some German: Übersetzung, some Japanese: 翻訳 some arabic السلام

One the other hand trying to add the character ő was a pain - then it doesn't always round trip (it did sometimes :(. On the other hand I cannot get it to work in the word Bevezető on the page [[SemWebMagyar]] (maybe because it is in a link??) -- Chaals

Seems to be okay for posting, but on reediting, I get numeric character references (NCR) for Japanese, which makes it impossible to edit actual Japanese (even more so because they are decimal).

Fortunately, the numeric character references get backconverted. But then, can I add an example of an NCR in test? Example NCR: &#x5678;. We should try to change the editing page (or even better, everything) to UTF-8.

Puting in an NCR with &#x5678; didn't work. Let's try some more variants: hex: &#x5678;, decimal: &#x5678;

Using a decimal '&', i.e. &#38; seems to be the only thing that works. Pretty lame and inconvenient.
But at least there is safe roundtripping.

& or `&` (after all, it's `code`)

AboutThisService

Charles — Thu, 19 Jun 2003 15:42:54 GMT

Charles:

__NOTOC__
[[DanBri]] set up an ESW Wiki using TWiki, January 2002 ([http://esw.w3.org/mt/esw/archives/000017.html weblog notes]; [http://esw.w3.org/mt/esw/archives/000027.html upgrade announcement]).

After researching some infelicities, we decided to migrate to [[MoinMoin]]
([[ToDo]]: grab rationale, [[LinkMe]]: discussion in #rdfig about lost updates and such).

[[SandroHawke]] installed [[MoinMoin]], and DanC did the migration;
see [http://lists.w3.org/Archives/Public/www-archive/2003Mar/0084.html imported ESW twiki stuff into moinmoin] Wed, Mar 26 2003.

<code><nowiki>/t/view/TopicName</nowiki></code> (older TWiki URIs) are now redirected to <code><nowiki>/topic/TopicName</nowiki></code>.

Remaining TWiki migration issues: moin doesn't like wikinames to begin with acronyms. So PPR:[[HowToRenameWikiPages]] may be useful. It wasn't! Nothing useful in there. Hmm.

----

We need clear license terms... e.g. a [[CreativeCommons]] logo
right next to the 'save' button on the edit page.

----

oops... is the output of this service not XHTML happy? evidently not.

----

wow! [[DanConnolly]] thought you had to start new pages my making
links from existing pages... wants a "making new islands is
not cool" blurb in the "you can create this page now" text.

----

a concern about the preservation of the information here... should we archive the HTML
version as well? else we need [[MoinMoin]] to reconstruct it; who knows if that'll be
feasible in 20 years.

''You can use `moin-dump` to create a static HTML version, tar that and store it away, by using a cron job. Also, you won't have to wait 20 years till you can do the same and create an XML dump.''

----

Needless URL duplication? why have ?action=view instead of just a link to the
topic itself. The 'clear comment' link you see after editing, in particular, encourages two URLs to get deployed for each Wiki topic.

----

[[MoinMoin]] is a Python Wiki:[[WikiClone]], based on Wiki:[[PikiPiki]]. The name is a common German slang expression explained on the [[MoinMoin]] page. If you run a Wiki using [[MoinMoin]], please add it to the [[MoinMoin]]:[[MoinMoinWikis]] page. Contributed code is on the [[MoinMoin]]:[[MacroMarket]], [[MoinMoin]]:[[ActionMarket]] and [[MoinMoin]]:[[ParserMarket]] pages.

----

Eeek! the ?action=subscribe thingy is an unsafe GET! (see [http://www.w3.org/2001/tag/doc/get7 W3C TAG finding] for why we should care).

----

= Testing Basic Internationalization =
This is a test to see how well this Wiki deals with non-ASCII characters: Some German: Übersetzung, some Japanese: 翻訳 some arabic السلام

One the other hand trying to add the character ő was a pain. if you add &#337; then it doesn't always round trip (it did sometimes :(, but if you add &#0337; it seems to come out fine here. On the other hand I cannot get it to work in the word Bevezető on the page [[SemWebMagyar]] (maybe because it is in a link??) -- Chaals

Seems to be okay for posting, but on reediting, I get numeric character references (NCR) for Japanese, which makes it impossible to edit actual Japanese (even more so because they are decimal).

Fortunately, the numeric character references get backconverted. But then, can I add an example of an NCR in test? Example NCR: &#x5678;. We should try to change the editing page (or even better, everything) to UTF-8.

Puting in an NCR with &#x5678; didn't work. Let's try some more variants: hex: &#x5678;, decimal: &#x5678;

Using a decimal '&', i.e. &#38; seems to be the only thing that works. Pretty lame and inconvenient.
But at least there is safe roundtripping.

& or `&` (after all, it's `code`)

SemWebMagyar

Charles — Thu, 19 Jun 2003 15:38:08 GMT

Charles:

__NOTOC__
Szemantikus Web magyarul

[http://www.w3.org/2001/sw/Europe/200305/foaflang/ Ki ért Magyarul?] (FOAF). [http://dict.sztaki.hu/english-hungarian Angol-Magyar Szótár]

* [http://w3c.hu Magyar W3C Iroda]
* Az oldalt [http://et.progos.hu Vojnisek Péter] szerkeszti

Dokumentumok
* [http://www.w3.org/2002/Talks/2409-Budapest-IH/0.html Szemantikus Web: Bevezeto]

SemWebMagyar

Charles — Thu, 19 Jun 2003 15:34:09 GMT

Charles:

SemWebMagyar

Charles — Thu, 19 Jun 2003 15:31:49 GMT

Charles:

AboutThisService

Charles — Thu, 19 Jun 2003 15:31:07 GMT

Charles:

__NOTOC__
[[DanBri]] set up an ESW Wiki using TWiki, January 2002 ([http://esw.w3.org/mt/esw/archives/000017.html weblog notes]; [http://esw.w3.org/mt/esw/archives/000027.html upgrade announcement]).

After researching some infelicities, we decided to migrate to [[MoinMoin]]
([[ToDo]]: grab rationale, [[LinkMe]]: discussion in #rdfig about lost updates and such).

[[SandroHawke]] installed [[MoinMoin]], and DanC did the migration;
see [http://lists.w3.org/Archives/Public/www-archive/2003Mar/0084.html imported ESW twiki stuff into moinmoin] Wed, Mar 26 2003.

<code><nowiki>/t/view/TopicName</nowiki></code> (older TWiki URIs) are now redirected to <code><nowiki>/topic/TopicName</nowiki></code>.

Remaining TWiki migration issues: moin doesn't like wikinames to begin with acronyms. So PPR:[[HowToRenameWikiPages]] may be useful. It wasn't! Nothing useful in there. Hmm.

----

We need clear license terms... e.g. a [[CreativeCommons]] logo
right next to the 'save' button on the edit page.

----

oops... is the output of this service not XHTML happy? evidently not.

----

wow! [[DanConnolly]] thought you had to start new pages my making
links from existing pages... wants a "making new islands is
not cool" blurb in the "you can create this page now" text.

----

a concern about the preservation of the information here... should we archive the HTML
version as well? else we need [[MoinMoin]] to reconstruct it; who knows if that'll be
feasible in 20 years.

''You can use `moin-dump` to create a static HTML version, tar that and store it away, by using a cron job. Also, you won't have to wait 20 years till you can do the same and create an XML dump.''

----

Needless URL duplication? why have ?action=view instead of just a link to the
topic itself. The 'clear comment' link you see after editing, in particular, encourages two URLs to get deployed for each Wiki topic.

----

[[MoinMoin]] is a Python Wiki:[[WikiClone]], based on Wiki:[[PikiPiki]]. The name is a common German slang expression explained on the [[MoinMoin]] page. If you run a Wiki using [[MoinMoin]], please add it to the [[MoinMoin]]:[[MoinMoinWikis]] page. Contributed code is on the [[MoinMoin]]:[[MacroMarket]], [[MoinMoin]]:[[ActionMarket]] and [[MoinMoin]]:[[ParserMarket]] pages.

----

Eeek! the ?action=subscribe thingy is an unsafe GET! (see [http://www.w3.org/2001/tag/doc/get7 W3C TAG finding] for why we should care).

----

= Testing Basic Internationalization =
This is a test to see how well this Wiki deals with non-ASCII characters: Some German: Übersetzung, some Japanese: 翻訳 some arabic السلام

One the other hand trying to add the character ő was a pain. if you add &#337; then it doesn't always round trip (it did sometimes :(, but if you add &#0337; it seems to come out fine.

Seems to be okay for posting, but on reediting, I get numeric character references (NCR) for Japanese, which makes it impossible to edit actual Japanese (even more so because they are decimal).

Fortunately, the numeric character references get backconverted. But then, can I add an example of an NCR in test? Example NCR: &#x5678;. We should try to change the editing page (or even better, everything) to UTF-8.

Puting in an NCR with &#x5678; didn't work. Let's try some more variants: hex: &#x5678;, decimal: &#x5678;

Using a decimal '&', i.e. &#38; seems to be the only thing that works. Pretty lame and inconvenient.
But at least there is safe roundtripping.

& or `&` (after all, it's `code`)

AboutThisService

Charles — Thu, 19 Jun 2003 15:30:09 GMT

Charles: figuring out oddness with NCRs

__NOTOC__
[[DanBri]] set up an ESW Wiki using TWiki, January 2002 ([http://esw.w3.org/mt/esw/archives/000017.html weblog notes]; [http://esw.w3.org/mt/esw/archives/000027.html upgrade announcement]).

After researching some infelicities, we decided to migrate to [[MoinMoin]]
([[ToDo]]: grab rationale, [[LinkMe]]: discussion in #rdfig about lost updates and such).

[[SandroHawke]] installed [[MoinMoin]], and DanC did the migration;
see [http://lists.w3.org/Archives/Public/www-archive/2003Mar/0084.html imported ESW twiki stuff into moinmoin] Wed, Mar 26 2003.

<code><nowiki>/t/view/TopicName</nowiki></code> (older TWiki URIs) are now redirected to <code><nowiki>/topic/TopicName</nowiki></code>.

Remaining TWiki migration issues: moin doesn't like wikinames to begin with acronyms. So PPR:[[HowToRenameWikiPages]] may be useful. It wasn't! Nothing useful in there. Hmm.

----

We need clear license terms... e.g. a [[CreativeCommons]] logo
right next to the 'save' button on the edit page.

----

oops... is the output of this service not XHTML happy? evidently not.

----

wow! [[DanConnolly]] thought you had to start new pages my making
links from existing pages... wants a "making new islands is
not cool" blurb in the "you can create this page now" text.

----

a concern about the preservation of the information here... should we archive the HTML
version as well? else we need [[MoinMoin]] to reconstruct it; who knows if that'll be
feasible in 20 years.

''You can use `moin-dump` to create a static HTML version, tar that and store it away, by using a cron job. Also, you won't have to wait 20 years till you can do the same and create an XML dump.''

----

Needless URL duplication? why have ?action=view instead of just a link to the
topic itself. The 'clear comment' link you see after editing, in particular, encourages two URLs to get deployed for each Wiki topic.

----

[[MoinMoin]] is a Python Wiki:[[WikiClone]], based on Wiki:[[PikiPiki]]. The name is a common German slang expression explained on the [[MoinMoin]] page. If you run a Wiki using [[MoinMoin]], please add it to the [[MoinMoin]]:[[MoinMoinWikis]] page. Contributed code is on the [[MoinMoin]]:[[MacroMarket]], [[MoinMoin]]:[[ActionMarket]] and [[MoinMoin]]:[[ParserMarket]] pages.

----

Eeek! the ?action=subscribe thingy is an unsafe GET! (see [http://www.w3.org/2001/tag/doc/get7 W3C TAG finding] for why we should care).

----

= Testing Basic Internationalization =
This is a test to see how well this Wiki deals with non-ASCII characters: Some German: Übersetzung, some Japanese: 翻訳 some arabic السلام

One the other hand trying to add the character ő was a pain. if you add ő then it doesn't round trip, but if you add &#0337; it seems to come out fine.

Seems to be okay for posting, but on reediting, I get numeric character references (NCR) for Japanese, which makes it impossible to edit actual Japanese (even more so because they are decimal).

Fortunately, the numeric character references get backconverted. But then, can I add an example of an NCR in test? Example NCR: &#x5678;. We should try to change the editing page (or even better, everything) to UTF-8.

Puting in an NCR with &#x5678; didn't work. Let's try some more variants: hex: &#x5678;, decimal: &#x5678;

Using a decimal '&', i.e. &#38; seems to be the only thing that works. Pretty lame and inconvenient.
But at least there is safe roundtripping.

& or `&` (after all, it's `code`)

SemWebMagyar

Charles — Thu, 19 Jun 2003 15:17:59 GMT

Charles:

Charles — Fri, 30 May 2003 09:31:07 GMT

Charles: What publishing facility do people have?

__NOTOC__
In the beginning, there was the HTML meta element.
Then came PICS, which could be carried inside meta elements.
Then came RDF, in some ways a generalization of PICS, written in XML,
and XHTML, also written in XML. Whence comes the question...

''How do I put RDF in my HTML document?''
* [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport appendix B of the 1999 RDF spec] suggests sticking RDF in the head of an HTML document, but the result doesn't conform to the XHTML specs. (more in [http://infomesh.net/2002/rdfinhtml/#embedNoValidate Part I of RDF in HTML: Approaches])
* The initial [[CreativeCommons]] deployment involves putting RDF inside comments inside HTML. Blech!
* stick the RDF/XML in the XHTML document, and build a modular DTD (details in [http://infomesh.net/2002/rdfinhtml/#embedAndValidate Part II of RDF in HTML: Approaches])
* make a separate RDF file and link to it
* [[AnswerMe]]. ''each of these ideas seems to fall short in some way that's critical to some constituency.''

What sort of RDF metadata do folks want to put in their HTML documents, anyway?

* bibliographic metdata; e.g. [[DublinCore]] (see also: [http://www.w3.org/2000/06/dc-extract/form DC extraction service]
* rights metdata; e.g. [[CreativeCommons]]
* geographic info: [http://ilrt.org/discovery/chatlogs/rdfig/2003-04-30#T16-10-36 discussion of geourl, HTML meta, and RDF]
* news; e.g. [http://www.w3.org/2000/08/w3c-synd/ site summaries]
* all kinds of RDF that people develop, but can only put onto their geocities or semi-controlled HTML web pages

----
references, newest first:

* [http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/ public-rdf-in-xhtml-tf] started May 21 2003
* [http://www.w3.org/2003/03/rdf-in-xml.html RDF in XHTML] tasks approaches from Joseph Reagle
* [http://ilrt.org/people/cmdjb/2003/05/iswc/paper.html paper on revising of RDF/XML] by Dave Beckett including known problems, requirements for new syntaxes, analysis of existing work.
* [http://www.w3.org/MarkUp/Group/2003/WD-xhtml2-20030506/mod-meta.html#sec XHTML Metainformation Module] in XHTML2 WD draft.
* [http://www.w3.org/2001/sw/meetings/tech-200303/#s-rdf-html RDF and HTML] session in the March 2003 Semantic Web Architecture meeting in Cambridge
* [http://www.w3.org/TR/2003/WD-rdf-syntax-grammar-20030123/#section-rdf-in-HTML|Using RDF/XML with HTML and XHTML] in the RDF Syntax WD (January 2003)
* [[TagIssue]]:RDFinXHTML-35
* [http://infomesh.net/2002/rdfinhtml/ RDF in HTML: Approaches], May 2002 by Sean B.
* [http://www.w3.org/DesignIssues/Syntax.html A strawman Unstriped syntax for RDF in XML] esp section "RDF in HTML - Transparent or not?", Jun 1999 by TimBL
* [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport appendix B to 1999 RDF spec]

----
[[Category:Faq]], [[ProxyTopic]]

evidence that this is a real FAQ: [http://ilrt.org/discovery/chatlogs/rdfig/2003-05-12#T16-18-53 discussion 12May] although that question was where was the justification. Answer: in the RDF Model and Syntax spec appendix B.