- From: Felix Sasaki <felix.sasaki@fh-potsdam.de>
- Date: Fri, 29 Jan 2010 13:26:49 +0100
- To: "Evain, Jean-Pierre" <evain@ebu.ch>
- Cc: Joakim Söderberg <joakim.soderberg@ericsson.com>, "Bailer, Werner" <werner.bailer@joanneum.at>, Pierre-Antoine <pierre-antoine.champin@liris.cnrs.fr>, "public-media-annotation@w3.org" <public-media-annotation@w3.org>
- Message-ID: <ba4134971001290426o43aeb4ev10ebdb2584adedc6@mail.gmail.com>
Not sure if this was mentioned in this thread yet, but yesterday a document was published which might help in developing the requirements to be tested in the test suite: http://www.w3.org/TR/2010/NOTE-test-methodology-20100128/ Best, Felix 2010/1/29 Evain, Jean-Pierre <evain@ebu.ch> > That will be xml files in the formats advertised and for which the mapping > has been provided. > > Jean-Pierre > > -----Original Message----- > From: public-media-annotation-request@w3.org [mailto: > public-media-annotation-request@w3.org] On Behalf Of Joakim Söderberg > Sent: mercredi, 27. janvier 2010 15:11 > To: Bailer, Werner; Pierre-Antoine; public-media-annotation@w3.org > Subject: RE: [mawg] RE: Testsuites importants point wrap-up and post on the > mailing list > > Great, now we got the discussion going! > > Werner/Jean-Pierre, can you please explain and exemplify how the input > would look like? > > /Joakim > > -----Original Message----- > From: public-media-annotation-request@w3.org [mailto: > public-media-annotation-request@w3.org] On Behalf Of Bailer, Werner > Sent: den 26 januari 2010 17:01 > To: Pierre-Antoine; public-media-annotation@w3.org > Subject: RE: [mawg] RE: Testsuites importants point wrap-up and post on the > mailing list > > +1 to Pierre-Antoine > > If we go for a web based implementation of the test suite, it could be a > service that takes key/value pairs of the properties extracted from the > container file as input. This eliminates the need of having an artificial > format as input. As Pierre-Antoine suggested, providing the values of the > properties that are expected to be extracted from a certain input file is > very useful for debugging. > > Best regards, > Werner > > > -----Original Message----- > > From: public-media-annotation-request@w3.org [mailto:public-media- > > annotation-request@w3.org] On Behalf Of Pierre-Antoine > > Sent: Dienstag, 26. Jänner 2010 15:36 > > To: public-media-annotation@w3.org > > Subject: Re: [mawg] RE: Testsuites importants point wrap-up and post > > on the mailing list > > > > On 26/01/2010 14:41, Joakim Söderberg wrote: > > > II) Regarding testing the individual features, we can either: > > > > > > 1) Create some media files corresponding to the formats in > > scope, > > > that contain metadata in that format. E.g. a jpg-file, with EXIF > > > elements, an mp3 with ID3 etc. > > > > as Raphael pointed out, depending on the format, this won't be a > > *media file*, but rather a metadata file (e.g. MPEG-7). > > > > > BUT then we will have to recommend a library (or other tool) to > > > extract the metadata, since it should not be part of the test. > > > > I'm not too sure about that; is it very relevant for us to commit > > (even > > informally) to a particular software/library? Furthermore, the library > > depends on the programming language... > > > > > 2) Or we produce a text or XML (1) file containing > > the > > > native metadata elements and let it represent the metadata in > > > assumed media file.E.G: <exif:INAM>Eiffel Tower</exif:INAM> > > > > > > An implementation reads the file, gets the relevant > > > attribute and returns the correct "ma:" result. > > > > As I pointed out, I think such a solution would be vain or even > > counter-productive, as it would require implementations to be able to > > parse this artificial format, which would not be used outside our test > > suites. Furthermore, what would guarantee that an implementation > > passing the test with the artificial format would *also* behave > > correctly with embeded metadata? > > > > > > However, I think that providing such files would be a good idea, but > > for a different reason: they would help implementors to check that > > their implementation extract the legacy metadata in a way which is > > consistent with what we expect. This would *not* be a part of the test > > (as it would only test the extraction library, not the ma: mapping), > > but this would definitely help implementors to understand what is > > wrong if their implementation fails a test -- help them debug the > > implementation or help us debug the test suite, as we may err in our > > making of the media/metadata files... > > > > pa > > > ----------------------------------------- > ************************************************** > This email and any files transmitted with it > are confidential and intended solely for the > use of the individual or entity to whom they > are addressed. > If you have received this email in error, > please notify the system manager. > This footnote also confirms that this email > message has been swept by the mailgateway > ************************************************** > > >
Received on Friday, 29 January 2010 12:27:23 UTC