Agenda for TAG face-to-face meeting in Vancouver

21-23 July 2003

Previous meeting: 14 July 2003 teleconf

Reading List

1. RDDL draft
2. The use of Metadata in URIs and mail thread
3. contentPresentation-26 Draft Finding
4. David Orchard's description (3rd version) of abstractComponentRefs-37
5. 16 July 2003 Editor's Draft of Arch Doc

Summary Agenda (at a Glance)

Detailed Agenda

Monday 21st July

13:00-15:00

1. Administrative (30 min.)

1. Roll Call, Scribe
2. Accept minutes of previous call
3. Agree agenda - please review ahead of the meeting and request changes on tag@w3.org
4. Next Telcon: proposed 28th July 2003 (Regrets: SW)
5. November F2F (check on dates and local arrangements).

2. nameSpaceDocument-8 and RDDL (90 min.)

Objectives:

1. To affirm TAG intention to progress RDDL as a TAG sponsored W3C Note.
2. To review and resolve necessary chances to the current RDDL draft.
3. To resolve RDDL to RDF mapping issue.
4. To resolve nameSpaceDocument-8 (it has been with us since 14th January 2002)

• namespaceDocument-8
  • Action TB 2003/04/07: Prepare RDDL Note. Include in status section that there is TAG consensus that RDDL is a suitable format for representations of an XML namespace. Clean up messy section 4 of RDDL draft and investigate and publish a canonical mapping to RDF. See TB's 1 June version.
  • Action PC 2003/04/07: Prepare finding to answer this issue, pointing to the RDDL Note. See comments from Paul regarding TB theses.
  • Refer to draft TAG opinion from Tim Bray on the use of URNs for namespace names.
    • RF: Folks assume that because the specs say so, URNs will be persisitent. But persistence is a function of institutional commitment and frequency of use.

15:00-15:30 Break
15:30-17:30

3. Findings in Progress (90 min. with 15 min. break)

Objectives:

1. Develop consensus around direction and content of these findings.
2. Next steps and actions toward resolution of related issues.
3. Consider status wrt possible LC on webarch.

• metadataInURI-31: 8 July 2003 draft of "The use of Metadata in URIs"
  • Action DO 2003/07/07: Send rationale about why WSDL WG wants to peek inside the URI.
  • See also TB email on Apple Music Store and use of URI schemes instead of headers
• abstractComponentRefs-37
  • See issue description from David Orchard. Next steps?
  • Action DO 2003/06/23: Point Jonathan Marsh at options. Ask them for their analysis.
• contentPresentation-26: Action CL 2003/06/02: Make available a draft finding on content/presentation.

4. Issues identified for resolution before Last Call (see list) (30 min)

Objectives:

1. Discussion of errorHandling-20 (other 3 issues expected to either have been resolved or relevant draft finding discussed).

• whenToUseGet-7 (discussion/resolution likely in advance of F2F)
• errorHandling-20  (Maybe for LC; Discussion expected)
  • Action CL 2003/02/06: Write a draft finding on the topic of (1) early/late detection of errors (2) late/early binding (3) robustness (4) definition of errors (5) recovery once error has been signaled. Due first week of March.
• contentTypeOverride-24 (resolution likely in advance of F2F)
• metadataInURI-31 (discussed above).
• abstractComponentRefs-37(discussed above).

Tuesday 22nd July

09:00-10:30

5. Architecture Document

16 July 2003 Editor's Draft of Arch Doc

Objectives:

1. To identify and action any essential changes to the Architecture Document in advance of issuing a Last Call.
2. To resolve a plan for publishing an LC WD of webarch
3. To discuss other process issues:
   1. Meaning of "normative reference" in this document?
   2. What does a CR period look like for this document?

Outstanding Actions

• Action RF 2003/06/02: Rewrite section 5. Section 5 is expected to be short.
• Action IJ 2003/06/16: Attempt to incorporate relevant bits of "Conversations and State" into section to be produced by RF.
• Action SW 2003/07/07: Try to get TimBL to sign off on Paul's text. If SW able to reach TBL, SW/TBL send to AC as co-chairs. If not, have IJ send on behalf of TAG.
• Action TBL 2003/07/14: Suggest changes to section about extensibility related to "when to tunnel".
• Completed action TBL 2003/07/14: Send email to AC about TAG expectations re: arch doc (Deadline 14 July)

Discussion

• Sections 2.3 and 3.2.1
• State of whenToUseGet-7, errorHandling-20, contentTypeOverride-24, and metadataInURI-31 (see list of LC and discussion issues for July F2F).
• Open Discussion (technical)
  • Summary of changes/actions.
• LC Decision and Planning (administrative)
  • Unresolved Issues.
  • Reviews sought.
  • Review period.

10:30-11:00 Break
11:00-12:30

6. Architecture Document (continued)

(see above)

