Professional Documents
Culture Documents
June, 2010
ISSUE Pg.
Personal account registration flow. 6
Software products legal questions and encryption regulations explanation 35
Maemo content type 37
New Taxonomy - new content categories supported by Ovi Publish. 38
Metadata details - New metadata collected added. 63
Ovi Store is Nokia's global application and content market reaching millions of Nokia users worldwide on Nokia devices
as well as through the Nokia device browser. Submitting content and applications to Ovi is done through a self-service
tool that provides publishers with an easy way to distribute and monetize their content.
Ovi is Nokia’s global brand for Internet services which currently includes Maps, Messaging (email and instant
messenger), Media (Ovi Store, Ovi Share and N-Gage), and Music. With the Ovi services catalogue continually
growing, Ovi will remain an increasingly powerful way for you to access and create content and services from a mobile
device, desktop computer or via the Web.
A consumer can experience the Ovi Store by easy access through browsing a variety of content. After choosing a
content item, the consumer simply clicks the download action button next to the item to initiate the download.
• Easy access to a single channel reaching millions of consumers around the world
• Monetize your applications and content with Nokia-provided billing
• Rewarding revenue share of 70% (for credit card transactions developers receive 70% of the end user price,
less applicable taxes; for transactions through direct mobile carrier billing, developers receive 70% of the end
user price, less applicable taxes and fixed operator billing charges)
• Fast time to market via self-serve publishing
• Sales and usage reports, updated daily
Publishing applications and content to the Ovi Store is done through a self-service tool, Ovi Publish, used by publishers
to register and upload content to the Ovi Store. Publishing your content makes it available for download and
consumption on Nokia devices worldwide.
To make your content available in the Ovi Store you can use our content intake portal at http://publish.ovi.com. Once
you’re registered as an Ovi publisher you can publish content to the Ovi Store.
Once your content has been successfully submitted into the publish interface, it is reviewed by Nokia for quality and to
ensure it meets Nokia Brand Guidelines.
2. PUBLISHER REGISTRATION
• Go to publish.ovi.com
• Click Register Now.
Personal Accounts are designated primarily for individuals that wish to distribute content. These accounts
cannot apply to be a Media Publisher
• Enter the information details for the Administrator of your company’s Ovi Publish account.
• Click Next.
Step 4/5
NOTE: The €50 charge is a non-refundable processing fee. Fields marked with an asterisk (*) are mandatory.
Step 6/6
2.2 Logging in
The Ovi Publisher Home page opens, giving you general information on the following:
• Your latest content updates
• A brief overview of how to publish content
• A list of important terms used when publishing content
• Links to information related to your account
When you receive your password for the first time you may want to change it to something that is easier to remember.
To change your password:
• Click Update.
Publishers that submit chargeable content to Ovi Store must provide their bank data details in order to receive payment
attributed to purchases of their content. Publishers that submit free content to Ovi Store do not need to provide this
information.
To provide your bank data details go to Payee Information page under the Account tab. Please contact your bank if
you need help gathering this information.
NOTE: In case you use an intermediary bank for depositing funds into your account from abroad, please
provide the intermediary details to Publishtoovi.support@nokia.com. Please include the following information: Bank
country, Bank city, Bank name and SWIFT code for both banks (intermediary and beneficiary.
Media Account publishers are allowed to publish the personalization content on Ovi Store which includes:
Audio, video, wallpapers, themes and maples.
Media Geo Account is intended for 3rd Party publishers who have geographic rights to distribute content, which may or
may not be exclusive, and is more generic by nature, such as popular ringtones. Content in this type of account is
limited by geographic region. The Ovi Store content team will select a limited number of Media Geo accounts in each
geographic region to ensure content quality and discoverability is maintained.
The goal of creating these accounts is to enable Ovi Store to provide optimum placement of your content in Ovi Store,
while ensuring maximum relevance for consumers.
There are certain files and creative materials that you must have ready and available when adding a new content item
for publishing. Submitted content files are checked in the QA process and must follow specific requirements.
This chapter provides information on those requirements:
• General guidelines on how to publish content to Ovi
• Examples of how content is presented in downloadable pages across the various Ovi Store touch points
• Information about the files used to create content including content file types, images and icons
The creation of images for content download pages should follow these general rules of thumb:
• Avoid using too much information over the images.
• Make sure any text on the image is readable. If not, do not use text.
• Do not use borders in the thumbnails.
• Violent, sexually explicit, or offensive images are not permissible.
In order to publish content to Ovi Store, the following items must be prepared in advance of the submission process.
These items include:
• Packaged application.
• If you’re submitting a Java application it will need to be packaged as a JAR and JAD pair and signed
appropriately. See section 5.2 for more information.
• If you’re submitting a Symbian application it will need to be packaged as a .SIS file and be Symbian Signed
(Express or certified).
• If you’re submitting a Maemo application it will need to be packaged as a .deb file
• If you’re submitting a Flash Lite application it will need to be packaged as a .SIS file and be Symbian Signed
(Express or Certified) if it’s for S60 devices. If it’s for Series 40 devices it must be published as an .NFL file.
• Images (used to visually represent your application experience to a consumer).: make sure you have all of the
necessary image sizes listed in section 4.4
• Icons; used to identify your application on a consumer’s handset.
• Name and description of the content item.
• A list of keywords to be used as metadata for your application enabling indexing and discovery via the Ovi
Store search functionality.
• Identify in advance the devices you wish to target with your content items.
http://www.forum.nokia.com/devices/matrix_oviStore_1.html
• Identify in advance the appropriate countries to which you will distribute your content. Please keep in mind that
content may be considered appropriate in some countries but not in others. For example, gambling and risqué
content is prohibited in some Middle Eastern countries.
GOOD BAD
EXAMPLE OF HOW TO
CROP AN IMAGE
GOOD BAD
EXAMPLE OF HOW TO
CROP AN IMAGE
GOOD BAD
EXAMPLE OF HOW
TO CROP AN IMAGE
There are only a small number of image and icon files that the publisher must supply. The rest are optional. In other
words, they can be generated by the system from the file supplied by the publisher or they are optional to the content.
The publisher can submit an image (for example, 256X256 pixels) and in some instances the system will resize it to the
correct pixel size depending on where the image will appear. Then the publisher can edit the image if necessary. The
file size of images must be as small as possible.
In addition to normal optimizations, there are other factors that can increase the size of an image and these must be
considered when creating images and icons:
• Transparency
• Amount of colors
• Gradients and complexity
Table 1 describes:
• The names of all the images and icon that can be used when creating new content
• The purpose of the image or icon
• Size in pixels of the image or icon
• If the image or icon needs to be supplied by the publisher
• If the system will generate it or not
• Any comments about the file
Icon- This icon / product logo is 96x96 Optional Yes Editable by the
96x96 shown when the end-user 10 (scaled down publisher after
navigates through the Bytes- from Icon - system has
store on Nokia touch 2MB. 256x256) generated it
screen devices. Square
Format:
JPG,
PNG
Icon- This icon / product logo is 85x85 Optional Yes Editable by the
85x85 shown when the end-user 10 (scaled down publisher after
navigates through the Bytes- from Icon - system has
store on QVGA resolution 2MB. 256x256) generated it
Nokia devices. Square
Format:
JPG,
PNG
Primary This screen shot image as 144x144 Optional Yes (scaled Editable by the
Screen shown below, appears as 10 down from publisher after
shot the first image in the Bytes- Primary screen system has
144x144 content item page on 2MB. shot 256x256) generated it
Nokia touch screen Square
devices. Format:
The screen shot should JPG,
depict the user PNG
experience of your game
or application.
Primary This screen shot image as 66x66 Optional Yes (scaled Editable by the
screen shown below, appears as 10 down from publisher after
shot the first image in the Bytes- Primary screen system has
66x66 content item page on the 2MB. shot 256x256) generated it
Nokia mobile XHTML Square
experience. Format:
The screen shot should JPG,
depict the user PNG
experience of your game
or application.
Secondar This screen shot image as 144x144 Optional Yes (scaled Editable by the
y screen shown below, appears as 10 down from publisher after
shot the second image in the Bytes- Secondary system has
144x144 content item page on 2MB. screen shot generated it
Nokia touch screen Square 256x256)
devices. Format::
The screen shot should JPG,
depict the user PNG
experience of your game
or application.
Secondar This screen shot image as 66x66 Optional Yes Editable by the
y screen shown below, appears as 10 (scaled down publisher after
shot the second image in the Bytes- from system has
66x66 content item page on 2MB. Secondary generated it
Nokia mobile XHTML Square screen shot
experience. Format:: 256x256)
The screen shot should JPG,
depict the user PNG
experience of your game
or application.
.
Tertiary This screen shot image as 144x144 Optional Yes Editable by the
screen shown below, appears as 10 (scaled down publisher after
shot the third image in the Bytes- from Tertiary system has
144x144 content item page on 2MB. screen shot generated it.
Nokia touch screen Square 256x256).
devices. Format::
The screen shot should JPG,
depict the user PNG
experience of your game
or application.
Tertiary 66x66 image shown in the 66x66 Optional Yes Editable by the
screen content item details page 10 (scaled down publisher after
shot and is used in thumbnail Bytes- from Tertiary system has
66x66 in high resolution mobile. 2MB. screen shot generated it
Square 256x256).
Format::
JPG,
PNG
Once you have successfully created your Publisher account and are logged in, you can start creating new content. A
content item is composed of:
• Metadata – Descriptive text or graphics included in content item or file. A content item contains one set of
metadata, which can be used by several files.
• File(s) – The actual content file, plus information for a selected distribution. There can be more than one file
per content item, for example, to support different devices.
The steps to adding content are listed here and described in further detail in this chapter:
• Getting started checklist
• Choosing a content type
• Selecting a channel
• Describing content
• Choosing a price point
• Adding metadata
• Adding a file
• Choosing distribution
• Submitting a file to a quality assurance (QA) check
To add new content to your content items:
• Refer to the getting started checklist in section 4.2 Content files to make sure you have everything.
• Click the Content tab.
• Click “New content item”.
To choose the type of content you want to create - Click the content type.
NOTE: The content types that are available to choose from may vary depending on the publisher type.
Personalization content, wallpaper, video, and ringtones will be available for media account publishers only.
In this chapter, the Symbian application is used as an example.
• Answer the legal questions to ascertain the technical parameters of the encryption used (if any), and the
purpose of that encryption. If an official classification is required, you will be prompted to submit a copy of the
ECCN provided by BIS. The form to be submitted is known as a CCATS. This is the official document used
by BIS to communicate the final classification of encryption items.
• Click Continue.
Only decontrolled or mass-market encryption items will be published on Ovi (ECCNs EAR99 or 5D992 respectively)
and Nokia reserves the right to refuse publication if the encryption item is not suitable or if inadequate information is
provided by the publisher. It is the publisher's responsibility to determine the technical parameters of any encryption
capability of those items submitted for publication on Ovi and to first obtain the necessary classifications and
permissions for export. This information should be provided to Nokia. If not already available, the publisher may be
required to first obtain an Export Control Classification Number (ECCN) from the United States Bureau of Industry and
Security (BIS) prior to publication on Ovi, even if the content is developed or distributed outside the United
States. Please refer to Section 17.7, Export Control, in the Terms and Conditions of the Ovi Publisher Agreement for
more details.
BIS regulates exports of products and technology, including software offered for download extra-territorially, i.e. outside
the U.S. An "export" is defined as the shipment, transfer, or electronic transmission, either from the U.S. to a foreign
country or within the U.S. to an embassy or affiliate of a foreign country. Posting software products to the Internet for
download constitutes an export even if the software is not ultimately downloaded. For more information about export
controls for encryption items, please refer to http://www.bis.doc.gov/encryption.
Metadata is descriptive text or graphics that is used to classify or define a content item or file. The content item
creation page requires to fill the mandatory metadata pertaining to the content you wish to sell on Ovi Store- display
name, description, Global price point, Preferred billing method, Support email address and website, content icon and
content screen shot.
On the content item tab you can edit the metadata you just entered on the previous content creation page and you may
add additional optional metadata such as secondary and tertiary icons. The next step after completing all content item
metadata is to upload the actual application. For a complete list of metadata, see section 9.
• To get context help about a field, move your mouse over the green question mark.
Table 2
Content type Possible content File extensions Maximum
areas currently supported File size
Symbian application Applications .sis .sisx 350 MB
(Symbian applications Games
must be Symbian Signed
to pass QA).
Java application (Java Applications .jar +.jad 2 MB
applications must be Games (both files are
signed to pass QA). mandatory for a
single Java content
item)
Web RunTime (WRT) Applications .wgz 2 MB
widget Games
Flash Lite application Applications .sis .sisx .nfl 2 MB
(Flash Lite applications Games Note: Currently SIS
must be Symbian Signed, files created with
express or certified, for the Adobe Mobile
S60 devices) Packager tool will
not be supported
and will be rejected
during the QA
process.
Audio Audio .mid .mp3 .mp4 .aac 35 MB
.amr
Ringtone Ringtone .mid .mp3 .mp4 .aac
.amr
Video Video .3gp .mp4 35 MB
NOTE: The categories shown reflect the Store's new information architecture. Consumers will continue to see
the old categories until a future release. For example though you may choose the "Books" category, your book
content will continue to appear under "Entertainment" until the version of store supporting this category is released.
The publisher chooses a global price point (price amount) to implement for the content. The pricing structure is based
on predefined price tiers where:
• The retail price of a content item is the same regardless of the payment method.
• For each price point Nokia has defined a global retail price. Additionally each price point may have country and
operator specific exceptions.
You can define the price point in the content item page.
The publisher selects a billing method by which the publisher prefers the end-user to purchase the content by. The
billing payment options are “Credit card & operator billing” or “Credit card only”.
NOTE: Your billing preference will be applied in most cases, but if your stated preference is NOT possible,
the system will default to an allowed billing method that will be presented to the end user. For example, some
operators may not allow credit card billing in which case operator billing will be used by default.
The file is the actual application or media content file you wish to publish on Ovi Store. In addition you will need to
provide related information regarding the file and select the target distribution (where you want the content to surface –
devices, countries and languages.
To add a file:
• Click “Upload file” in the notification massage or click on the content files tab.
• Enter the details of your file. Follow the instructions describing what each field is for.
Note: In this screenshot the content item selected was a Symbian application. The actual input fields and
information you see may vary depending on the content type you’re uploading.
NOTE: You can add numerous files to a single content item by clicking Add new file. All files in a
single content item share the same general and channels metadata.
File specific file metadata, for example, version, application UID are not shared.
You must choose the distribution compatibility for each file in your content item. The Distribution tab contains tabs for:
• Devices
• Countries
• Languages
You can choose the specific Nokia devices which are best suited for your content by selecting all devices or by
specifying devices individually.
Note: While operators are currently specified under each country, operator-specific distribution is not supported by the
Ovi Store. Content will not be available at all in that country, if operator specific distribution is selected. To make the
content available in the country of a specific operator - select the country.
Before a content item can be published, it must be submitted to a quality assurance (QA) for review. Once you have
added the distribution information you can check submit the file to QA.
• Click the File tab.
• Make any final changes to the general metadata if necessary.
• Click Submit to QA.
You will receive a confirming notification that the file has been submitted to QA..
If your content has global appeal and you wish to target territories that are language sensitive – you can make it easier
for end users to find your content by following these tips:
• Transliterate your content display name by changing the letters of the name into the corresponding characters
of the local language
• Localize the content description
• Translate your application interface into that language.
• Add content type information (e.g.: ringtone, theme, game etc) to your content description.
• Add the word “free” to your content description (but only if your content is indeed free!).
•
The translations of your metadata (display name and description) will appear to end users who have
chosen that matching language in their Nokia device settings (or in their device browser in the case of the
xHTML version of Ovi Store).
For applications that are audience (country and/or language) sensitive, translate the application itself so that end users
of the specific languages will choose to use it.
After translating the application, upload the different associated content files to the content item and target each
translated version to the appropriate distribution.
5. SECURITY
All content items submitted for publishing go through a quality assurance process. The main purpose of the the QA
review is to ensure consumers receive quality content and application experiences through Ovi Store. We also strive to
achieve fast publishing turnaround for developers. The best way to ensure your content is approved quickly is to test it
thoroughly on all target devices before submitting it to Ovi Store.
Nokia’s QA process consists of the performance of a number of tests as well as a review of legal and content
appropriateness on all items submitted by developers.
NOTE: Testing does not cover every aspect of the content experience or application functionalities, nor does it cover
all possible phone, operator and language combinations. Rather, we focus on the verification of basic or core
functionality. It is the responsibility of the content publisher to fully test, validate and sign their application content prior
to submission to the Ovi Store. Do not expect Ovi consumers and users to test your content for you. If you do, they
may not buy from you again!
As you prepare a file to be published, its QA status will pass through several states. Each state tells you where the file
is in the process and what, if anything, you need to do next to make sure the file is successfully published. The QA
states are:
• NOT SUBMITTED TO QA - A file has not yet been submitted to QA. The desired publisher action is to submit
a file to QA.
• PENDING - The file has been submitted to QA but is still in the queue for testing or in the QA process
• IN PROGRESS - The QA review process is currently taking place.
• FAILED - The file has undergone testing and was found lacking in functionality or compatibility. In the file view,
failed link, you will be able to see reason the file failed QA.
• PASSED - The file has undergone testing and was found to have good functionality and compatibility. The file
will be published to Ovi Store.
After the quality assurance process is complete you will receive an email stating the status of the item in the system. If
the QA fails, the reason and related test case will be provided by email.
Nokia tests content prior to publishing to ensure consumers experience the same level of high quality across all
content types in the Ovi Store. While it is expected that all publishers will thoroughly test their content and applications
on all target devices before submittal, if Nokia’s QA test process identifies any problematic content, the publisher of
that content will be notified with a summary of the test failure results. It is then the publisher’s responsibility to either
When you submit content for testing during the QA process there are factors that must be taken into account before
submission. The publisher must check that content meets these criteria before submission.
• Publishers must complete the content submission form and lock the file
• Device distribution must have at least one specific device selected with a proposed compatibility status of
FULLY TESTED per platform. You may also select to distribute in any country.
• Localization or language should be stated if applicable to ensure the right content is targeted to the right
market. You may select to distribute content without specifying target languages by selecting Works for all
languages.
• Only Nokia billing is accepted. If the content contains any other external billing solution it will be rejected.
• For signed content items, such as Symbian signed or Java Verified signed, channel specific metadata
information must be entered for the "End date for published content" field. The date entered should be no later
than the expiration date of the certificate.
• Tip for identifying the end date:
Java ME applications:
1. Open the JAD file with a text editor (e.g. notepad)
2. Copy the contents of the “MIDlet-Certificate-1-1:” field (text starting from the colon and ending to the
carriage return) and paste it to an empty text file.
3. Save the text file
4. Change the file extension to .cer
5. Open the file. The validity is presented in the “Valid from” field
SIS files (you can use the Signsis utility which is available with the Symbian development tools).
1. On command line the following is executed: "Signsis -op sis_file_name.sis"
2. The outcome has usually multiple certificates, the validity period here would be the first listed certificate with
the fields.
For example: Validity
Not Before: May 27 00:00:00 2008 GMT
Not After : May 27 23:59:59 2018 GMT
• Content that includes links to external sites will be rejected by QA.
• Symbian application submissions (of the .sis and .sisx file type) must be pre-tested and must fulfill the Symbian
Signed Criteria, which is available at: www.symbiansigned.com.
All applications submitted to the Ovi Store must be able to provide proof that Symbian Signed and Java Verified
requirements are met if requested. For more information, see http://forum.nokia.com/main/0,6566,22,00.html.
Nokia may require third party testing for applications. If the QA team receives content that frequently fails, it is the
publisher’s responsibility to submit information to Nokia that the content works. Third party testing may be required
as proof.
• Be touch enabled.
• Utilizes the full screen and be fully playable without the device's generic virtual d-pad.
• Ensure that the virtual d-pad is switched off by default.
•
6.3 Submission process
Resubmission process
If a previously submitted content item fails the QA process or if the publisher needs to make changes, the publisher
may unlock the content item, edit it and relock to resubmit to QA.
Content server failure policy
Once content has been submitted to QA, you can check the QA status of a content item or of individual files. To check
the status of a content item, open the Content Item tab.
Scroll down the Content Item tab to check the status of an individual file.
If you want more detailed information about a file’s QA status, click Details of file to open the File tab.
Table 3
Color Status description Status bar
Green Passed
Red Failed
Orange Pending
Blue In progress
Green border QA complete: Does not mean that file
passed the QA, just that the QA was
completed
Red border QA failed to complete the process
7. EDITING CONTENT
You can edit content at any time and during any content status.
Content item and content file/s can be edited independently of one another.
Editing content that is currently in the QA process – You may edit an item or file that is undergoing the QA review
process. This will however remove the item or file from the QA review process. After making the changes resubmit the
item or file to QA. This will restart the QA review process from the beginning. If your item or file is already published,
the published revision of the item or file will remain published until the edited revision is QA passed after which it will
replace the previous published revision in the store.
• Click the content item you want to edit. The Content Item tab opens.
• Select the field you want to edit and click on the Edit link.
To edit an existing file, go to the content files tab and click Edit file on the relevant file:
• Click View metadata.
• When your changes are complete, click ’Submit changes to QA’ for the QA review to start
In addition to the standard graphical and text-based promotion in Ovi Store, Nokia also offers
publishers the option to submit additional graphical and metadata assets (see below) that Nokia
can use to help elevate the publisher’s Brand and potentially drive additional downloads.
Each Spotlight placement enables a publisher to gain additional promotional push within a slot found in categories
across all Ovi Store platforms; Web, Mobile Web, and Mobile Client. Spotlights can significantly enhance content
visibility and download rates in Ovi Store. Spotlight placement is located at the top of each category area and provides
a larger thumbnail image and an additional line of text below the content item name.
Placement 1: Content Areas – appear in Device Client and XHTML experiences (5 Content Areas)
To take advantage of this promotional opportunity, publishers should ensure content is available for Nokia to select –
publishers should be sure to add the metadata shown in the diagram below to the <content title>. The Ovi Store team
will monitor your content’s performance for the duration of your Spotlight run.
NOTE: Content will be re-submitted through the QA and Moderation process after metadata is added prior to Spotlight
promotion.
The screenshot below highlights an area on Ovi Publish where publishers may upload images and copy for spotlights
promotion on device and on desktop. Please ensure all files are completed including those marked optional.
All companies wishing to sell or distribute content on Ovi store must first register at publish.ovi.com to become a
publisher. Once the company is verified and contract agreements are in place, new users can be added for that
company. A role is assigned to each user when creating an account.
When a publisher registers for the first time the first user created is assigned a cp_manager role. User roles determine
their access rights. The roles available include:
cp_manager – administrator access
• Can manage users
• Can edit publisher company information
• Can see agreements for that publisher company
• Can see all content items of any user in the company
• Can upload and edit all content items of any user in the company
• Can view the Ovi Reports of the company
cp_developer
• Can see all content items of any user in the company
• Can upload and edit all content items of any user in the company
cp_developer_limited
• Can see only that user’s content items
• Can upload and edit only that user’s content items
Anyone who is a cp_manager can add new users for their company. A cp_manager can create a user with a
cp_manager role.
Company information must be kept up to date. Anyone who is a cp_manager can edit company details.
For all financial related information, refer to the Ovi Store publisher Terms and Conditions at publish.ovi.com or at
https://publish.ovi.com/ndas/show_accepted_nda
For Ovi Store reporting information, see the Reporting Guide within the Ovi Publish support section. The Reporting
Guide explains: Calculations for revenue projection and Relationship between Downloads, Purchases and Projected
Revenue.
Icon - 46x46 Optional (Automatically generated and You may upload a None
scaled down from the 256x256 Icon) 46x46 specific icon.
This icon / product logo is shown when Size: 46x46. Image
the end-user navigates through the must be square
store on the Nokia mobile XHTML Format: JPG, PNG
experience.
This icon was automatically generated
and scaled down from the 256x256
Icon.
Primary Optional (Automatically generated and You may also choose to None
screen shot scaled down from the 256x256 Primary upload a 96x96 specific
96x96 Screen shot). icon.
Size: 96x96. Image
This screen shot image as shown must be square
below, appears as the first image in the Format: JPG, PNG
content item page, on QVGA resolution
Nokia devices.
The screen shot should depict the user
experience
of your game or application
Content item Represents the main entity that is published and includes the
metadata and files for different devices. For example, Nokia’s
Maps application.
Content type Describes what kind of digital media the content item is. For
example, Java application, audio file or theme.
CP Content Provider (Publisher)
Device The physical entity where the content item can be viewed. For
example, Nokia S60 phones.
Distribution The devices, countries and languages to which the file is
distributed. For example, Nokia N95 version for Europe only.
File The actual content file plus related information for a selected
distribution. For example, xxx.SIS, xxx.JAR.
Forum Nokia Nokia’s developer community and website where publishers can
get technical information about devices, support, resources, and
discuss ideas with other content creators.
http://forum.nokia.com
Metadata Descriptive text or graphics included in content item or file. For
example, name, description, icon.
Ovi Store The Nokia channel where a content item is published.
Ovi Store Publisher The tool used to publish a content item to Ovi Store.
Platform