Re: comments on metadata note

Tzviya,

I played with a possible replacement of the tables with <dl> structures but... I am not convinced at all. The point is: it would make the list very long and therefore very difficult to get some sort of an overview; that is where a table is really very helpful. I have added some markup that are really there for accessibility (@scope, @summary, proper table structures); because this is, in fact, a very basic table I believe it should be all right.

The only way to get around this issue would be to get into a complex CSS processing to store the data in lists and display them as tables. Whilst I know it is possible, I also know that, alas!, it is still complicated and brittle in terms of the various browsers out there; let alone the fact that I do not exactly know how to that with all bells and whistles...

Is it a big problem if we keep the tables as they are?

Ivan


> On 22 Dec 2014, at 20:12 , Ivan Herman <ivan@w3.org> wrote:
> 
> Hey Tzviya,
> 
> I leave most of the things to Bill, who is the main editor, only a few remarks below,
> 
> 
> On 22 Dec 2014, at 18:53, Siegman, Tzviya - Hoboken <tsiegman@wiley.com> wrote:
> 
>> Hi Bill and Madi,
>> 
>> Thank you for all your work on the metadata note [http://w3c.github.io/dpub-metadata/]. As I mentioned on the call, I have some edits that I hope will be easy to execute. Some of these are just picky.
>> 
>> I recommend against including phrases that indicate time. For example, eliminate the phrase, “new annotations WG”, because it immediately dates the document.
>> 
>> Can we make a decision about DPIG vs. DPUB? This document refers to DPIG. Our IRC channel and such use DPUB. I vote for DPUB.
>> 
> 
> Well, the IRC channel was just to make it short...
> 
> This group is, the DPUB IG, in fact. DPUB is a bit too general for my taste...
> 
>> Audience:
>> As discussed on today’s call, this document is targeted at a W3C audience. We will assess at a later date whether there will documents targeting a publishing audience. That being said, I think this document assumes a bit too much familiarity with publishing. A way to alleviate that is to link to the defined terms in the appendix.
> 
> That was, in fact, a temporary glitch in respec, which has been settled since. All DPUB terms should now link to the glossary, exactly for the reasons that you say. Please tell me if there are terms that I did not do yet...
> 
>> I think it would also be helpful to eliminate or reword some of the statements that end up sounding like commentary.
>> 
>> See “Example 1”.
>> CrossRef—which provides (among other services) cross-publisher linking from citations to cited publications using the DOI [link to definition of DOI] (the identifier that has become fundamental to the scholarly publishing ecosystem)—has for some time recommended that DOIs always be expressed in the form of a URI. However, this is inconsistently done because of the lack of understanding (perhaps change to familiarity with?) of the URI by publishers and other participants in the publishing ecosystem and the large number of existing published DOIs expressed in the previously recommended format, which was not a URI.
>> 
>> I think doing this will neutralize the document as well as make it briefer.
>> 
>> Section 1.1 “…in the three modes described at the beginning of this section.”  - I am a little unsure about what the three modes of publishing are.
>> 
>> Appendix B & C
>> As part of my goal of eliminating tabular objects that do not need to be tables, please consider making this thing called a list into an actual list. Imagine reading this on a phone or with AT.
>> 
> 
> As Bill said, these were transferred from a google sheet.
> 
> I am not 100% in this case. Yes, it can be transformed into DL lis, something like
> 
> ISBN
>     URI form (if applicable)
>      Authority
>     Comments
> ...
>      ...
> 
> Do you think it would really make it better? It will make a fairly long list...
> 
> But if you really think it is better, I can do it I guess (although, at this point, I do not see any other way than doing manually)
> 
> thanks!
> 
> Ivan
> 
> 
> 
>> Please let me know if I can help in any way,
>> 
>> Thanks,
>> Tzviya
>> 
>> [1] http://w3c.github.io/dpub-metadata/
>> 
>> ****************************
>> Tzviya Siegman * Digital Book Standards & Capabilities Lead * John Wiley & Sons, Inc.
>> 111 River Street, MS 5-02 * Hoboken, NJ 07030-5774 * 201-748-6884 * tsiegman@wiley.com


----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704