1. Is HAVi just a standard or a full object code for several platforms?
   
   
2. What does "HAVi compliance" mean?
   
   
3. What must device makers and third-party software vendors do to produce HAVi-compliant devices and applications?
   
   
4. What are the advantages of HAVi-enabled devices?
   
   
5. Who will write HAVi applications? How can these be updated?
   
   
6. Who will develop DCM/FCMs?
   
   
7. What FCM APIs are defined in the HAVi specification?
   
   
8. Can a developer define an FCM if current standardized FCMs (VCR, Tuner, Webproxy, etc.) do not meet their needs?
   
   
9. Is there an FCM Manager similar to DCM Manager?
   
   
10. Does HAVi specify standards for DCMs on LAV devices?
    
    
11. Will HAVi API be modified in future versions? As the HAVi API's are improved/updated, will the older API's and applications become incompatible with newer versions?
    
    
12. What is the schedule for HAVi and HAVi products?
    
    
13. Won't the overall hardware costs be very high, since a controller (with a fairly big display) would be required?
    
    
14. What are the changes between versions 0.8 and 1.0 beta, and versions 1.0 beta and 1.0?
    
    
15. What is the status of the HAVi plugfest?
    
    
16. What is the status of compliance related documents?
    
    
17. How can one obtain the HAVi specification document?
    
    
18. What is the license policy/fee for HAVi development?
    
    
19. Are there any books regarding HAVi?

HAVi puts forward a set of platform-independent APIs (in the form of HAVi specification document) that allow licensed developers to easily develop home-networking applications. HAVi does not put forward a standard object code; the implementation of the HAVi software stack is left to each company, with the condition that the implementation must be fully compatible with the HAVi specification (see Compliance section??).

A "HAVi compliant" device will:

• Support IEEE-1394
• Provide HAVi SDD data in IEEE 1212 configuration ROM
• Support IEC 61883
• Conform to the standards of the HAVi Compliance Test Specification

Device makers must:

• Ensure that their devices are IEEE-1394 compatible.
• Incorporate HAVi SDD data (such as device class) inside the configuration ROM.
• Make DCM/FCMs (and optionally, GUI), for operating the devices available.
• Incorporate the HAVi device class software elements.

Third-party software vendors should:

• Ensure that the DCM/FCM and applications they write using the HAVi API's satisfy all the requirements specified in the Compliance Test Suite documents.

The HAVi specification offers advantages for both the end user and the device manufacturer.

Some advantages for Developers:

• Develop home-networking applications easily by using the platform-independent HAVi native API or Java-binding HAVi API.
• Create new digital AV products covering a wide cost/functionality spectrum based on HAVi scalability.
• Exploit the advantages of IEEE-1394, such as plug-and-play and fast data transfer.
• Explore new business opportunities writing compatible applications for devices from other manufacturers.

The HAVi Specification was developed for home entertainment AV networks, providing high bandwidth for transmitting multiple AV streams and featuring easy "plug-and-enjoy". The HAVi specification allows for automatically detecting devices on the network, coordinating the functions of various devices, installing applications and user interface software on each device, and ensuring interoperability among devices regardless of manufacturer.

HAVi applications can be written by device manufacturers, third-party software developers, and service providers.

These applications can be updated in two ways:

• The standard method in HAVi is to have the application downloadable from a URL or cable service provider, and run on the Java virtual machine (JVM) inside an FAV device.
• Non-standard (i.e. proprietary) methods in which the application could be introduced into the HAVi device would be via PCMCIA Flash-ROM card, MO disk, floppy-disk, etc.

Since developing the DCM/FCM requires knowledge of the underlying hardware and software of the device, it would logically be developed by the device makers themselves, or third-party software vendors who have licensing agreements from the device maker.

The following FCM APIs have been defined in the HAVi specification:

• Tuner
• VCR
• Clock
• Camera
• AVDisc
• Amplifier
• Display
• AVDisplay
• Modem
• WebProxy

Yes, developers can define their own FCM APIs. However, these new FCM API's must be made available for other developers, by licensing them to application developers, or making them publicly open.

Developers can also join the HAVi organization and propose these API's for inclusion in the HAVi specification.

No, there is no FCM Manager, because the DCM Manager installs the DCM, and the DCM itself installs the FCMs.

Standardization of the DCM for LAV devices falls outside the scope of HAVi, and so it is left to the device manufacturer to provide proprietary DCMs.

As the official release of the specification evolves, it is intended that no APIs will ever be updated or removed. All changes will be achieved by adding new APIs. This ensures that older components can always request services from newer components successfully. Therefore, the applications will remain compatible.

The finished HAVi v1.0 specification is now available. The licensing program has commenced and interested parties can apply for a license.

Each manufacturer or software developer will determine their own schedule for product development and market introduction.

Since HAVi provides the following flexibility to developers, device cost can be kept low:

• Developers can build cheaper controller devices in the form of IAV devices.
• The HAVi output device model allows developers to display text-based control panel.
• When graphics-based GUI's are to be displayed, very few fields are mandatory -- many fields are optional, allowing the costs to be kept down.

The main changes between versions 0.8 and 1.0 beta are as follows:

• Java bytecode has been selected as the standard format during uploading
• APIs for new FCMs have been added
• Security has been added
• Connectivity with external networks (e.g. Internet) has been incorporated
• APIs for GUI have been added. Between versions 1.0 beta and 1.0, there are almost no changes to the APIs themselves, only their operation has been thoroughly verified via plugfest.

The initial "plugfest" regarding HAVi system software elements (such as CMM, Messaging System, etc.), various FCMs (Tuner FCM, VCR FCM, etc.) and Java-binding of HAVi APIs were completed in 1999 prior to the completion of the v1.0 specification.

The HAVi Organization may schedule additional technical sessions and "plugfest" opportunities for new members. The technical agenda of the HAVi Organization has not yet been published.

Compliance Test Suite document consisting of "Test Requirements" and "Test Cases" has been completed and is available for download.

Download it now.

Licensing for the HAVi specification is handled through Royal Philips Electronics on behalf of seven of the eight Promoter companies who co-created the HAVi Specification. (more information about THOMSON Multimedia's licensing policy)

• One-time license fee of US $5,000.
• US $0.10 per product.

Yes. A book titled "HAVi Example by Example" has been published. HAVi Example by Example introduces the programming interface packages and steps the reader through a wide range of examples. This book is intended for readers with an interest in Java programming or those intrigued by new home entertainment applications. Please check the following link for further information: http://www.vividlogic.com/hbx/