Re: We Need a Meeting!

Well, I think the agenda is quite full, and I'm concerned that this issue
is somewhat beyond the scope of the discussion. The immediate purpose of
the meeting is to gain a sense of where the project currently stands and to
raise any issues that may impede progress.

For Richard's issue, I think the best way to approach this is by first
filing an issue in our tracker.

Richard, please create a new content issue here:

http://project.webplatform.org/content/planning

Add the issue under Unassigned issues.

We can certainly put this on the agenda for discussion, but we may not get
to it tomorrow.

Thanks!

~Scott





On Thu, Sep 19, 2013 at 9:14 AM, Eliot Graff <Eliot.Graff@microsoft.com>wrote:

> Hi Richard.
>
> Apologies for missing your original mail. Yes, this is the correct list
> and this is the correct meeting to start the discussion. We do have a small
> team of people to implement changes to templates, but we should discuss
> this in the overall content discussion before implementing.
>
> Scott, can you add this item to the agenda? I know we're really packed for
> tomorrow; if we can't get to it this week, we can either discuss further in
> mail or take it up at the next meeting.
>
> Thanks,
>
> Eliot
>
>
>
>
> >-----Original Message-----
> >From: Richard Ishida [mailto:ishida@w3.org]
> >Sent: Thursday, September 19, 2013 8:54 AM
> >To: public-webplatform@w3.org
> >Subject: Re: We Need a Meeting!
> >
> >I'm new to this list, so I don't know your procedures. Ten days ago, I
> sent the
> >following email, which attracted no response. Would it be a suitable
> topic for
> >discussion at your meeting?
> >
> >RI
> >
> >On 09/09/2013 14:36, Richard Ishida wrote:> Folks,  >  > I've been working
> >through the list of HTML elements and attributes  > putting in links to
> the i18n
> >resources we have, and have made a start on  > the CSS properties, etc. It
> >wasn't always obvious where to put those  > links - they are not really
> like the
> >other optional links that appear at  > the bottom of the page;
> >internationalization information is typically an  > essential part of the
> >information that content authors/developers need  > (as, of course, is WAI
> >info).
> > >
> > > I'd like to propose that the template for each page in the list of  >
> elements,
> >attributes, and properties, etc. include an additional  > section:
> Universal
> >Access.
> > >
> > > In this section we can add WAI, i18n and device independence tips, and
>  >
> >links to relevant materials.
> > >
> > > Is this the right list to make such suggestions? Who would take  >
> decisions
> >on that?
> > >
> > > Cheers,
> > > RI
>
>