17:01:08 <RRSAgent> RRSAgent has joined #webperf
17:01:08 <RRSAgent> logging to http://www.w3.org/2013/07/17-webperf-irc
17:01:09 <Alois> Alois has joined #webperf
17:01:09 <simonjam> simonjam has joined #webperf
17:01:10 <trackbot> RRSAgent, make logs world
17:01:11 <Zakim> Zakim has joined #webperf
17:01:12 <trackbot> Zakim, this will be WPWG
17:01:12 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
17:01:13 <trackbot> Meeting: Web Performance Working Group Teleconference
17:01:14 <trackbot> Date: 17 July 2013
17:01:46 <JatinderMann> present+ DanAustin
17:01:50 <JatinderMann> present+ JatinderMann
17:02:02 <JatinderMann> present+ Alois
17:02:36 <JatinderMann> present+ simonjam
17:03:47 <Ganesh> Ganesh has joined #webperf
17:04:28 <JatinderMann> Topic: Test Cases
17:04:34 <JatinderMann> present+ Ganesh
17:04:54 <JatinderMann> Jatinder: http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTimingL2/test_navigation_timing2_objects.html
17:05:02 <JatinderMann> Jatinder: This test case tests basic Navigation Timing L2 support by testing if the performance.getEntries()[0], performance.getEntriesByName('document'), and performance.getEntriesByType('navigation') return a PerformanceNavigationTiming object
17:05:13 <JatinderMann> Jatinder: 	http://w3c-test.org/webperf/tests/submission/Microsoft/PerformanceTimeline/test_performance_timeline_functions.html
17:05:22 <JatinderMann> Jatinder: This test case tests if the performance.getEntries(), performance.getEntriesByName(), and performance.getEntriesByType() functions are supported.
17:05:56 <JatinderMann> Jatinder:  There was also the question on when we are going to move to using  https://github.com/w3c/web-platform-tests? I know Philippe took an action to find out change in process.
17:06:19 <JatinderMann> James: Should we continue to using the old respository?
17:09:34 <JatinderMann> Jatinder: I think we should continue using the old process until we change the process.
17:09:53 <JatinderMann> Topic: Web Workers in Resource Timing L2
17:12:25 <JatinderMann> Jatinder: For web workers, we need to decide whether the resources downloaded by the web worker should show up in the main document associated with the worker, or only when the buffer is requested from the web worker context though the performance.getEntries() methods. The opposite is also interesting, should the resources used in the main document by shown when calling performance.getEntries() methods from the worker context? Sounds like an in[CUT]
17:13:21 <JatinderMann> Dan: The main idea we were thinking about when this was raised in HTML WG, was to be able to download the timing data in the main page through a background thread via the worker.
17:15:31 <JatinderMann> Jatinder: The real world use case is to JSON.stringify(performance.getEntries()) to send the data to the server and do analysis there.
17:16:03 <JatinderMann> Jatinder: So the option is either JSON from the main document to get all data, or JSON from the main document and all the workers
17:35:43 <JatinderMann> Jatinder: We should keep in mind that analystics will just be a single script added to a web page. The analytics would want to have a view of all the resources used, without asking each worker (which isn't possible for the analytics).
17:36:07 <JatinderMann> James: For Shared workers, we would definitely need to keep the context seperated, as it doesn't have a view into the main document.
17:37:00 <JatinderMann> Jatinder: Our options might be to either completely seperate workers from the documents, or to keep dedicated workers connected with the main document, and just have the shared worker seperate. I think each has an interesting case, and we should think about it some more before deciding.
17:37:28 <JatinderMann> Jatinder: There is also the point that High Resolution Time defines the dedicated worker's time origin as the same as the main document, but the shared worker is the time of creation of the shared worker.
17:37:51 <JatinderMann> Dan: Yes, let's think about the different customer scenarios more carefully before closing on the direction that we want to go in.
17:38:02 <JatinderMann> Topic: FPWDs of New Specs
17:38:49 <JatinderMann> Jatinder: At this point, we have discussed most of the new charter specs in the working group and have put together drafts of most of the specs. I want to start cleaning up all of the specs and start publishing them as FPWD. Let's spend the next couple of weeks reviewing open issues and closing up on the drafts.
17:39:38 <JatinderMann> Dan: I'd be interesting in hearing from Philippe what the process is for exclusion from discussion - I believe its at the FPWD point that we can choose to exclude ourselves or not.
17:40:02 <JatinderMann> Dan: I think once all of the drafts have been cleaned up, I would like to see them go to FPWD.
17:40:20 <JatinderMann> Dan: What about the task of putting together a draft of best practices?
17:40:47 <JatinderMann> Jatinder: I think we are really just looking for a volunteer to put together a draft. Once we have a draft the working group can review.
17:40:54 <JatinderMann> Dan: I will volunteer to put together a draft.
17:41:27 <JatinderMann> Jatinder: Let me know if you need any help in putting together a Note with this information. We should loop in Philippe as well to close on what kind of document this will be.
17:41:38 <JatinderMann> rrsagent, generate minutes
17:41:38 <RRSAgent> I have made the request to generate http://www.w3.org/2013/07/17-webperf-minutes.html JatinderMann
19:06:33 <Zakim> Zakim has left #webperf