RE: [mawg] MAWG implementation thoughts

Dear all,

If I take the example of TV-Anytime (probably more will appear in the next few months using EBUCore and we'll see what are the implementation options) I would see two typical cases:


1.       TVA instances will be published on a page e.g. like BBC does on BBC backstage. The API could develop a method to access these files and map the information to the ma: attributes using the Xpath expressions provided in the mapping table or possibly combining terms from complex structures (see the discussion on person and organisation names.

2.       TVA has defined how two develop web services for queries. You may want to have a look at this to look for ideas? But this not a simple API.

Best regards,

Jean-Pierre

From: public-media-annotation-request@w3.org [mailto:public-media-annotation-request@w3.org] On Behalf Of Bailer, Werner
Sent: mardi, 17. novembre 2009 16:05
To: Chris.Poppe@UGent.be; public-media-annotation@w3.org
Subject: RE: [mawg] MAWG implementation thoughts

Dear Chris,

Concerning the first two points: I agree.

Concerning the web service scenario: I think the main difference is the fact that it could do more complex processing for the mapping than one would want to integrate into a browser, i.e. it could be more flexible.

Best regards,
Werner

From: public-media-annotation-request@w3.org [mailto:public-media-annotation-request@w3.org] On Behalf Of Chris Poppe
Sent: Dienstag, 17. November 2009 09:40
To: public-media-annotation@w3.org
Subject: [mawg] MAWG implementation thoughts

Dear all,

I was trying to implement a test suite and came across the following problems/remarks when thinking about scenario1 in the attached figure.


*         Do we need a method in our API to identify the media resource for which we are giving access to the metadata?

o   I guess that in an implementation we would get an object implementing the interface through a getMediaResource() method.
So maybe we can include in the API a method getMediaResource(URI) which would return an object implementing the API for the specified media resource.



*         Do we need a method in the API to identify the metadata of the media resource?

o   In some cases the media resource holds the reference to the metadata, in others the metadata holds the reference to the media resource, and probably there will be systems where the link between the metadata and media resource is managed in a higher level.

In this case we can add methods like setMetadataSources(URI[]) so that the user agent can at least find XML-files that hold the metadata, or get information on a specific web service that should be called to retrieve the metadata?

The second scenario also got me thinking.

*         There is no link between Web IDL and WSDL so I was wondering how this scenario would in fact be implemented? If such a web service is used the methods of the web service are not standardized, internally the calls to the API are standardized (if they are implemented in Java). However what would be the benefit in this case, I can assume that the web service would use the API to access different Media Repositories which brings us back to scenario 1 actually.


Seems that I am still missing the entire picture somehow so feedback on this is more than welcome!

Kind regards,
Chris

Ghent University - IBBT
Faculty of Engineering
Department of Electronics and Information Systems (ELIS)
Multimedia Lab Gaston Crommenlaan 8 bus 201
B-9050 Ledeberg-Ghent
Belgium

t: +32 9 33 14959
f: +32 9 33 14896
t secr: +32 9 33 14911
e: chris.poppe@ugent.be<mailto:chris.poppe@ugent.be>

URL: http://multimedialab.elis.ugent.be




-----------------------------------------
**************************************************
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
**************************************************