W3C home > Mailing lists > Public > public-digipub-ig@w3.org > November 2013

RE: displayed metadata

From: Siegman, Tzviya - Hoboken <tsiegman@wiley.com>
Date: Fri, 1 Nov 2013 13:03:20 -0400
To: Ivan Herman <ivan@w3.org>
CC: "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>
Message-ID: <C274A5503C851E43A8ED400AC86E0285036A0CFF67@SOM-MB.wiley.com>
Thank you Ivan. I will try to clarify. It seems that much of this come to the question of whether books have URIs. At this point, most do not. I am coming to the conclusion that much of what this group discusses comes back to URIs.

Tzviya Siegman * Senior Content Technology Specialist * John Wiley & Sons, Inc.
111 River Street, MS 5-02 * Hoboken, NJ 07030-5774 * 201-748-6884 * tsiegman@wiley.com

-----Original Message-----
From: Ivan Herman [mailto:ivan@w3.org] 
Sent: Friday, November 01, 2013 10:01 AM
To: Siegman, Tzviya - Hoboken
Cc: DPUB mailing list (public-digipub-ig@w3.org)
Subject: Re: displayed metadata

Hi Tzviya,

On Nov 1, 2013, at 14:36 , "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com> wrote:

> Hi All,
> I am (finally) working on use cases for Behavioral Adaptional Content. There is much to discuss in the category of what I'll call displayed metadata. This is information about the content, but it is also information that should be displayed to the user.  We encounter this at the publication level, the sub-publication (chapter or article) level, and at a more granular level in some cases.  
> Is there a way to render information like this if it has been captured as <meta>, RDF, or microdata? More examples?
> Example 1
> Chapter Number + Chapter Title + Subtitle:
> <header>
> <h1><span class="chapterNumber">Chapter X </span> <span 
> class="chapterTitle">Chapter Title: </span> <span 
> class="chapterSubTitle">Subtitle</span></h1>
> This is one of many ways to mark up the information. One could also use <h2> and <h3> for the Chapter Title and Subtitle, but the rest of the chapter with its many levels of headings remains to be marked up. In XML models I have seen this called <titleGroup>.

I must admit I do not really understand the question. Do you ask whether this type of information can be put into HTML using microdata or RDF (well, encoded in RDFa)? The answer is yes, provided that there is an agreement in the vocabulary. But, say,

<span property="some_vocabulary_term_for_chapter_number">Chapter X</span>

in RDFa is possible, and it would provide a statement roughly of the form

<> URI_for_some_vocabulary_term_for_chapter_number "Chapter X"

when turned into RDF, where <> here stands for the URI or some sort of a reference (DOI?) for the book as a whole. Similar can be done in microdata. Of course, property (or itemprop in microdata) can be used by CSS for styling, too.

But I am not sure this is what you ask...

TS: This is what I'm asking, and I suppose I'm looking for the controlled vocabulary. At this time, most books do not have a URI. 
> Example 2
> Media Review: A journal article is a review of external media, such as a book. The metadata for the reviewed media must be included so the user knows what is reviewed. Ideally, this should be linked data, but that aside, how do we accomplish this semantically?

Similarly as above, both microdata or RDFa can be used for this.

> Currently this is often done using <p>s, <div>s and <span>s with classes, such as <p class="MediaReviewAuthor">  and the like. In some cases, a DOI is included. This offers display, but little else.

I see two issues:

- what is the reference to the book? Does each ebook has such thing? A DOI or anything similar?
- encoding in RDFa/microdata is possible. But who does what with this information? Extracting, say, RDF from that information is possible but then so what? What is the usage?

TS: The reference to the book is simply that this is a book being reviewed (or discussed). I was thinking that information could be used to show a relationship between the 2 books in addition to displaying the information to the reader.


> I will add these as use cases over the weekend. Any thoughts?
> Best,
> Tzviya
> ****************************
> Tzviya Siegman * Senior Content Technology Specialist * John Wiley & Sons, Inc.
> 111 River Street, MS 5-02 * Hoboken, NJ 07030-5774 * 201-748-6884 * 
> tsiegman@wiley.com

Ivan Herman, W3C
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Friday, 1 November 2013 17:03:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:35:46 UTC