Re: Audiobooks TF

Yes sure will put it on issue tracker.


More generally there are also some book that different chapter or different collection created by different writer.

So, yes this sounds like not an audiobook specific issue we have.


Thanks,

Zheng

________________________________
From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Sent: Friday, June 15, 2018 11:02:01 AM
To: Ivan Herman
Cc: Xu, Zheng | KGB; Avneesh Singh; Luc Audrain; Reid, Wendy; W3C Publishing Working Group
Subject: Re: Audiobooks TF

Yeah, it could go in the issue tracker and it could be more general.

Zheng, could you file this one as it seems to be a requirement for you?

I have mixed feelings about this though. If we go down that road we could end up with very complex metadata per resource being expressed in the manifest. There's a balance to find and it's not an easy one.

2018-06-15 16:58 GMT+02:00 Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>>:
(I think this should go on a github issue.)

Hadrien,

the structure you have below may be more general: to allow for a creator on a PublicationLink. Think of a conference publication as one WP: each article in the proceedings is a separate resource, with a separate set of creators (readBy is one of the specialized creators in 4.2.1.4)

ivan


On 15 Jun 2018, at 16:27, Hadrien Gardeur <hadrien.gardeur@feedbooks.com<mailto:hadrien.gardeur@feedbooks.com>> wrote:

Hello Zheng,

We're not using id/idref at all in our current syntax.

If you want to indicate different narrators per track, you can simply indicate their name using readBy like this:

"readingOrder": [
  {
    "url": "http://www.notexisted.org/download/audio1.mp3",
    "fileFormat": "audio/mpeg",
    "name": "Part 1, Sections 1 - 3",
    "readBy": "First Narrator"
  },
  {
    "url": "http://www.notexisted.org/download/audio2.mp3",
    "fileFormat": "audio/mpeg",
    "name": "Part 1, Sections 1 - 3",
    "readBy": "Second Narrator"
  }
]

That's not supported by our current WebIDL though, but I guess we could probably tweak it if deemed necessary (I'd like to have the duration of tracks in here).

Keep also in mind that the audio tracks themselves can contain metadata, that's usually the best option for complex resource level metadata.

Best,
Hadrien


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




--
Hadrien Gardeur
Co-founder, Feedbooks
http://www.feedbooks.com
T: +33.6.63.28.59.69
E: hadrien.gardeur@feedbooks.com<mailto:hadrien.gardeur@feedbooks.com>
54, rue de Paradis
75010 Paris, France