If we want to properly use a a value like "Microsoft", then adding "osvendor" instead of "vendor" for that could be a first step. If streamlining with OMA or similar standards is in the interest of downstream projects, that would be the next step. Either for a pending "1.0.1" update of the data artifacts in the near future or for one beyond.
Werner On Thu, Jul 31, 2014 at 9:50 PM, eberhard speer jr. <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > About the 'default', to be clear : > > I am referring to any value that is empty, '-', 0 [meaning no value] > and any property/value that represents a 'default' value. > Not only the properties that are 'meaningless' like nokia_version for > a desktop. > > Adding these generic 'defaults' may look impressive but the data is > meaningless fluff. > If the value for property xyz is not present, not known or is some > known default [you can spot them], it should not be included in the > response. > > That's an 'honest' response, in that the end-user now knows that any > property not present can default to something meaningful in their > current context, instead of having them 'run' with nonsense 'default' > data. > > That's an honest and much shorter response : all signal. > > esjr > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJT2p3uAAoJEOxywXcFLKYcIGwH+gL3Rs4Sx3/Va/Za1u7KyxSo > f4sT8PkBMRmGVsXQXMeCtU3fds0xwxzJHpEtpBRwWwUEkFrgpb4wV6CNLlrgNYO9 > +Pzdv75HOBzzpX8zj++cBuYUwuQyd5PAweRdrbu1PUeS7Pf3ltVOHpera8eKwh69 > Wb5zoXn9mLpr/hA4eRJqGkrQ0vNZclI9wctS5fb24Mod+CFcYBu/QXVqNEn7fFRM > V7pf68W+oMhYJWJ6t3VbBaTqIH8omuSgHavHclRf/lTeuaGb5cs7E9bFJ3Xa/SnV > bbMfTBwMf9AvMDxwheobCqojq2yjSZUNwu5wGqCMCEfoMzDBLVyHAXjcEOzASjg= > =5KkQ > -----END PGP SIGNATURE----- >
