W3C | TAG | Previous teleconference: 21st May 2007. | Next teleconference: 11th June 2007.

TAG face-to-face meeting, 30 May-1 June, Googleplex, Mountain View, CA, USA

photo credit: Norm Walsh (other sizes)

Nearby: issues list - findings - www-tag archive - tag archive - pending actions

Meeting at a glance

1. Logistics

(also separate Logistics page)

2. Recommended readings

• TAG Charter
• Webarch
• For URNsAndRegistries-50
  • draft finding
•  For XMLFunctions-34 and Elaborated Infoset
  •  elaboratedInfoset
  • The Interpretation of XML documents a DesignIssues note on XML Functions from TimBL
• Dereferencing HTTP URIs draft finding
• For XMLVersioning-41
  • Revised Versioning draft findings: terminology, strategies, XML Languages
  • HTML Design Principles (Proposed)
• For namespaceDocument-8
  •  Associating Resources with Namespaces
• For Self Describing Web
  • Revised Draft finding (updated 24 May 2007; the stable URI for the version to be reviewed is http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2007-05-24.html.)

3. Agenda

3.1. Administrative (<30min)

1. Convene: take roll, review and agree agenda
2. Regrets:DaveO (Wed am), Norm (Fri am)
3. Appoint: scribes for the two days
   Approve: minutes of previous teleconference (21 May.)
4. Next f2f: 17-18th September, University of Southampton, Hampshire, UK.
   • Continue informally into a 3rd Day? Nearby facilities?
5. Nov-Dec F2F and Tech Plenary
   • Separate F2F or combined with TP?
   • Liason meetings with other WGs. (who's likely to be there with availability to meet with other WGs).

3.2 URNsAndRegistries-50

• Resolution to the two parts of the draft finding on URNsAndRegistries-50

• draft finding
• Review from Stuart

3.3 XMLFunctions-34 and Elaborated Infoset

• Agree the scope of the issue. Our previous discussion in Boston foundered on topics such a "quoting" (early/late evaluation) and whether expression in the form of Infoset manipulation served as adequate proxy for the 'meaning' of an elaborated document.

• Elaborated Infosets from Henry: message+thread and draft
• The Interpretation of XML documents  from TimBL

3.4 Review of "Dereferencing HTTP URIs" draft finding.

Objectives

• Review draft finding on "Dereferencing HTTP URIs"
• Determine next steps toward TAG approval/publication

Resources

• Outstanding action items.

3.5 Versioning

3.5.1 Review of Draft Findings

Objectives:

• Review what we are trying to achieve wrt to our issue XMLVersioning-41
  • How do we move beyond drafts toward consensus?
• Review part1 derived draft findings - terminology, strategies

Resources:s:

• Outstanding action items.
• Current versioning draft findings terminology, strategies, XML Languages
• Review Comments (on prior versions part1) from Rhys and Stuart.
• Review comments on  terminology from DanC
• Other recent reviews?

3.5.2 Version Identification

Objectives

• Reconsider current advice in Webarch
• Contast with advice in draft findings.
• Articulate positive and negative use cases for version identification (in instances and in language defns)

Resources

• Question from DanC, "should CSS, HTML, etc. documents bear version information?"
• Current versioning draft findings terminology, strategies, XML Languages
• HTML Design Principles (Proposed)

3.5.3 Versioning XML Languages

Objectives

• Review revised part2 draft finding XML Languages

Resources

• Revise "part2" draft finding  XML Languages
• Review Comments (on prior versions  part2) from Norm

3.5.4 Versioning: Application of Finding to HTML (and TagSoup)

Objectives

• Taking HTML (past, present and future) as a test case: Apply the model and guidance offered in our draft findings.
• Where appropriate: generate consensus advice on versioning for HTML-WG.

Resources

3.6. Purpose and Direction

Objectives

To develop a shared understanding of:

• What we do; for whom; what they want/need from us.
• How we contribute to the objectives of the Consortium
• Our values wrt to how we communicate with the community (responding to requests and feedback, web presence, publications...).
• Critical objectives, measures and plans (and processes - are they working?)

Resources

• TAG homepage, charter, Issues List, findings.
• TAG Survey article by Henry

3.7 Issue namespaceDocument-8

Objectives

• Agree on what we want to accomplish
• Agree on the modeling approach
• Agree on next steps

Resources

• Outstanding action items
• Draft Finding Associating Resources with Namespaces

3.8 Self Describing Web

Objectives

• Review revised draft from Noah (@@ink TBD)
• Agree next steps.

Resources

• Agenda Proposal (previous F2F) from Noah and Draft finding as revised on 24 May 2007.
• Related Issues:
  • Media Type issues: w3cMediaType-1, w3cMediaType-2, nsMediaType-3, uriMediaType-9, mediaTypeManagement-45
  • Metadata issues: namespaceDocument-8, siteData-36.
  • Mixed Language issues: RDFinHTML-35, mixedUIXMLNamespace-33, xmlFunctions-34
  • Miscellaneous issues: the self-describing Web has been until now tracked under the catch-all issue ultimateQuestion-42.

3.9 Naming and Virtual Worlds.

Objectives

• Consider whether there are issue of Web Architecture in the collision of virtual worlds with each other and the real world.

Resources

• Telecon discussion from 30th April
• The Croquet Consortium
• SLurl 2nd Life URLs
  • "Just link to SLurl.com with a Second Life location:
    http://slurl.com/secondlife/<region>/<x-coordinate>/<y-coordinate>/<z-coordinate>/
    So, for example, to link to Ahern(50,50,50), you would enter the following:
    http://slurl.com/secondlife/Ahern/50/50/50 <-- The final z-coordinate is optional."
• Others?