Re: xmltv-users Digest, Vol 103, Issue 4
Gary Buhrmaster <[email protected]> Thu, 19 May 2016 07:52:50 +0000
| Newsgroups | gmane.comp.tv.xmltv.general |
|---|---|
| Message-ID | <CAMfXtQzed7P7hT0UjtdpdEpLnt2WWP+x_-X=Z46syvPuOXFh+w@mail.gmail.com> |
On Wed, May 18, 2016 at 6:18 AM, <[email protected]> wrote: ..... > Message: 7 > Date: Wed, 18 May 2016 01:18:06 -0500 > From: Robert Eden <[email protected]> > Subject: Re: [xmltv-users] tv_grab_na_sd (new grabber for your > consideration) ..... > I haven't tried the grabber yet, but I have a problem with the name (I > think Kevin's grabber had the same name and I objected to it then as > well. :) ) > > 1. The Schedules Direct JSON service is no longer just North America > 2. SD doesn't describe the data source as Schedules Direct has two, > SD-DD (used by na_dd, which *is* only North America), and SD-JSON. > > really the best name is taken.. tv_grab_sd_json.... so how about > tv_grab_sd_json2? (I'm open to better ideas) Ah, yes, names. The Shakespearean "Rose" problem. There are a couple of parts to my thoughts to the name issue. First, when this grabber was started, the data was na only. The name followed (so, think legacy). That does not indicate in any way that the name should continue, just explains from where it came. Secondly, while sd has stated they have data for other countries, I have had no independent validation from any alpha/beta testers in other parts of the world that the data is actually good (or, at least, good enough), unlike my validation in the us (na). "Trust, but verify" is a good rule to follow. Lastly, taxonomy. As the xmltv "standard" is to usually conform to the ISO 3166-1 alpha-2 country code or the exceptional reservations (with a couple of non-compliance examples), I guess that if the sd_json grabber is intended to work for sudan, such a name might be conceivably be appropriate, otherwise, such a name seems at least a little wrong. There is no formal "everywhere" country code in the specs, but there are a few user reserved codes. AA, QQ, XX, or ZZ are typically used for "unknown" or "unspecified" (mostly because they are in the user reserved name space groups, and easy to recognize as being special). And the last part of the grabber is typically the provider (such as atlas, or rt). sd still sounds correct for the provider (and sd_json seems to me like a grabber for the sudan which uses the json epg provider). Does the project community have a strong consensus on the choice of universal/unalighned country code? I sort of trend to zz. Once I receive validation that the data is "good" (or at least good enough) from outside of NA I can see promoting this grabbers name to something of the form tv_grab_zz_sd, which seems to me to be a more appropriate name that is in alignment with the usual suspects. ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j