RE: The use cases table, modified, for comment

Hi,

First, the notion is to maintain the database in XML and do the transform to
HTML for use in browser or reading system. We have the XSLT for this now.

If you recommend we convert to HTML now, we would need to be able to provide
more semantics than is available now. 

The Summary is expected to be very short the long description could be very
extensive, have tables, etc.

We probably will add specific information for 3D printing.

Best
George

-----Original Message-----
From: Siegman, Tzviya - Hoboken [mailto:tsiegman@wiley.com] 
Sent: Wednesday, October 14, 2015 9:24 AM
To: George Kerscher; 'Deborah Kaplan'
Cc: 'Ivan Herman'; public-dpub-accessibility@w3.org
Subject: RE: The use cases table, modified, for comment

Hi George,

Thanks for taking the time to review.

Would you please elaborate on what specific aspects of Diagrammer you'd like
us to mention? As you noted, the model is in XML. This assessment focuses on
HTML. I assume the outcome will guide Diagrammer forward. For example,
Diagrammer currently has elements called <d:summary> and <d:longdesc>. Is
there a need for the equivalents of both?

Thanks,
Tzviya  

Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com 

-----Original Message-----
From: George Kerscher [mailto:kerscher@montana.com] 
Sent: Wednesday, October 14, 2015 11:06 AM
To: Siegman, Tzviya - Hoboken; 'Deborah Kaplan'
Cc: 'Ivan Herman'; public-dpub-accessibility@w3.org
Subject: RE: The use cases table, modified, for comment

Dear All,

Sorry for being so slow to chime in. I reviewed 
https://rawgit.com/w3c/dpub-accessibility/ivan-comment-on-analysis/extended-
description-analysis.html


First,  the work taking place at the Diagram Center developing and
maintaining Diagrammar: A Framework for Making Images and Graphics
Accessible 
Should be noted IMO. This can address a wide range of enhancements
envisioned in a structured environment. We envision the XML content being
transformed to HTML for viewing in browsers and reading systems.
http://diagramcenter.org/standards-and-practices/content-model.html


Secondly, SVG is wonderful for many types of graphical content, but it is
not suited for the range of enhancements that have been envisioned. It seems
that the tables capture this.

Finally, for EPUB 3.1 we note the action item for Matt that aria-describedat
will be announced as deprecated.  It would be excellent to attempt to
resolve the mechanism for EPUB 3.1 developments.

Hope this helps.

Best
George

 mechani

-----Original Message-----
From: Siegman, Tzviya - Hoboken [mailto:tsiegman@wiley.com] 
Sent: Monday, October 12, 2015 12:03 PM
To: Deborah Kaplan
Cc: Ivan Herman; public-dpub-accessibility@w3.org
Subject: RE: The use cases table, modified, for comment

Thanks for your time Deb

Everyone else, the "Implementation Complexity" table is filled in. Please do
a review and make the changes yourself, or send comments to me.

Thanks,
Tzviya

Tzviya Siegman
Digital Book Standards & Capabilities Lead
Wiley
201-748-6884
tsiegman@wiley.com 


-----Original Message-----
From: Deborah Kaplan [mailto:dkaplan@safaribooksonline.com] 
Sent: Monday, October 12, 2015 1:56 PM
To: Siegman, Tzviya - Hoboken
Cc: Ivan Herman; public-dpub-accessibility@w3.org
Subject: RE: The use cases table, modified, for comment

In that case I absolutely beg everybody else on this list to contribute some
of those values. I put more time than I had to spare into building this
document last week according to the plan we had decided upon in our last 2
meetings, and I do not have the time to produce an entire new section of
content out of thin air in time for this document to be delivered in a
timely fashion. The best I can offer is that if other people come up with
values for that section, I can get them into the HTML; other people don't
have to fight with HTML or github if you just send me plaintext or
spreadsheet or something.

I will add a specification of what is meant by "role", and I will
incorporate Ivan's other changes.

Deborah

On Mon, 12 Oct 2015, Siegman, Tzviya - Hoboken wrote:

> There is a column for Authors (that's us) and UAs. We need to at least
look over the authors column. If part of argument is that something is way
to convoluted to deal with, we need to express that here.
>
> Tzviya Siegman
> Digital Book Standards & Capabilities Lead Wiley
> 201-748-6884
> tsiegman@wiley.com
>
>
> -----Original Message-----
> From: Deborah Kaplan [mailto:dkaplan@safaribooksonline.com]
> Sent: Monday, October 12, 2015 1:46 PM
> To: Siegman, Tzviya - Hoboken
> Cc: Ivan Herman; public-dpub-accessibility@w3.org
> Subject: RE: The use cases table, modified, for comment
>
>> I think PF was relying on us to provide information about the table
called "Implementation Complexity" as well.
>
> I don't think we should do that, though. Given the conversations with them
privy to, they know far more than we do about the complexity of
implementation. We would be giving them false information, where they have
the expertise to know the actual answers.
>
> Unless they mean "complexity of implementation by content producers,"
> actually is our expertise. But if what they mean is "complexity of
implementation by user agents and AT," well, that's where they are the
experts in the conversation.
>
> Deborah
>

Received on Wednesday, 14 October 2015 16:10:22 UTC