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

Re: displayed metadata

From: Jean Kaplansky <Jean.Kaplansky@aptaracorp.com>
Date: Fri, 1 Nov 2013 21:13:55 +0530
To: "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>
Message-ID: <CE992DF1.31C4A%jean.kaplansky@aptaracorp.com>
Comments below – look for > JLK@Aptara:

From: <Siegman>, Tzviya - Hoboken <tsiegman@wiley.com<mailto:tsiegman@wiley.com>>
Date: Friday, November 1, 2013 at 9:36 AM
To: "DPUB mailing list (public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>)" <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: displayed metadata
Resent-From: <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Resent-Date: Friday, November 1, 2013 at 9:36 AM

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:
<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>.

> JLK@Aptara: Did you check schema.org for any existing patterns that might support this in any way?

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?
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.

> JLK@Aptara:  I’ve seen this done via database like markup for bibliographical information. It’s painstaking markup to produce, since you need to set up business rules for what goes into a bibliographic entry based on the media type, but it’s not impossible to do, and can be maintained via taxonomy and stringent CMS practices.

I will add these as use cases over the weekend. Any thoughts?

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<mailto:tsiegman@wiley.com>
Received on Friday, 1 November 2013 15:45:44 UTC

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