Java Embedded @ JavaOne 2012 Call for Papers
is Closed

The Call For Papers for Java Embedded @ JavaOne is now closed. Thank you all very much for your interest in the Java Embedded @ JavaOne conference.

To learn more about the Call-for-Papers, see the information below.

Tips and Guidelines for Paper Submissions

The following information provides general guidelines for submitting papers for Java Embedded @ JavaOne 2012. Providing such information does not guarantee that a submission will be accepted by the conference review committee.

General Tips

  • Session title should be descriptive of the session content and use common keywords. Example of a descriptive title: Balancing Replication and Partitioning in a Distributed Java Database. Example of a non-descriptive title: JavaFX and You.
  • Write an abstract that is easy to read and describes the value of the presentation for attendees. Do explicitly mention what is being discussed during the session rather than making a blatant marketing pitch.
  • For example, include mention of a product demonstration, case study, customer/partner participation, quantitative information, etc.
  • Use the present tense in session descriptions. For example, "In this session, hear how a leading utilities company uses Java Embedded applications to..."
  • Select values and tags that are accurate and will help attendees identify your content during a search.
  • Do not use the first person (I, our, we).
  • Do not include proprietary or confidential material.
  • Submitter must secure necessary permissions for use of proposed presentation materials before submitting.
  • Oracle reserves the right to edit all content. Abbreviated Oracle product names and unacceptable acronyms will be spelled out in the editing process and will count towards the character limits.
  • Standard presentations will be 60 minutes. We suggest allocating 10 minutes for a Q&A period within that timeframe.
  • It is not necessary to submit multiple entries on the same topic; all submissions will be reviewed centrally. For example, do not submit the same entry as a customer and then as a user group member.
  • Verify your contact and content information before submitting.

Tips for Titles and Abstracts

  • Observe the character counts for session titles and abstracts. Session titles are limited to a maximum of 80 characters, including spaces (approximately 12 to 17 words, on average). Session abstracts are limited to a maximum of 750 characters, including spaces.
  • You must use complete Oracle product names at all times.
  • You may not create acronyms or abbreviations of Oracle product names.
  • In general, you may not use acronyms in session titles and must spell out acronyms at first use in abstracts. Because of title and session length restrictions, some widely accepted industry acronyms are acceptable (for example, SOA or SaaS). Less commonly known acronyms will be spelled out in the editing process and will count towards your character limits in titles and abstracts.