There are cases where one might use the "vendor" attribute, too, e.g.
<operatingSystem id="Apple.iOS.1.0.0.0">
</operatingSystem>
in OperatingSystemDataSource.xml, but in other XML files inside the same
tag like <device> I would not use "vendor" for an OS where it actually
means device.
On Thu, Jul 31, 2014 at 11:14 PM, Werner Keil <[email protected]> wrote:
> Aspect is not new or unique to OpenDDR but defined by W3C DDR, see:
> http://www.maddr.org/ddrsimpleapi
>
> An aspect allows to group certain properties together, but their semantic
> meaning.
> So "vendor" in the Device aspect is just the same as "vendor" in the OS
> aspect, which is why additional values like "osvendor" or "os_vendor" (that
> is just a different way of calling it in non-core vocabularies) can be
> necessary.
>
> "Microsoft" works as "osvendor" but especially for a desktop computer the
> "vendor" should be blank unless you want to specify particular PCs by
> vendors like "Lenovo", "Acer" or "Dell"[?]
>
> Werner
>
>
> On Thu, Jul 31, 2014 at 10:39 PM, eberhard speer jr. <[email protected]>
> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Color me confused, but wasn't there such a thing as 'Aspect' in the
>> various standards ?
>> To whit, the W3C DDR Aspects : Device, Browser, OS.
>>
>> So Aspect qualifies Property, as in : Device Vendor, Browser Vendor
>> and OS vendor...
>>
>> If that's the case "os_vendor" is a travesty at best.
>>
>> esjr
>>
>>
>>
>> On 31/07/2014 23:22, Werner Keil wrote:
>> > 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:
>> >
>> > 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/
>>
>> iQEcBAEBAgAGBQJT2ql+AAoJEOxywXcFLKYcOfYIAKqkGN2kvF4kx+zMKhvbslvu
>> errQq9qqoxX1cXcpIvPwokv8NqDVS9iL4ufFzN25SnLflR6DuZHtlfwPp4bO2Krg
>> 8JfD1kFS6jr3yAizxdwr2jWrN+SVaEpFOZalpTuECE+YSQErmO4WTJ3ieBq4hrEA
>> AhyAkQmNskObvsk564kqLatGo4Tw8FZhi4loLlGKpSk/XnnEPHNRceVzhtIoX8sQ
>> xWMyDk9p/X7/msIQZGrRLk16d2Yc8oraMbUrZqZxUGx9D2sGoi3Rt5WFG2UBL2M4
>> EdnQAGoMJ6aUIKBDejD3B9YALwUaLudGL/CLuW25wTIgkkwQZjGVhVsb/Qz4Twc=
>> =eEaS
>> -----END PGP SIGNATURE-----
>>
>
>
