W3C Wiki - Recent changes [en]

Webapps/WebComponentsJune2013Meeting

Abarsto — Tue, 21 May 2013 00:07:24 GMT

Agenda:

New page

This is the Meeting Page including Agenda for the Web Applications WG (WebApps) Web Components meeting in San Francisco CA US on Thursday June 21.

To register for this meeting, contact [Dimitri Glazkov mailto:dglazkov@google.com]. The registration deadline is @TBD.

== Meeting Logistics ==

* Meeting Host = Google
* IRC channel = #webapps; irc.w3.org:6665
* Date = June 21 2013
* Time = See below; all times are US West Coast time zone
* Location = @ TBD
* Meeting Room = @TBD
* Phone Conference Bridge: W3C's Zakim Bridge will be used if needed. +1.617.761.6200; see also [http://www.w3.org/2006/tools/wiki/Zakim-SIP Zakim SIP Bridge]; PIN = 92323#

== 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#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]
* [http://www.w3.org/2008/webapps/wiki/WorkMode Group's Work Mode]

== Agenda ==

* 09:00 - 09:30 -
* 09:30 - 10:30 -
* 10:30 - 11:30 -

== Minutes ==

[@TBD 21-June-2013]

Ontology editors

Rliepins — Mon, 20 May 2013 19:52:53 GMT

← Older revision		Revision as of 19:52, 20 May 2013
Line 96:		Line 96:

	'''Available at:''' http://www.cambridgesemantics.com/products/anzo_for_excel		'''Available at:''' http://www.cambridgesemantics.com/products/anzo_for_excel
		+
		+	'''Unique strength:'''
		+
		+	'''Possible drawback:'''
		+
		+
		+	== [http://owlgred.lumii.lv/ OWLGrEd] ==
		+
		+	'''Description:''' a graphical ontology editor for OWL.
		+
		+	'''Available at:''' http://owlgred.lumii.lv/

	'''Unique strength:'''		'''Unique strength:'''

	'''Possible drawback:'''		'''Possible drawback:'''

Ontology Dowsing

Rliepins — Mon, 20 May 2013 19:48:52 GMT

Ontology Editors:

← Older revision		Revision as of 19:48, 20 May 2013
Line 89:		Line 89:
	* [http://www.cambridgesemantics.com/products/anzo_for_excel Anzo for Excel] will generate an initial ontology based on spreadsheet data and structure.		* [http://www.cambridgesemantics.com/products/anzo_for_excel Anzo for Excel] will generate an initial ontology based on spreadsheet data and structure.
	* [http://eulergui.sourceforge.net/ Euler GUI] is an editor for N3, RDF, OWL and other various other things.		* [http://eulergui.sourceforge.net/ Euler GUI] is an editor for N3, RDF, OWL and other various other things.
		+	* [http://owlgred.lumii.lv/ OWLGrEd] is a graphical ontology editor for OWL.

Headlights2013/Anniversaries

Msiderwicz — Mon, 20 May 2013 18:43:57 GMT

← Older revision		Revision as of 18:43, 20 May 2013
(7 intermediate revisions not shown)
Line 58:		Line 58:

	*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)		*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)
		+

	{\| class="mw_metadata"		{\| class="mw_metadata"
Line 63:		Line 64:
	! !! '''J''' !! '''F''' !! '''M''' !! '''A''' !! '''M''' !! '''J''' !! '''J''' !! '''A''' !! '''S''' !! '''O''' !! '''N''' !! '''D'''		! !! '''J''' !! '''F''' !! '''M''' !! '''A''' !! '''M''' !! '''J''' !! '''J''' !! '''A''' !! '''S''' !! '''O''' !! '''N''' !! '''D'''
	\|-		\|-
-	\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~ \|\| ~~text~~	+	\| W3C \|\| IntlCES (LasVegas) \|\| MWC(Spain) \|\| W3Conf? \|\| \|\| WWW2014(Korea) \|\| MobileAsiaExpo(Shanghai) \|\| \|\| \|\| \|\| \|\| \|\| Persons with Disabilities Day
	\|-		\|-
		+	\| WebFoundation \|\| \|\| \|\| TED (Vancouver) \|\| \|\| \|\| \|\| \|\| \|\| \|\| WebIndexForum \|\| \|\|
		+	\|-
		+	\| Tim \|\| Davos (Switz) \|\| \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text
	\|}		\|}
-
-	~~Tim: Davos (Switzerland), TED (Vancouver), WWW2014 (Korea), Web Index (London),~~
-	~~W3C: IntlCES (Las Vegas), MWC (Barcelona), W3Conf, GSMA Mobile World Asia (Shanghai)~~
-

	* CERN is celebrating its 60th anniversary in 2014. In April 2013, it began promoting 'the 20th anniversary of the Web' as it defines it. See the following info/links. NOTE: TimBL (through Dillon Mann at TWF) replied to Canada's national newspaper, ''The Globe and Mail'', that his definition of the Web's anniversary is different than CERN's (and his view is the anniversary year is 2014, not 2013).		* CERN is celebrating its 60th anniversary in 2014. In April 2013, it began promoting 'the 20th anniversary of the Web' as it defines it. See the following info/links. NOTE: TimBL (through Dillon Mann at TWF) replied to Canada's national newspaper, ''The Globe and Mail'', that his definition of the Web's anniversary is different than CERN's (and his view is the anniversary year is 2014, not 2013).
-

Headlights2013/Anniversaries

Denis — Mon, 20 May 2013 14:29:35 GMT

← Older revision		Revision as of 14:29, 20 May 2013
Line 59:		Line 59:
	*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)		*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)

-	{\| class="~~wikitable sortable~~"	+	{\| class="mw_metadata"
	\|-		\|-
-	! J !! F !! M !! A !! M !! J !! J !! A !! S !! O !! N !! D	+	! !! '''J''' !! '''F''' !! '''M''' !! '''A''' !! '''M''' !! '''J''' !! '''J''' !! '''A''' !! '''S''' !! '''O''' !! '''N''' !! '''D'''
		+	\|-
		+	\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text \|\| text
	\|-		\|-
	\|}		\|}

Headlights2013/Anniversaries

Msiderwicz — Mon, 20 May 2013 14:20:32 GMT

← Older revision		Revision as of 14:20, 20 May 2013
Line 58:		Line 58:

	*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)		*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)
		+
		+	{\| class="wikitable sortable"
		+	\|-
		+	! J !! F !! M !! A !! M !! J !! J !! A !! S !! O !! N !! D
		+	\|-
		+	\|}

	Tim: Davos (Switzerland), TED (Vancouver), WWW2014 (Korea), Web Index (London),		Tim: Davos (Switzerland), TED (Vancouver), WWW2014 (Korea), Web Index (London),

