W3C

- DRAFT -

XHTML2 WG Weekly Teleconference

23 Jul 2008

Agenda

See also: IRC log

Previous

Attendees

Present
Tina, ShaneM, Roland, Alessio
Regrets
Steven, Mark
Chair
Roland
Scribe
ShaneM

Contents


 

Scibe: ShaneM

<scribe> Scribe: ShaneM

Passwords in the Clear

Response was sent. DONE.

XSD Review

<scribe> Ongoing

CR Transition Status

Roland sent a follow up - no action in three weeks.

Role Attribute Module

No updates.

XHTML Basic 1.1 Transition

Basically we r done - DTDs might live in MarkUp and date space. depends on powers that be.

Publication of Rec on 29 July.

XHTML Modularization Transition to Rec

Review period ended. No news on status.

XHTML 1.1 Second Edition

Waiting on M12N to get to Rec. Ready to go.

XHTML Access Module

Shane's actions: working on navigation order and SVG response ongoing.

Action on adding child emements in M12N is complete - this is relatively easy to do. DTDs have hooks and Schema you define the content model on the fly.

http://www.w3.org/TR/2008/WD-xhtml-access-20080526/#sec_3.1.2.

<scribe> ACTION: Shane to fix table of contents in Access Module - the links to sections are wrong in some cases. [recorded in http://www.w3.org/2008/07/23-xhtml-minutes.html#action01]

Discussion of what is really meant by navigation order...

If we were to say that the navigation order was the order of values in targetid, would that help? What would it mean if you had another intervening navigation event... does it restart the sequence of access key selections?

Alessio agrees it is not a simple case...

Roland suggests we enumerate the possibilities just so we can make a good decision.

<scribe> ACTION: Shane to document the ways navigation order / access could be interpreted. Group will then pick one and we will move on. [recorded in http://www.w3.org/2008/07/23-xhtml-minutes.html#action02]

Tina mentions that it would be interesting to have an element in which you could specify the list of IDs in "navigation order".

XML Events 2

Mark sent a note Monday about how the script element might be trickier than we thought w.r.t. backward compatibility.

Suggested we bring back the handler element as well.

Roland has been thinking about this, and agrees there is value in having both.

Could possibly introduce a way to say that the handler for an action is a function as opposed to a URI

Roland points out that this problem existed in XML Events 1 already.

If there is a function attribute, the function gets passed the event context. so @function takes a function name

<action event="whatever" function="someFunction">

Shane asks when @handler when there is @function? Roland mentions that there are XForms declarative examples that might make sense.

So @handler ONLY refers to specific elements that are part of the language, and any custom handlers an author wants are implemented in a scripting language and referenced via @function

Shane mentions that @function might make sense on the listener as well (and in the global attribute collection)

Roland thinks it probably does.

Roland mentioned that the Chair of the DOM3 Events group mentioned that they have been making some changes and we should sync up.

No follow up as yet, but we should keep an eye out.

XHTML Features

This continues...

All actions continue.

<Roland> XML Entity definitions for Characters

<Roland> http://www.w3.org/TR/2008/WD-xml-entity-names-20080721/

RDFa Syntax status

CR is complete, no real objections.

Roland raised the issue of @rel values. These are defined in the XHTML Vocatulary space

http://www.w3.org/1999/xhtml/vocab

We own the collection of values - if any one wants to extend the base reserved word collection they need to come to us.

Topic; XHTML 2 status update

Script element is tricky in the content model...

there are attributes that conflict and seem to have different semantics.

Roland will try to summarize the script issues.

Validator and error messages

The validator will tell people to use <li/> in an XHTML document.

Should we ask them to NOT give that advice?

<scribe> ACTION: Tina will try to dig up a document in the wild that gives "bad" advice and send an example to the mailing list. [recorded in http://www.w3.org/2008/07/23-xhtml-minutes.html#action03]

Summary of Action Items

[NEW] ACTION: Shane to document the ways navigation order / access could be interpreted. Group will then pick one and we will move on. [recorded in http://www.w3.org/2008/07/23-xhtml-minutes.html#action02]
[NEW] ACTION: Shane to fix table of contents in Access Module - the links to sections are wrong in some cases. [recorded in http://www.w3.org/2008/07/23-xhtml-minutes.html#action01]
[NEW] ACTION: Tina will try to dig up a document in the wild that gives "bad" advice and send an example to the mailing list. [recorded in http://www.w3.org/2008/07/23-xhtml-minutes.html#action03]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2008/08/20 15:09:57 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/@handler/@function/
Found Scribe: ShaneM
Inferring ScribeNick: ShaneM
Default Present: Tina, ShaneM, Roland, Alessio
Present: Tina ShaneM Roland Alessio
Regrets: Steven Mark
Agenda: http://lists.w3.org/Archives/Public/public-xhtml2/2008Jul/0022.html
Got date from IRC log name: 23 Jul 2008
Guessing minutes URL: http://www.w3.org/2008/07/23-xhtml-minutes.html
People with action items: shane tina try will

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.
[End of scribe.perl diagnostic output]