- From: Thierry MICHEL <tmichel@w3.org>
- Date: Tue, 05 Oct 2010 12:54:18 +0200
- To: Doug Schepers <schepers@w3.org>
- CC: "public-media-annotation@w3.org" <public-media-annotation@w3.org>
Doug, Could you please join today's call (now) ? I have sent an invitation earlier. Thierry Le 05/10/2010 12:50, Doug Schepers a écrit : > drastic simplification, with only one or two interfaces, with a couple > of methods to get back arrays of values, rather than trying to strongly > type all the possible attributes for each type of metadata. The array > structure could simply be an associative array, with the name of the > property as the index for the value, like a JSON structure. This would > be much simpler to implement, and even simpler for content authors, > since they could use a generic function to get and process any metadata > value, rather than having to make custom code for each type of metadata > they wanted. > > Since any given piece of metadata may have multiple representations with > different data and in different formats on different dates, I would > suggest that each return value be an array of arrays... with the > metadata itself embedded in an array item that describes its format and > date... or something like that. > > This is the suggestion I made before, at TPAC and when I talked to > several of you individually. I'm not set on my solution, but I feel > confident that the API as designed in the spec today is too large and > too rigid.
Received on Tuesday, 5 October 2010 10:55:16 UTC