W3C | TAG | Previous: 30 Jun teleconference | Next: 14 July 2003 teleconf

Agenda for 7 July 2003 TAG teleconference

Nearby: Teleconference details · issues list · www-tag archive

Note: The Chair does not expect the agenda to change after close of business (Boston time) Thursday of this week.

Homework

• All: Text sent by David Orchard about extensibility.
• At least CL, NW: Client handling of MIME headers
• All: Second comment from Noah in summary of comments about URIs, Addressability, and the use of HTTP GET and POST
• All: Notes from Chris Lilley on error handling

1. Administrative (10min)

1. Roll call. Likely regrets: RF.
2. Accept minutes of 30 Jun teleconference?
3. Accept this agenda?
4. Next meeting: 14 July?
5. Face-to-face meeting agenda?

2. Technical (80 mins)

2.1 Review of text from Voice Browser Working Group (20 mins)

• contentTypeOverride-24
  • Speech Recognition Grammar Specification Version 1.0, section 2.2.2 External Reference by URI

Draft forwarded by SW (Member-only)

2.2 Findings (20 mins)

See also: findings.

Next steps on these findings:

• contentTypeOverride-24: Client handling of MIME headers; see summary of comments.
  1. Action SW 2003/06/23: Talk to Voice Browser WG about proposed text, then bring back to TAG. (Done)
  2. Action CL, NW 2003/06/30: Read the draft finding by 7 July. NW Done
  3. Completed action IJ 2003/06/30: Announce on www-tag that we expect to approve this finding in a week or so. Last chance for comments (Done)
  4. Completed action IJ 2003/06/30: Ping SMIL IG about this finding, which refers to architectural error in SMIL 2.0 (Done).
  5. See comments from Philipp Hoschka and Rob Lanphier
  6. See suggested editorial changes from TBL
• 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.
• URIs, Addressability, and the use of HTTP GET and POST; see summary of comments. See also comments from Larry Masinter.
  • whenToUseGet-7
    • Next step for revised draft finding?
    • Action IJ 2003/06/23: Incorporate a sentence about scope based on LM comments.
• contentPresentation-26: Action CL 2003/06/02: Make available a draft finding on content/presentation.
• metadataInURI-31
  • Completed action SW 2003/06/02: Draft finding for this one. (Done)
  • See also TB email on Apple Music Store and use of URI schemes instead of headers
• Action IJ 2003/06/09: Turn TB apple story into a finding.

2.3 Architecture document (15 minutes)

27 June 2003 Working Draft of Arch Doc published.

1. Discussion of text sent by David Orchard about extensibility.
2. Action PC 2003/06/16: Send second draft of AC announcement regarding TAG's last call expectations/thoughts and relation to AC meeting feedback.
3. Action RF 2003/06/02: Rewrite section 5. Section 5 is expected to be short.
4. Action IJ 2003/06/16: Attempt to incorporate relevant bits of "Conversations and State" into section to be produced by RF.

2.4 Issues the TAG intends to discuss (25 mins)

• errorHandling-20
  • 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.
• RDFinXHTML-35
• mixedUIXMLNamespace-33

2.5 Issues with action items

• 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.
• siteData-36
  • Action TBL 2003/02/24 : Summarize siteData-36

2.6 Issues the TAG intends to discuss at face-to-face meeting

Identifiers

• 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'sproposed step forward on IRI 27.

Qnames, fragments, and media types

• 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
  • See issue description from David Orchard. Next steps?
  • Action DO 2003/06/23: Point Jonathan Marsh at options. Ask them for their analysis.
• putMediaType-38

RDDL, namespace documents

• 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 Brayon 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.

2.7 New issues?

The TAG expects to discuss these on 14 July.

1. Visibility of Web Services, raised by Mark Baker
2. Character model conformance, raised by TBL
3. Meaning of URIs in RDF documents, raised by TBL

3. Other actions

• Action IJ 2003/02/06: Modify issues list to show that actions/pending are orthogonal to decisions. IJ and PLH making substantial progress on this; hope to have something to show in May.