(Created page with '=Using DOAP for AboutData= This page contains an evaluation of the RDF-based DOAP file format for use as a storage for AboutData. ==The DOAP file-format=...')
|Line 67:||Line 67:|
This page contains an evaluation of the RDF-based DOAP file format for use as a storage for AboutData.
"DOAP is a project to create an XML/RDF vocabulary to describe software projects, and in particular open source."
The program name used internally. Example: "kedit". This property is not translated.
DOAP doesn't seem to have the notion of an internal name and would require an extension to its schema, eg.
<xdoap:internalName>Internal Application Name</xdoap:internalName>
Returns the application's product name, which will be used in KBugReport dialog. By default it returns appName().
While DOAP has a tag for linking to a bug tracker it doesn't allow us to specify the product and component to use for filing bugs. It would thus need to be extended, eg.
The translation catalog name; if null or empty, the appName will be used. You may want the catalog name to differ from program name, for example, when you want to group translations of several smaller utilities under the same catalog.
DOAP doesn't have the notion of translation catalogs and would require an extension to its schema, eg.
A displayable program name string. This string should be marked for translation. Example: ki18n("KEdit").
Defines the Internet domain of the organization that wrote this application. The domain is set to kde.org by default, or the domain of the homePageAddress constructor argument, if set.
AFAICT this is only used for deriving default D-Bus service names for the application. I don't think it makes a lot of sense to keep this information inside the AboutData storage.