The discussion continued on chat, leading to the following conclusion.
First, each template is meant to represent a certain class of devices
with the same settings (but see below for the current status). If there
is a name for that class that can be presented to users (think "Nokia
S40"), it is added to the template's meta data (template.ini) as
"templateName". This is optional. There might be templates which only
match one specific model or where the class is so obscure that showing
it is useless.
Second, we need to find better ways of determining the exact
manufacturer and model (Moblin Bugzilla #10380). Right now, we only have
the device name chosen by the user, which may or may not contain the
model. If (and only if) the exact model can be determined, it will be
added to the templates returned via D-Bus as the new "modelName"
property ("Nokia 7210c").
Third, "fingerPrint" in the template meta data is a list of
"Manufacturer Model" strings. This is what the exact model name (if
available) or the device name (fallback) are matched against by the
D-Bus server to rank templates.
Currently we have neither "templateName" nor "modelName". As the
short-term solution, the sync-ui uses the first entry in the fingerPrint
property and shows it to the user ("We think your device is a 'Foo Bar'.
If this is not right, ..."). This implies that right now, templates have
to be define per model, not per class.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.