Does the use of MPEG-21 in AXMEDIS cut down the transportability of media among different devices and platforms? (...) Does the use of MPEG-21 DRM prevent the use of superdistribution in AXMEDIS? (...) The use of peer to peer technology at a B2B level may attract significant cultural resistance from content owners, who (rightly or wrongly) associate it with a lack of control over who can access their content. (...) One of the objectives of AXMEDIS is to reduce the cost of content creation and distribution. Although this may provide a long-term increase in the profit margin available to content owners, distributors and retailers, it is at the expense of what could possibly be a significant technology investment and carries a high risk of arriving too late to market. (...) One slight risk is on the decline in use of DRM (i.e., an acceptance of non-DRM formats by content owners) may diminish the perceived value of the project. Many record labels are experimenting with non-DRM formats and some analysts see this as the future of digital content. (...) Which is the business model of AXMEDIS ? (...) What will happen to the AXMEDIS framework and tools after the conclusion of the AXMEDIS project in the August 2008? (...) In the last years digital media industry has evolved significantly and I would have preferred to see more reference to new models of content production and distribution that are evolving. In particular the trend towards user-generated content deserved more attention. How AXMEDIS technology could be used to exploit such activities would have given the tutorials a more cutting edge feel. (...) What about at the DRM content where the license had been lost? (...) What about the usage of the MXF format? (...) AXMEDIS is adopting, more or less all the major available, proposed and de facto standards. By doing this, it doesn’t provide an effective contribution to standardization processes. Moreover the above mentioned huge number of standards makes the architecture very complex and difficult to be adopted. (...) The current approach assumes that AXMEDIS would constitute the foundation of automated content and metadata production as well as digital rights management. If adopted, this would be a major contribution. Other strategies such as interoperability with other DRM systems also need to be considered. (...) What are the protection models? (...) Can you in the same AXMEDIS AXCP Javascript broadcast to all channels ? (...) Is AXMEDIS DRM supported already? (...) When tracing content rights, how far is the user identity protected? (...) What about legal complications in different countries regarding rights? (...) What about DDEX standard with AXMEDIS architecture? It could be very good to integrate our own metadata and/or, DDEX, etc. (...) It could be very good to integrate our own metadata into AXMEDIS objects an use them in our applications and may be in yours. Should we come to AXMEDIS architecture, do you provide SDK or Web Services or some kinds of integration? (...) How do you see all these technologies moving into very broad mass market? (...) Does AXMEDIS get everybody sign into the consortium or do you license? (...) Are AXMEDIS tools available for research or commercial? (...) Are you using open source, and which one? (...) What is the IPR of AXMEDIS ? (...) Is the AXMEDIS Affliation programme successful? (...) What about the integration of Fair play? (...) Is there any integration with DMP? (... ) How about streaming of some formats like DVD? (...) Do you have different domains? (...) Do you need hardware for integration ? (...) Did you have any experiment with users? (...) Is AXMEDIS only research? (...) Have you succeeded in making MPEG21 usable? (...) Is there any component that convert an object to streaming? (...) Can I include an AXMEDIS player into our WEB application ? (...) Adopting AXMEDIS can we develop our own application and create our own environment as there are Web services and JS. (...) What about content processing capabilities of AXMEDIS? (...) Have you succeeded in making MPEG21 usable? (...) Can AXMEDIS Kiosk have more interactive content? (...) Do you have an AXMEDIS format? (...) Do you compute the thumbnails? (...) Do you compute the ringtones? (...) Are you supporting JPEG2000? (...) Do you compute the video previews? (...) What about encryption technology in AXMEDIS? (...)
| |
|
Question: What about encryption technology in AXMEDIS? Answer: The protection of content in AXMEDIS is performed with the so called AXMEDIS protection tools. Presently we have Protection tools for: DES, 3DES, RSA, etc. You can write your own AXMEDI protection tool by using so called AXMEDIS Plug in Development Tool Kit, SDK. |
|
Question: Do you compute the video previews? Answer: YES, the AXMEDIS Content processing can automatically compute previews from videos and include them in AXMEDIS objects and/or post them on WEB portal via web services, FTP, etc., send them via email, MMS, etc. |
|
Question: Are you supporting JPEG2000? Answer: Presently we are not supporting JPEG2000 into the players. It can be easily added into the AXMEDIS content processing and also into the players. In any case, nothing is preventing of including a JPEG2000 file into an AXMEDIS object, so that in this sense the JPEG 2000 is supported. |
|
Question: Do you compute the ringtones? Answer:
YES, the AXMEDIS Content processing can automatically compute ringtones and include them as preview in AXMEDIS objects or post them on WEB portal via web services, FTP, etc., send them via email, MMS, etc. |
|
Question: Do you compute the thumbnails? Answer: YES, the AXMEDIS Content processing can automatically compute thumbnails and include them as examples in AXMEDIS objects or post them on WEB portal via web services, FTP, etc. send them via email, etc. |
|
Question: Do you have an AXMEDIS format? Answer: AXMEDIS format is an ISO MEDIA format, the AXMEDIS format has been proposed as CMIP MAF standard at MPEG ISO. |
|
Question: Can AXMEDIS Kiosk have more interactive content? Answer: Yes, the AXMEDIS Kiosks may have any kind of AXMEDIS cross media content, the AXMEDIS format and model (mainly MPEG-21), a package that may contains/includes: metadata, identification codes, content descriptors, presentation layer with SMIL and/or HTML, style sheets, etc. javascript for coding the content behavior any other digital resource: images, video, documents, audio, games, data, xml, etc. any format in the same package. Nested AXMEDIS objects The content is interactive such as SMIL and HTML or MPEG-4. In addition, the content may be smart including javascript code for searching, automating the playing, etc. |
|
Question: Have you succeeded in making MPEG21 usable? Answer: YES, AXMEDIS is presently a complete end to end solution based on MPEG-21. It includes also tool for really massively producing MPEG-21 objects, distributing them ,and real players to use them. Player for the end user, that industries joining AXMEDIS can customize for their purposes or they can even use the standard one from the AXMEDIS portal. |
|
Question: What about content processing capabilities of AXMEDIS? Answer: The content processing capabilities of AXMEDIS are described into the Technical Note http://www.axmedis.org/documenti/view_documenti.php?doc_id=3624 other functionalities can be added adding AXMEDIS Content Processing Plug ins. You can write your own AXMEDI Content Processing tools by using so called AXMEDIS Plug in Development Tool Kit, SDK. |
|
Question: Adopting AXMEDIS can we develop our own application and create our own environment as there is Web services and JS. Answer: YES, the AXMEDIS Content Processing is open, it can be controlled via WS and can control WS etc. So that it can be easily integrated in your applications. See the technical note http://www.axmedis.org/documenti/view_documenti.php?doc_id=3455 |
|
| << Start < Prev 1 2 3 4 5 Next > End >>
| Results 1 - 11 of 46 |
|
|
INNOVAZIONE SELEZIONATA DA ITALIA DEGLI INNOVATORI 2011
|