12:30-14:00 Lunch
14:00-15:30

7. Identifiers (URIEquivalence-15 , IRIEverywhere-27)

Objectives:

1. Open discussion of issues surrounding URI/IRI comparisons and equivalences (relates to issues #15 and #27).

• URIEquivalence-15
  • SW proposal: Track RFC2396bis where Tim Bray text has been integrated. Comment within the IETF process. Move this issue to pending state.
• IRIEverywhere-27
  • Action CL 2003/04/07: Revised position statement on use of IRIs.
  • Action TBL 2003/04/28: Explain how existing specifications that handle IRIs are inconsistent. TBL draft not yet available on www-tag.
  • See TB's proposed step forward on IRI 27.

15:30-16:00 Break
16:00-17:30

8. Qnames, fragments, and media types (rdfmsQnameUriMapping-6, fragmentInXML-28, abstractComponentRefs-37, putMediaType-38)

[Clustering of issues #6, #28, #37 and #38 requested by DanC - Dan, can you explain the motivation to cluster? Thx.]

Objectives:

1. Converge or refactor issues around common basis?
2. Next steps and actions toward resolution.

• rdfmsQnameUriMapping-6
  • Action DC 2003/02/06: Propose TAG response to XML Schema desideratum (RQ-23).
• fragmentInXML-28 : Use of fragment identifiers in XML.
  1. Connection to content negotiation?
  2. Connection to opacity of URIs?
  3. No actions associated / no owner.
• abstractComponentRefs-37(discussed above).
• putMediaType-38

Wednesday 23rd July

09:00-10:15

9. New and other Issues requested for discussion. (mixedUIXMLNamespace-33, RDFinXHTML-35, siteData-36 plus possible new issues) (75 min)

Objectives

1. Initiate discussion and actions on substantially undiscussed issues.
2. Identify next steps and actions.

Existing Issues:

• mixedUIXMLNamespace-33
• RDFinXHTML-35
• siteData-36
  • Action TBL 2003/02/24 : Summarize siteData-36

Possible New Issues (this list will be reviewed ahead of the F2F at the 14th July telcon)

• Visibility of Web Services, raised by Mark Baker
• Character model conformance, raised by TBL
• Meaning of URIs in RDF documents, raised by TBL

10:15-10:45 Break
10:45-12:00

10. New and other Issues requested for discussion (continued) (60 min)

(see above)

11. Wrap up and adjourn. (15 min)

12:00-13:30 Lunch
13:30-15:00

12.  Informal continuation.

[Some TAG members need to depart at 12:00]

Informal discussion of any matters of interest.

Items not scheduled for discussion at F2F

This is a 'dumping' ground for elements of our standing agenda that I have not propagated to the F2F agenda, along with some supporting rationale.

Findings in Progress

[Expect contentTypeOverride-24 and whenToUseGet-7 to have made significant progress ahead of F2F. xmlIDSemantics-32 has a stable and mature draft finding and XML Core WG are working toward a resolution of this issue.]

• contentTypeOverride-24: 9 July 2003 draft of Client handling of MIME headers
  1. Action CL, NW 2003/06/30: Read the draft finding by 7 July. NW Done
• 9 July 2003 draft of URIs, Addressability, and the use of HTTP GET and POST
  • whenToUseGet-7
    • Subsumed action DO 2003/07/07: Send text that DO and Noah M. can agree to to tag@w3.org. (DO should verify 9 July text)
• xmlIDSemantics-32:
  1. Chris Lilley draft finding.
  2. Action CL 2003/06/30: Revise this draft finding with new input from reviewers. 7 July Deadline.
• Action IJ 2003/06/09: Turn TB apple story into a finding.

Issues

• uriMediaType-9
  • IANA appears to have responded to the spirit of this draft (see email from Chris Lilley).What's required to close this issue?
  • Action CL 2003/05/05: Propose CL's three changes to registration process to Ned Freed. [What forum?]
• HTTPSubstrate-16
  • Action RF 2003/02/06: Write a response to IESG asking whether the Web services example in the SOAP 1.2 primer is intended to be excluded from RFC 3205
  • See message from Larry Masinter w.r.t. Web services.
• xlinkScope-23
  • See draft, and SW message to CG chairs.
  • Action CL 2003/06/30: Ping the chairs of those groups asking for an update on xlinkScope-23.
• binaryXML-30
  • Action TB 2003/02/17: Write to www-tag with his thoughts on adding to survey.
  • Next steps to finding? See summary from Chris.
• xmlFunctions-34
  • Action TBL 2003/02/06: State the issue with a reference to XML Core work. See email from TimBL capturing some of the issues.
• charmodReview-17
  1. Completed action IJ 2003/07/14: Move issue 17 to pending rather than resolved.
  2. Completed action DC: Remind I18N WG of what we are expecting regarding issue 17; send this on behalf of the TAG (Done).