Re: [whatwg] metadata

On Mon, Apr 24, 2017 at 5:04 AM, Kevin Marks wrote: > On Sun, Apr 23, 2017 at 5:58 PM, Andy Valencia > wrote: >> === Dynamic versus static metadata >> >> Pretty much all audio formats have at least one metadata format. While >> some apparently

Re: [whatwg] metadata (and royalty reporting for some weird reason)

Hi all: * I agree with the exposure of issues Andy presents. I do sympathize with his approach, too. * getMetadata sounds reasonable to me. The choice that a final user/client of a web service, or a streaming service, can add some data sounds reasonable to me. And I am not

Re: [whatwg] metadata

On Sun, Apr 23, 2017 at 5:58 PM, Andy Valencia wrote: > === Dynamic versus static metadata > > Pretty much all audio formats have at least one metadata format. While > some apparently can embed them at time points, this is not used by any > players I can find. The

Re: [whatwg] metadata (and royalty reporting for some weird reason)

On 2017-04-23 18:58, Andy Valencia wrote: Reporting Only "artist" and "title" are required for royalties reporting for internet radio. I'm sorry for a bit of topic drift on this list, and I'm sure requirements vary by nation. I do reporting for a local station and among the requirements I

Re: [whatwg] metadata

I've become aware of quite a bit more metadata support in the world of web browsers; please consider my old proposal withdrawn. === Reporting > Only "artist" and "title" are required for royalties reporting for > internet radio. I'm sorry for a bit of topic drift on this list, and I'm sure

Re: [whatwg] metadata (re-mapping)

On 2017-04-16 15:36, Delfi Ramirez wrote: * Sound.load(new URLRequest("07 - audio.mp3")); * Some old tricks on the issue were done in the past. here the link of an ECMAScript derivative from the past, if it serves you as a model ID3 tags Get/Receive [6]. That is not a trick,

Re: [whatwg] metadata

Hi Roger, hi all: * "_passing metadata in a stream so that a HTML webplayer can show artist and title_" can be accomplished extracting the ID3 tags from the file and presenting them as JSON values, for example * Sound.load(new URLRequest("07 - audio.mp3")); * Some old

Re: [whatwg] metadata

