- From: Dave Raggett <dsr@w3.org>
- Date: Thu, 07 Mar 2013 10:52:08 +0000
- To: public-sysapps@w3.org
> Once the WG has reached consensus on which of the proposed drafts to
> work on, each specification will be given its own repository on the
> SysApps Organization on Github. Each repository will be named after
> the expected specification shortname. For example, a specification
> using 'foo' as a W3C shortname should be inside sysapps/foo and be
> accessible from https://github.com/sysapps/foo/. Having each
> specification in its own repository provides both editors and
> interested parties a single palce to monitor changes and issues
> related to a particular specification.
One small addition is the need for us to check that the proposed
specification shortname don't conflict with existing ones.
For Phase 1, we have:
Alarm --> web-alarms FPWD 5 Feb 2013
Contacts --> contacts-manager-api FPWD expected today
The following are still in the pipeline and need shortnames:
Execution & Security Models
Messaging
Telephony
Raw Sockets
The Device APIs WG has a historical published Working Draft with the
short name "messaging-api", see:
http://dev.w3.org/2009/dap/messaging/
http://www.w3.org/TR/2011/WD-messaging-api-20110414/
So we may want to avoid "messaging-api". However, if we want to re-use
that one, I can ask the Device APIs WG if they are agreeable to that,
given that they have suspended work on it. I would also need to seek
confirmation from the webmaster that this is okay, given the change of
working group. Should I give this a try, or should we seek a new short name?
Any suggestions for the remaining Phase 1 deliverable short names?
--
Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Thursday, 7 March 2013 11:10:59 UTC