So im going to jump in early in this thread and just give my comments: ua-prof: definitely. The ua-prof for a device sometimes has upto a hundred properties for said device. I dont think we should consider putting all those detailed properties in our DDR, ex: audio hardware and specifications. So by supplying the ua-prof, that can complement our data and allow the user to then query that data source to get these detailed or extended properties. As for multiple ua-profs for 1 device, that seems odd, each device should have 1 ua-prof from the manufacture?
As for the ddr_ properties, those all look good for *client* response values. If you look at my dClass plugin, i kind of started going down this path. I always return the dClass version (dClass 2.2.4) and I also have a comment field for each index and for the devicemap/ODDR index, it contains the version (OpenDDR 1.27). http://www.rezsoft.org:9000/uadiag Guid: well, we already have an "id" field which should be unique. The nice thing about it is that its human friendly. A 32bit (or 64, 128) GUID is not at all human friendly. ________________________________ From: eberhard speer jr. <[email protected]> To: "'[email protected]'" <[email protected]> Sent: Sunday, August 24, 2014 1:29 PM Subject: Data 2.0 - Vocabulary Properties : ddr_ and guid -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, since we're adding anyway ;-) here are some more 'new' properties I'd like to propose : ddr_ : properties pertaining to the DDR responsible for the 'response' ddr_vocabulary : Vocabulary Name [example : DeviceMap] ddr_api : version number of the API used to create the response ddr_version : data resources version number ddr_date : release data of the data referenced in version number guid : a *unique* identifier use-case : user queries DDR, gets a response, [user may save the response], later user re-queries the DDR and gets a *different* response. The guid tells the user both are responses to the same request, when properties [or their number] change over time. Comments ? esjr -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT+iD7AAoJEOxywXcFLKYccmoH/iCGCVUnImwAwbReHKHo2TuB JKrF+5IEW/vMRV2dxzj/qD54WfJRcK75WtR1yFwicDOzlPf1i4e34rqnF7kO+8P5 QNc7MxqnWZOvrQeoYltV0u0fjZ4qsv4pRAFU9DNrVwQRJq2v5TILAvk+LFilMyaY TxeHh7b5VdZooyd8fnhKe24xR1FY/BVikrXZdpEUyyetq6Pm/RJNKuM8FYsx+F2w 8eCdfVgYobDlS0/KspBZlCDebPviW/InQyNeFme+2u5pnEFQmlKcc0Rr7UkVDJfD FmhIiwinHFFgN1SVUK/Q7mooUeA26demAimzxiGQA7Pob4GAjK0QFHy2dS5ZIfo= =ud/o -----END PGP SIGNATURE-----
