"Knowledgeable" and AFAIK they would have to sign the Apache Contributor Agreement[?]
Werner On Fri, Jan 17, 2014 at 12:45 PM, eberhard speer jr. <[email protected]>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bertrand wrote : > "Could that be loaded in addition to what's under > data/device-data/src/main/resources/devicedata ? > > If Werner keeps contributing data in there, having two distinct data > sets that are merged might be the easiest." > > I totally agree, the OpenDDR resources, for example : > > <device id="SHV-E220S"> > <list> > <value>SHV-E220S</value> > </list> > </device> > > could be merged with DeviceMap specific tokens, like so for example : > > <device id="SHV-E220S"> > <list> > <value>SHV-E220S</value> > </list> > <dmap> > <value>SHVE220S</value> > </dmap> > </device> > > (just 'invented' stuff) > or some such simple structure. > > That way the resulting resources would be useable for the regex-based > 'old' OpenDDR code and the n-gram based new DeviceMap code. > > I think the main question, apart from the trivial issue of the final > merged format and the tags to use, is setting up the infra to maintain > the dmap data and giving 'knowledgeable contributors' access to the > maintenance tool. > After a one-time catch-up effort to iron out current problem areas, > with an average of 20-ish new devices per OpenDDR release and only a > very small percentage requiring 'correction', it should be fairly easy > to stay 'in sync'. > Some coordination with the OpenDDR maintainers would be very helpfull > - -- any suggestion, Werner ? > > As matters stand now, I 'only' have to add a front-end and > access-control to make the infrastructure I developed 'publicly' > accessible. > I have no problem making that infrastructure available via my site and > then, like OpenDDR contribute the merged data resources. > > If this construction is agreeable to all -- at least initially > until/if someone builds a similar infra on a platform more 'agreeable' > and accessible to all -- I say : onward and will make that available, > after login, to the contributors here. In that case you can expect the > 1st tools of this to become available towards the end of next week also. > > esjr > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (MingW32) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJS2RfUAAoJEOxywXcFLKYcsl8IAIrCIP2H+InaJDSa91r7TZbB > D30gazl+STkHMdi6zCic9juZSfiCjTS0aqFA4Y7HptD3Ni/UzIeViKQcPZ2oKmXR > 9fXrub37sDmgBbddp03YHAR3XHz0T8+7QpkJfQnAceYpucQDwYGZkyR6Fgziuxkv > ulvhrCvyIAlH78ZbH6/Ja971LYUB/5OGE2lGicIgKYSSp2lQfjpbEJj1SSVCOz43 > rNGU/lnchofdxRWnHCfUzHu58yyaX1jYjE3EUGUfsdjrVVPESbTuX/aaaKtNamNy > Jn9U9mso6SNeYU2mbgS5uTZqKf9TNLOjdiimfpnukTcdScyDUnZ8hwecQ/3haE0= > =v7cX > -----END PGP SIGNATURE----- >