On 2017-04-16 03:01, Delfi Ramirez wrote: * WIPO stands for _World Intellectual Property Organization_, and the ... * Meta-Data: Following the indications of the WIPO ( focusing on a World Wide Web service ) that now, services like Pandora are not allowed to stream ( are de

Re: [whatwg] metadata

Hi Roger, hi all: My fault WPI, was horrendous mistake due to the keyboard, and other thingsin mind : WIPO, I meant. here below the info to avoid future re-works in the API and teh tag, if it helps. * WIPO stands for _World Intellectual Property Organization_, and the IP acronym for

Re: [whatwg] metadata

On Fri, Apr 14, 2017 at 10:23 PM, Andy Valencia wrote: > But the overarching issue is that you're doing JS-initiated > network operations, and origin policy is going to stop you. > You can claim Shoutcast/Icecast should give permissive > origins, but they don't, and

Re: [whatwg] metadata

On 2017-04-15 14:00, Delfi Ramirez wrote: Some information that may be of use, concerning to the WPI rules for royalties et al in files. I have no idea what/who WPI is. But StreamLicensing.com (which has a deal with ASCAP/BMI/SESAC/SoundExchange) Only require artist and title, and that

Re: [whatwg] metadata

Hi All: Some information that may be of use, concerning to the WPI rules for royalties et al in files. What we know as rights. Uh, Meta elements required * Title : 100% * Artist ( Interpreter): 12% * Time: lenght of the piece. Royalties are assigned by time

Re: [whatwg] metadata

On 2017-04-14 22:23, Andy Valencia wrote: Ok. Note that this data structure suffices to encode the baseline information from Shoutcast/Icecast. It does not, for instance, encode "Label", needed to do licensing reporting in the USA. "Year" is another datum often of interest. Only "artist" and

Re: [whatwg] metadata

Thank you for the helpful comments. wrote: > http://www.smackfu.com/stuff/programming/shoutcast.html isn't detailed > enough to get interoperable implementations, in particular the metadata > keys would have to be defined. Note that mp3, flag, ogg, and wav all have entirely

Re: [whatwg] metadata

On Mon, Apr 10, 2017 at 6:44 AM, Philip Jägenstedt wrote: > There is a very old bug for exposing the metadata: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=5755 > > In order to make progress, there needs to be implementer interest. Although > it may well fizzle out, a new

Re: [whatwg] metadata

On Mon, Apr 10, 2017 at 8:38 AM Andy Valencia wrote: > What follows is a first pass at addressing a missing ability > when dealing with Internet streams, usually radio ones. > Comments and suggestions are quite welcome; as my first > attempt--ever--at submitting to

[whatwg] metadata

What follows is a first pass at addressing a missing ability when dealing with Internet streams, usually radio ones. Comments and suggestions are quite welcome; as my first attempt--ever--at submitting to this group, apologies if I've made any mistakes in how I've proceeded. Thanks, Andy Valencia

Re: [whatwg] metadata attribute for media

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/02/13 05:48 AM, Nils Dagsson Moskopp wrote: If one cares to that extent, and is already handling format differences, dealing with vendor variation on top isn't that much more effort. I disagree, strongly. Ok, thanks for the feedback. Do

Re: [whatwg] metadata attribute for media

Ralph Giles gi...@mozilla.com schrieb am Tue, 11 Dec 2012 17:23:38 -0800: On 12-12-11 4:58 PM, Ian Hickson wrote: […] I don't think we should have an open-ended API without fixed names, because that is a recipe for an interoperability disaster. I agree it would have interoperability

Re: [whatwg] metadata attribute for media

On 12-12-11 5:23 PM, Ralph Giles wrote: That said, I'm not convinced this is an issue given the primary use-case, which is pretty much that web content wants to do more sophisticated things with the metadata than the user-agent's standardized parsing allows. If one cares to that extent, and

Re: [whatwg] metadata attribute for media

On Wed, Dec 12, 2012 at 2:23 PM, Ralph Giles gi...@mozilla.com wrote: That said, I'm not convinced this is an issue given the primary use-case, which is pretty much that web content wants to do more sophisticated things with the metadata than the user-agent's standardized parsing allows. If

Re: [whatwg] metadata attribute for media

On Thu, 20 Sep 2012, Ralph Giles wrote: Back in June, I proposed[1] a new attribute to get metadata tag data out of media resources. I've done an experimental implementation of this which is now in the Firefox Aurora (alpha) channel[2] and Nightly development builds. The method is

Re: [whatwg] metadata attribute for media

On 12-12-11 4:58 PM, Ian Hickson wrote: This seems reasonable. Thanks for the feedback. Anyone else? :-) I don't want to be the one to maintain the mapping from media formats to metadata schema, because this isn't my area of expertise, and it isn't trivial work. Good point. This would

Re: [whatwg] metadata attribute for media

On 12-11-26 4:18 PM, Ralph Giles wrote: interface HTMLMediaElement { ... object getMetadata(); }; After the metadataloaded event fires, this method would return a new object containing a copy of the metadata read from the resource, in whatever format the decoder implementation

Re: [whatwg] metadata attribute for media

On 12-09-27 1:44 AM, Philip Jägenstedt wrote: I'm skeptical that all that we want from ID3v2 or common VorbisComment tags can be mapped to Dublin Core, it seems better to define mappings directly from the underlying format to the WebIDL interface. You're right. Given the open-endedness of

Re: [whatwg] metadata attribute for media

On Fri, 21 Sep 2012 01:32:19 +0200, Ralph Giles gi...@mozilla.com wrote: Back in June, I proposed[1] a new attribute to get metadata tag data out of media resources. I've done an experimental implementation of this which is now in the Firefox Aurora (alpha) channel[2] and Nightly development

[whatwg] metadata attribute for media

Recently, we've been considering adding a 'tags' or 'metadata' attribute to HTML media elements in Firefox, to allow webcontent access to metadata from the playing media resource. In particular we're interested in tag data like creator, title, date, and so on. My recollection is that this has

Re: [whatwg] metadata attribute for media

On Tue, Jun 12, 2012 at 7:53 AM, Ralph Giles gi...@mozilla.com wrote: Recently, we've been considering adding a 'tags' or 'metadata' attribute to HTML media elements in Firefox, to allow webcontent access to metadata from the playing media resource. In particular we're interested in tag data