Questions about last week's minutes

["Kristen Eberlein" <keberlein@sdl.com>]

Hi, Paul.

I know that Stan answered some of your questions in e-mails and his
explanations of the modified minutes. Let me see if I can answer some of your
unanswered questions.

Report from Learning and Training SC:
-------------------------------------

> - Processing support: Su-Laine asked John for an update on the
>       state of processing support for the L&T specializations. John
>       reported that the current L&T specializations relied heavily
>       on default processing tools and flows. That said, the L&T
>       SC has posted a set of sample topics and set of XHTML
>       processing extensions for review.
 

<Paul> XHTML processing extensions or expectations? Has posted where?  Need a
URI if you want it reviewed. Reviewed for what?  Is it to become a TC
deliverable? </Paul>

<Kris> I think the phrase "for review" should simply removed. </Kris>


ITEM: General implications of multiple uses of the same topic with different
keys
-----------------------------------------------------------------------------
----

>      - AI/Robert: Touch base with Michael this coming week to determine
> how/whether Michael needs assistance in writing up a proposed resolution or
> whether Robert should assume ownership of that write-up.

<Paul> And what is the URI of the write up we plan to review when Michael is
on the call? </Paul>

<Kris> There was no write up at the time of the TC call. The action item was
1) for Robert to get with Michael and ensure that Michael's concerns were
conveyed to the TC, and 2) for Robert to "assume ownership" of the item if
Michael could not follow it through.

Robert did post on this topic to the list yesterday:
http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201103/msg00
021.html </Kris>


Best regards,
Kris
Kristen James Eberlein l DITA Architect and Technical Specialist l SDL
Structured Content Technologies Division l (t) + 1 (919) 682-2290 l
keberlein@sdl.com

Please consider the environment before printing this e-mail