productname
Synopsis
Mixed Content Model
productname ::= (#PCDATA|footnoteref|xref|abbrev|acronym|citation|citerefentry| citetitle|emphasis|firstterm|foreignphrase|glossterm|footnote| phrase|quote|trademark|wordasword|link|olink|ulink|action| application|classname|methodname|interfacename|exceptionname| ooclass|oointerface|ooexception|command|computeroutput|database| email|envar|errorcode|errorname|errortype|filename|function| guibutton|guiicon|guilabel|guimenu|guimenuitem|guisubmenu| hardware|interface|keycap|keycode|keycombo|keysym|literal| constant|markup|medialabel|menuchoice|mousebutton|option| optional|parameter|prompt|property|replaceable|returnvalue| sgmltag|structfield|structname|symbol|systemitem|token|type| userinput|varname|nonterminal|anchor|author|authorinitials| corpauthor|modespec|othercredit|productname|productnumber| revhistory|remark|subscript|superscript|inlinegraphic| inlinemediaobject|inlineequation|synopsis|cmdsynopsis| funcsynopsis|classsynopsis|fieldsynopsis|constructorsynopsis| destructorsynopsis|methodsynopsis|indexterm|beginpage)*
Attributes
Name |
Type |
Default |
||||
| class |
Enumeration:
|
"trade" |
Parameter Entities
The following parameter entities contain productname:
| Parameter Entities | ||
| %bibliocomponent.mix; | %docinfo.char.class; | %ndxterm.char.mix; |
| %para.char.mix; | %refinline.char.mix; | %tbl.entry.mdl; |
| %title.char.mix; | ||
Description
A ProductName is the formal name of any product. Identifying a product this way may be useful if you need to provide explicit disclaimers about product names or information.
For example, the copyright statement on this book includes the following general notice:
or words to that effect. If every product name in this book had been diligently coded as a ProductName, we could have automatically generated a complete list of all the product names and mentioned them explicitly in the notice.Some of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O'Reilly & Associates, Inc., was aware of the trademark claim, the designations have been printed in caps or initial caps.
In running prose, the distinction between an Application and a ProductName may be very subjective.
Processing expectations
Formatted inline.
Two of the values of the Class attribute on ProductName, Trade and Registered, make assertions about trademarks. DocBook also has a TradeMark element; presumably the same markup is intended regardless of which one is used.
The Service and Copyright values should also generate the anticipated marks, if appropriate.
![[4.0]](figures/rev_4.0.png)
Future Changes
The InterfaceDefinition element will be discarded in DocBook V4.0. It will no longer be available in the content model of this element.
Parents
These elements contain productname: appendixinfo, application, articleinfo, attribution, biblioentry, bibliographyinfo, bibliomisc, bibliomixed, bibliomset, biblioset, bookinfo, bridgehead, chapterinfo, citation, citetitle, emphasis, entry, foreignphrase, glossaryinfo, glosssee, glossseealso, glossterm, indexinfo, lineannotation, link, literallayout, lotentry, member, msgaud, objectinfo, olink, para, partinfo, phrase, prefaceinfo, primary, primaryie, productname, programlisting, quote, refentryinfo, refentrytitle, referenceinfo, refpurpose, refsect1info, refsect2info, refsect3info, refsynopsisdivinfo, remark, screen, screeninfo, secondary, secondaryie, sect1info, sect2info, sect3info, sect4info, sect5info, sectioninfo, see, seealso, seealsoie, seeie, seg, segtitle, setindexinfo, setinfo, sidebarinfo, simpara, subtitle, synopsis, term, tertiary, tertiaryie, title, titleabbrev, tocback, tocentry, tocfront, ulink.
Children
The following elements occur in productname: abbrev, acronym, action, anchor, application, author, authorinitials, beginpage, citation, citerefentry, citetitle, classname, classsynopsis, cmdsynopsis, command, computeroutput, constant, constructorsynopsis, corpauthor, database, destructorsynopsis, email, emphasis, envar, errorcode, errorname, errortype, exceptionname, fieldsynopsis, filename, firstterm, footnote, footnoteref, foreignphrase, funcsynopsis, function, glossterm, guibutton, guiicon, guilabel, guimenu, guimenuitem, guisubmenu, hardware, indexterm, inlineequation, inlinegraphic, inlinemediaobject, interface, interfacename, keycap, keycode, keycombo, keysym, link, literal, markup, medialabel, menuchoice, methodname, methodsynopsis, modespec, mousebutton, nonterminal, olink, ooclass, ooexception, oointerface, option, optional, othercredit, parameter, phrase, productname, productnumber, prompt, property, quote, remark, replaceable, returnvalue, revhistory, sgmltag, structfield, structname, subscript, superscript, symbol, synopsis, systemitem, token, trademark, type, ulink, userinput, varname, wordasword, xref.
Examples
<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<para>
<productname class='trade'>Frobozz</productname>: it's not
just for breakfast anymore.
</para>
Frobozz™: it's not just for breakfast anymore.
As noted above, the TradeMark element could also be used:
<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<para>
<trademark>Frobozz</trademark>: it's not
just for breakfast anymore.
</para>
Frobozz™: it's not just for breakfast anymore.