HTML/Publications

Plehegar — Mon, 20 May 2013 13:36:07 GMT

← Older revision		Revision as of 13:36, 20 May 2013
Line 123:		Line 123:
	\|		\|
	\|LC in Q4 2013, Cfc for update deadline is 04/04		\|LC in Q4 2013, Cfc for update deadline is 04/04
		+	\|-
		+	\|[http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html Encrypted Media Extensions]<br/>David Dorwin, Adrian Bateman, Mark Watson
		+	\|[http://www.w3.org/TR/encrypted-media/ 10 May 2013]
		+	\|FPWD
		+	\|
		+	* [http://www.w3.org/html/wg/tracker/products/19 tracker]
		+	* [https://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&product=HTML%20WG&component=Encrypted%20Media%20Extensions&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=3542 bugs]
		+	* [https://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG&component=Encrypted%20Media%20Extensions&priority=P3 file a bug]
		+	\| use [http://lists.w3.org/Archives/Public/public-html-media/ public-html-media]
		+	\|
		+	\|
	\|-		\|-
	\|[http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html Public Identifiers for entity resolution in XHTML]<br/>David Carlisle		\|[http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html Public Identifiers for entity resolution in XHTML]<br/>David Carlisle
Line 221:		Line 232:
	!Implementations		!Implementations
	!Plans		!Plans
-	\|-
-	~~\|[http://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html Encrypted Media Extensions]<br/>David Dorwin, Adrian Bateman, Mark Watson~~
-	\|
-	* [http://www.w3.org/html/wg/tracker/products/19 tracker]
-	* [https://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&product=HTML%20WG&component=Encrypted%20Media%20Extensions&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=3542 bugs]
-	* [https://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG&component=Encrypted%20Media%20Extensions&priority=P3 file a bug]
-	~~\| use [http://lists.w3.org/Archives/Public/public-html-media/ public-html-media]~~
-	\|
-	~~\|CfC did not pass. TF is looking at specific issues.~~
	\|-		\|-
	\|[https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/region.html#extension-of-the-html-texttrack-api Extension of the HTML TextTrack API]<br/>Silvia Pfeiffer		\|[https://dvcs.w3.org/hg/text-tracks/raw-file/default/608toVTT/region.html#extension-of-the-html-texttrack-api Extension of the HTML TextTrack API]<br/>Silvia Pfeiffer

Guide/GitHub

Npdoty — Mon, 20 May 2013 02:37:36 GMT

Using gh-pages:

New page

'''''This is an early draft, primarily authored by npdoty with notes from some W3C team members. Advice should be taken with grains of salt, to taste. Interpretation of W3C Process is best left to W3C legal counsel; interpretation of your Working Group's preferred workflow is best left to your group and its chairs, editors and team contact.'''''

----

[http://git-scm.com/ Git] is a popular, open-source distributed version control system, commonly used with [http://github.com GitHub] as a convenient central host of repositories, along with wiki documentation, pull request management and issue tracking. Several W3C groups are using GitHub infrastructure for specification and test authoring workflows. Below we include some suggested steps for getting started and answers to some frequently asked questions about using GitHub for W3C spec work.

== Questions ==

=== How do we ensure archiving of work done on GitHub? ===

As usual, publication of Working Drafts and Recommendations into w3.org/TR/ will be done by your Team Contact by copying snapshots which satisfy pubrules into the appropriate space, with W3C-guaranteed archiving.

A common use case would be for editors' drafts to be pointers to the head revision of a git repository's master branch as it appears on GitHub. Because Git itself decentralizes archiving of every change (every user clones all history), backups of version history of Git repositories should be straightforward. W3C systeam is considering automated W3C backups of repositories within the GitHub W3C organization.

Issues, wikis, pull requests and other GitHub-hosted workflows may not be as straightforward to archive, and your group members may need their own GitHub accounts to make effective use of those features. GitHub repository wikis are themselves Git repositories, so backup should be relatively simple.

=== When should we use Git/GitHub as opposed to w3.org-hosted CVS or Mercurial? ===

''tl;dr'' -- your version control system is up to you and your group, but GitHub is growing increasingly popular among our Working Groups.

W3C has no official recommendations of what version control system your Group should use. Your Group's editors will be the ones most often using the chosen version control system, and your Group's participants may have their own preferences regarding viewing version history or proposing changes. GitHub has some real advantages for specification and test authoring: histories of changes are all public; Git and GitHub are commonly used tools among developers; easy branching can facilitate sharing in-progress proposals, etc. With CVS editors and chairs can make direct changes to w3.org-hosted specifications, but setup also requires an SSH key setup process with w3.org systeam.

=== Should we use GitHub for issue management too? ===

Different groups have had different preferences on the best way to manage spec issues and code issues. Repositories that manage test code often use [https://github.com/blog/831-issues-2-0-the-next-generation GitHub issues] extensively or exclusively, and they may also work well for issue workflows where an editor's single commit will often be the resolution of an issue or pull requests are commonly used.

[https://www.w3.org/Bugs/Public/ Bugzilla] is often used by groups (like HTML WG) that have a relatively complex issue resolution process.

[http://www.w3.org/2005/06/tracker/ Tracker] is particularly useful for integration with IRC trackbot and connecting mailing list discussion of an issue. (Tracker also separately tracks "actions" which are not present in GitHub's workflow.)

=== How do we manage IPR with specs authored on GitHub? ===

As with any specification, text contributions with IPR implications should be included only from formal participants in a Working Group who have made the necessary IPR commitments. Likely only the Working Group's editors and chairs should have commit privileges to your group's specification repositories. Editors should take special care when accepting Pull Requests that the appropriate IPR commitments have been made (as you do with text suggestions made to the group mailing list); chairs and staff should make sure editors understand this.

== Getting started ==

=== Informal drafts in your personal account ===

Getting started individually doesn't require any approval process. Create an informal draft (using ReSpec makes it easy) by starting a new repository with your personal GitHub account. We recommend one repository per deliverable, in general.

You can link to ReSpec directly from your source. Use a <tt>gh-pages</tt> branch to let others easily see the rendered version of your draft hosted on the Web (more details below).

=== Hosting a repository within the W3C organization ===

1. Your Team Contact should become (if they're not already) a part of the [https://github.com/organizations/w3c/settings/owners Owners Team] of the W3C organization. (Ask any of the current owners directly, or ask on &sysreq. This is only for W3C Staff.)

2. Team Contact should create a new Team for the editors (and optionally, the chairs) who will be contributing to the Group's deliverables. Give each editor push and pull access.

3. Create a new repository for each deliverable (like a Recommendation-track spec), or fork an existing informal draft into the W3C organization. Add each such repository to the "Team" so that the editors/chairs all have commit access. Other participants in the Working Group can suggest changes by submitting pull requests (in fact, editors can do that too to make the process more clear, if desired), but not every contributor will be given direct commit access.

=== Using <tt>gh-pages</tt> ===

In specification development, the reader will most often want to read the spec itself, rather than the raw HTML source code. GitHub provides easy functionality for this via the <tt>gh-pages</tt> branch and [https://help.github.com/categories/20/articles GitHub Pages].

You have a couple of alternatives. Get rid of the default <tt>master</tt> branch:
* create a <tt>gh-pages</tt> branch
* delete the <tt>master</tt> branch
* commit to the <tt>gh-pages</tt> branch, or merge feature branches into <tt>gh-pages</tt>

The [http://tobie.github.io/specs-on-github/ Using GitHub for Spec Work] guide describes how to get started using this method and starting with a template and ReSpec. Name the draft file <tt>index.html</tt> to simplify your URLs.

Alternatively, you can continue to use the <tt>master</tt> branch for development and writing but [http://concord-consortium.github.io/developer-notes/automating-gh-pages-integration.html use a post-commit hook] to simultaneously push those changes to <tt>gh-pages</tt>.

Testing/Test Framework TF/WebDriver

Tobie — Sun, 19 May 2013 20:38:22 GMT

← Older revision		Revision as of 20:38, 19 May 2013
Line 13:		Line 13:
	* Desktop and FirefoxOS https://developer.mozilla.org/en-US/docs/Marionette		* Desktop and FirefoxOS https://developer.mozilla.org/en-US/docs/Marionette
	* Fennec impl stalled: https://bugzilla.mozilla.org/show_bug.cgi?id=787203 not being worked on actively and is blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=787280		* Fennec impl stalled: https://bugzilla.mozilla.org/show_bug.cgi?id=787203 not being worked on actively and is blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=787280
		+
		+
		+	== Using WebDriver to Test Devices ==
		+	(Notes from Simon Stewart)
		+
		+	=== Problem: ===
		+
		+	We want to host a set of canonical webdriver tests on a publicly addressable server and run these against a device that may not be publicly addressable.
		+
		+	=== What We Know: ===
		+
		+	* The server hosting the tests has a functioning web server.
		+	* All WebDriver implementations are required to have an implementation of the JSON over HTTP protocol listed in the W3C WebDriver spec.
		+	* The device being tested can access the Web.
		+	* The device being tested is behind a corporate firewall: it cannot be reached by the server.
		+	* The device adheres to the WebDriver spec.
		+	* It can be assumed that the people running the tests (the testers for wont of a better word) are minimally technical.
		+	* The tests hosted on the server are written using the language bindings of WebDriver and therefore represent the "local end" mentioned in the spec.
		+
		+	=== Options: ===
		+
		+	The obvious option, of having the tests run on the server and connecting to the device can't be followed because of the firewall. The following may be considered:
		+
		+	==== Option 1: ====
		+
		+	A simple "reflector" is created. This would be hosted on the same network as the device and would be implemented as a basic HTTP server. In order to run the tests, the following steps would be required:
		+
		+	# The device's WebDriver mode would be enabled.
		+	# The testers would load the main page of the reflector. This would be a form, allowing the tester to input the URL used by the device for it's WebDriver JSON/HTTP implementation.
		+	# The reflector opens an HTTP connection to the server, asking to create a new testing session.
		+	# The server responds with the first WebDriver Command to execute and a key to identify this session with. This causes the HTTP connection to close. The reflector forwards the Command to the device, translating it to the JSON/HTTP protocol as necessary.
		+	# The device sends the WebDriver Response to the reflector, which opens a new HTTP request to the server and sends the Response and key back as the payload of that request.
		+	# The process of reflecting continues until the end of the tests.
		+
		+	==== Option 2: ====
		+
		+	The test scripts are hosted on the server but are actually run on the same network as the device, with results being uploaded to the server. The following steps would be required:
		+
		+	# The testers set up a machine on the same network as the device and install python, easy_install and/or pip, as well as virtualenv
		+	# The device's WebDriver mode would be enabled.
		+	# The testers run: `curl -L http://server/runtests \| DEVICE_URL=http://address.of.device/webdriver/url python`
		+	# This would execute the downloaded script, which would:
		+	## Create a new virtualenv to use for the remaining steps
		+	## Install local end bindings for webdriver (probably the python selenium libs)
		+	## Download the full suite of tests from the server via HTTP(S)
		+	## Run each of those tests
		+	## (Optionally) Upload the results to the server.
		+
		+	=== Problems Not Considered: ===
		+
		+	What happens when the device is on a 3G/LTE network and is otherwise unreachable (that is, hosting a simple server or reflector on the same network is extremely hard to do) There are commercial and OSS tools that already do something similar, so it's possible.
		+
		+	The WebDriver JSON/HTTP protocol is very chatty. If we lose a single HTTP request or response then the entire test becomes invalid. We could mitigate this by using persistent HTTP connections or another technology entirely (websockets, perhaps?)

Headlights2013/Anniversaries

Msiderwicz — Fri, 17 May 2013 19:50:49 GMT

← Older revision		Revision as of 19:50, 17 May 2013
Line 56:		Line 56:

	*Leverage existing opportunities planned for 2014 to gain efficiencies. For example, consider ways to integrate celebration with existing global events or themes:		*Leverage existing opportunities planned for 2014 to gain efficiencies. For example, consider ways to integrate celebration with existing global events or themes:
		+
		+	*May 2013 task force suggestion: let's leverage existing W3C/Tim/TWF events/activities first in 2014 with bottom-up approach (anniversary theme/logo/speaker briefing/etc.)
		+
		+	Tim: Davos (Switzerland), TED (Vancouver), WWW2014 (Korea), Web Index (London),
		+	W3C: IntlCES (Las Vegas), MWC (Barcelona), W3Conf, GSMA Mobile World Asia (Shanghai)

Webapps/Submitting tests

Abarsto — Fri, 17 May 2013 17:00:40 GMT

Testing Roles:

← Older revision		Revision as of 17:00, 17 May 2013
(3 intermediate revisions not shown)
Line 82:		Line 82:

	^1 If you are a member of WebApps, and would like to be able to merge Pull Requests after a successful review, ask one of the W3C Staff members to add your GitHub account into the ''Team'' group. Good candidates are Robin (darobin), Tobie (tobie) and Mike (MikeSmith).		^1 If you are a member of WebApps, and would like to be able to merge Pull Requests after a successful review, ask one of the W3C Staff members to add your GitHub account into the ''Team'' group. Good candidates are Robin (darobin), Tobie (tobie) and Mike (MikeSmith).
		+
		+	==Testing ''Roles''==
		+
		+	Information in this document refers to the following ''roles'':
		+
		+	* Contributor / Submitter - someone that contributes one or more test cases
		+
		+	* '''Test Facilitator''' - the person(s) responsible for maintaining a specification's test suite, including updating test cases, making sure Pull Requests are reviewed, etc. Normally, this role is assumed to the specification's Editor(s). A Test Facilitator will be designated as the ''Default Assignee'' for the test suite's bug component in WebApp's [http://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG Bugzilla database]. Test Facilitators are expected to work with Contributors e.g. to resolve quality issues, to eliminate redundant/overlapping asserts, etc.
		+
		+	* '''Testing Coordinator''' - the person responsible for coordinating all of WebApps' testing efforts. By default, this role is taken by a WG Chair, a WebApps ''Team Contact'' or a member of the WG. (In practice, this role may be shared by more than one person.)
		+
		+	* '''WebApps' Testing Group''' - WG members subscribed to the WG's <code>[http://lists.w3.org/Archives/Public/public-webapps-testsuite/ public-webapps-testsuite]</code> list
		+
		+	==Test Suite Status==
		+
		+	The easiest way to determine the status of a spec's test suite is to simply ask on the <code>[mailto:public-webapps-testsuite@w3.org public-webapps-testsuite@w3.org]</code> mai list. Additionally, some test suite status information including the spec's Test Facilitator is available in WebApps [http://www.w3.org/2008/webapps/wiki/PubStatus Publication Status] document.
		+
		+	== How to Report a Test Case Bug ==
		+
		+	A bug report for a test case can be reported via any of the following:
		+
		+	* An e-mail to the <code>[mailto:public-webapps-testsuite@w3.org public-webapps-testsuite@w3.org]</code> mai list
		+	* Make a Pull Request with a patch to fix the bug
		+	* File a Bugzilla bug against the appropriate test suite component in [http://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebAppsWG WebApps' Bugzilla database]. Please identify the test case(s) that has a bug and clearly describe the bug. (If you do not have write access to the bug database, send an e-mail to the list above).

TAG/Planning/May-2013-F2F

Avankest — Fri, 17 May 2013 08:51:23 GMT

Proposed Topics: as discussed in http://www.w3.org/2001/tag/2013/05/02-minutes.html

← Older revision		Revision as of 08:51, 17 May 2013
Line 18:		Line 18:
	* Capability URLs ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])		* Capability URLs ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])
	* Distributed Web Architecture ([http://w3ctag.github.io/presentations/reveal/distributed-web.html slides in development])		* Distributed Web Architecture ([http://w3ctag.github.io/presentations/reveal/distributed-web.html slides in development])
		+	* SysApps and the web
	* Persistence		* Persistence
	* Idiomatic API design		* Idiomatic API design

Testing/Test Management TF/HTML5 Test Coverage Analysis

Bh526r — Thu, 16 May 2013 22:41:01 GMT

← Older revision		Revision as of 22:41, 16 May 2013
(2 intermediate revisions not shown)
Line 188:		Line 188:
	\| HTML Testing TF \|\|\|\|		\| HTML Testing TF \|\|\|\|
	\|-		\|-
-	\| style="padding-left: 2em" \| 2.2.2 Dependencies \|\|\|~~\|\|\|~~\|\|\|\|	+	\| style="padding-left: 2em" \| 2.2.2 Dependencies
		+	\| User-Agent
		+	\|
		+	* Implementations that support the XHTML syntax must support some version of XML, as well as its corresponding namespaces specification, because that syntax uses an XML serialization with namespaces
		+	* Implementations must support DOM Core and the events defined in DOM Events
		+	* Implementations must support the features that are defined as extensions to the DOM Core:
		+	** 15 Interfaces: Attr, Comment, DOMImplementation, Document, DocumentFragment, DocumentType, DOMException, Element, Node, NodeList, ProcessingInstruction, Text, HTMLCollection (and the terms collections and represented by the collection), DOMTokenList, DOMSettableTokenList
		+	** 6 Methods: createDocument(), createHTMLDocument(), createElement(), createElementNS(), getElementById(), and insertBefore()
		+	** 10 attributes: ownerDocument, childNodes, localName, parentNode, namespaceURI, tagName, id, textContent, target, isTrusted
		+	** 4 Algorithms: "insert", "append", and "replace" algorithms for nodes, "clone" a Node and the concept of cloning steps used by that algorithm,
		+	** Event related: "Event" and "EventTarget" interfaces, "EventInit" dictionary, the "type" of an event, the "event listeners" associated with an "EventTarget"
		+	** The encoding and content-type of a document
		+	** The distinction between XML documents and HTML documents
		+	** "quirks" mode, "limited-quirks" mode, and "no-quirks" mode
		+	** The concept of "base URL change steps" and the definition of what happens when an element is affected by a "base URL change"
		+	** The concept of an element's unique identifier (ID)
		+	** The concept of a DOM "range", and the terms "start", "end", and "boundary point" as applied to "ranges"
		+	** "MutationObserver" interface, the concept of "MutationObserver" scripting environment and the "invoke MutationObserver objects" algorithm
		+	** 21 DOMExceptions: IndexSizeError, HierarchyRequestError, WrongDocumentError, InvalidCharacterError, NoModificationAllowedError, NotFoundError, NotSupportedError, InvalidStateError, SyntaxError, InvalidModificationError, NamespaceError, InvalidAccessError, TypeMismatchError, SecurityError, NetworkError, AbortError, URLMismatchError, QuotaExceededError, TimeoutError, InvalidNodeTypeError, DataCloneError
		+	** "MouseEvent" interface and related attributes: screenX, screenY, clientX, clientY, ctrlKey, shiftKey, altKey, metaKey, button, buttons, relatedTarget
		+	** "UIEvent" interface and related attributes: view, detail
		+	** "click" event
		+	** DOM Parsing and Serialization: innerHTML, outerHTML, insertAdjacentHTML
		+	* Implementations must support File API "Blob", "File" and "FileList", and File System API "File Callback"
		+	* Implementations must support XmlHttpRequest
		+	* Implementations must support "ArrayBuffer" interface and underlying concepts, and Uint8ClampedArray interface from the Typed Array Specification
		+	* Implementations must support JavaScript (ECMA262)
		+	* Implementations must support the Media Queries language
		+	* Implementations may support WebVTT as a text track format for subtitles, captions, chapter titles, metadata, etc, for media resources
		+	* Implementations must support the semantics of URLs defined in the URI specifications, as well as the semantics of IDNA domain names defined in the Internationalizing Domain Names in Applications (IDNA) specification. [RFC3986] [RFC3987] [RFC3490]
		+	* Implementations must support the cookies
		+	* Implementations must support CORS
		+	\| Bin Hu, AT&T \|\|\|\|
	\|-		\|-
-	\| style="padding-left: 2em" \| 2.2.3 Extensibility \|\|\|~~\|\|\|~~\|\|\|\|	+	\| style="padding-left: 2em" \| 2.2.3 Extensibility
		+	\| User-Agent
		+	\|
		+	\|Bin Hu, AT&T \|\|\|\|
	\|-		\|-
-	\| 2.3 Case-sensitivity and string comparison \|\|\|~~\|\|\|~~\|\|\|\|	+	\| 2.3 Case-sensitivity and string comparison
		+	\| User-Agent
		+	\|
		+	\|Bin Hu, AT&T \|\|\|\|
	\|-		\|-
-	\| 2.4 UTF-8 \|\|\|~~\|\|\|~~\|\|\|\|	+	\| 2.4 UTF-8
		+	\| User-Agent
		+	\|
		+	\|Bin Hu, AT&T \|\|\|\|
	\|-		\|-
	\| 2.5 Common microsyntaxes \|\|\|\|\|\|\|\|\|\|		\| 2.5 Common microsyntaxes \|\|\|\|\|\|\|\|\|\|

TAG/Planning/May-2013-F2F

Jenit — Thu, 16 May 2013 19:08:24 GMT

Proposed Topics: separated topics of capability URLs & distributed web architecture

← Older revision		Revision as of 19:08, 16 May 2013
Line 16:		Line 16:
	* Overall TAG goals and priorities		* Overall TAG goals and priorities
	* HTTPbis		* HTTPbis
-	* Capability URLs ~~and distributed Web Architecture~~ ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])	+	* Capability URLs ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])
		+	* Distributed Web Architecture ([http://w3ctag.github.io/presentations/reveal/distributed-web.html slides in development])
	* Persistence		* Persistence
	* Idiomatic API design		* Idiomatic API design

Headlights2013/Anniversaries

Msiderwicz — Thu, 16 May 2013 19:00:45 GMT

← Older revision		Revision as of 19:00, 16 May 2013
(3 intermediate revisions not shown)
Line 94:		Line 94:

	Mobile World Congress, Barcelona, Spain (Feb).		Mobile World Congress, Barcelona, Spain (Feb).
		+
		+	Winter Olympics, Sochi, Russia (AT&T, GM among lead advertisers)

	2014 Year of the Horse in China (all year).		2014 Year of the Horse in China (all year).
Line 112:		Line 114:

	TPAC2014		TPAC2014
		+
		+	International Day of Persons with Disabilities, (9-Dec.?)

	Also, Amy notes that each year, September 22, [http://onewebday.org One Web Day] does a celebration with videos, tshirts, badges, etc.		Also, Amy notes that each year, September 22, [http://onewebday.org One Web Day] does a celebration with videos, tshirts, badges, etc.

TAG/Planning/May-2013-F2F

Plinss — Thu, 16 May 2013 18:29:47 GMT

← Older revision		Revision as of 18:29, 16 May 2013
Line 11:		Line 11:

	=== Proposed Topics ===		=== Proposed Topics ===
		+	* TAG Operations
		+	** Interaction with other WGs (TAG Ambassador?)
		+	** Interaction with developer community
		+	* Overall TAG goals and priorities
	* HTTPbis		* HTTPbis
	* Capability URLs and distributed Web Architecture ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])		* Capability URLs and distributed Web Architecture ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])
	* Persistence		* Persistence
	* Idiomatic API design		* Idiomatic API design

TAG/Planning

Plinss — Thu, 16 May 2013 18:22:02 GMT

← Older revision		Revision as of 18:22, 16 May 2013
Line 5:		Line 5:
	=== Upcoming Meetings ===		=== Upcoming Meetings ===
	==== 2013 ====		==== 2013 ====
-	* [[TAG/~~planning~~/May-2013-F2F\|May 2013 F2F - London]]	+	* [[TAG/Planning/May-2013-F2F\|May 2013 F2F - London]]

TAG

Plinss — Thu, 16 May 2013 18:20:11 GMT

← Older revision		Revision as of 18:20, 16 May 2013
Line 1:		Line 1:
	Intended for use by the [http://www.w3.org/2001/tag/ W3C Technical Architecture Group]		Intended for use by the [http://www.w3.org/2001/tag/ W3C Technical Architecture Group]
		+
		+
		+	[[TAG/Planning\|Meeting Planning]]

TAG/planning/May-2013-F2F

Plinss — Thu, 16 May 2013 18:15:06 GMT

moved [[TAG/planning/May-2013-F2F]] to [[TAG/Planning/May-2013-F2F]]

New page

TAG/planning

Plinss — Thu, 16 May 2013 18:15:06 GMT

moved [[TAG/planning]] to [[TAG/Planning]]

New page

TAG/planning

Plinss — Thu, 16 May 2013 18:14:39 GMT

← Older revision		Revision as of 18:14, 16 May 2013
Line 5:		Line 5:
	=== Upcoming Meetings ===		=== Upcoming Meetings ===
	==== 2013 ====		==== 2013 ====
-	* [[May-2013-F2F\|May 2013 F2F - London]]	+	* [[TAG/planning/May-2013-F2F\|May 2013 F2F - London]]

TAG/planning/May-2013-F2F

Plinss — Thu, 16 May 2013 18:14:14 GMT

Created

New page

= May 2013 F2F - London =

When: May 29-31, 2013

Where: London, UK
* Meeting location: Mozilla London

Host: Mozilla

== Agenda ==

=== Proposed Topics ===
* HTTPbis
* Capability URLs and distributed Web Architecture ([http://w3ctag.github.io/presentations/reveal/capability-urls.html slides])
* Persistence
* Idiomatic API design