Discussion on Profile Structure Point8

From wiki.gpii
Revision as of 17:25, 27 June 2013 by CStrobbe (talk | contribs) (category added)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

How to handle items that are duplicates: Identical meaning but a different name?

Status: Open

Note 2012-05-29 HDM: We don't need to decide this here, for the development of the standard.  Decisions will have to be made by the maintenance group watching over the CORE terms.

Discussion

Besides runtime conflicts as described in 27: How do we deal with conflicts in profiles? there might also be conflicts when organizing and maintaining the registry, for example as we import a non-core setting into the core-settings-space. There might be semantic duplicates when a third party registers a non-core preference which is ...

  • a duplicate of a core or another non-core preference
  • is a semantic subset of a core or another non-core preference
  • semantically contains a core or another non-core preference

These points should be taken into account and discussed in the registry discussion. They will probably have to be dealt with when migrating non-core preferences into the core or to emphasize matchmaking.

Example 1: Duplicate

We already have a core preference called "fontsize" and a third party uses a non-core preference called "font-size".

Example 2: Subset

We already have a core preference called "fontsize" and a third party uses a non-core preference called "use-large-font". The third party option is just a boolean and can only be used to distinquish between normal and large, while the core preference offers more precise settings.

Example 3: Contains

We already have a core preference called "fontsize" and a third party uses a non-core preference called "font-style". The third party preference is a complex string, containing fontcolor, fontsize, the actual font and more.

See Also