Re: Comparing tv_grab_zz_sdjson_sqlite & tv_grab_sd_json

--===============0888215108459718342==
Content-Type: multipart/alternative; boundary=001a1141e6ba382e41053e12cdcd

--001a1141e6ba382e41053e12cdcd
Content-Type: text/plain; charset=UTF-8

On Tue, Oct 4, 2016 at 6:10 PM, Robert Eden <[email protected]> wrote:

> On 10/4/2016 3:25 PM, Nigel Jewell wrote:
>
> .....
> tv_grab_zz_sdjson_sqlite output
>
> ...
>
>   <previously-shown start="*20110904 +0000*" />
>
>
> The DTD doesn't specify a value for start, but it would make sense to be
> similar to other time values in the DTD.  Technically this does seem to
> meet the DTD, but since the SD data doesn't actually include the timezone
> on the Original Air Date, +0000 is not necessarily accurate.   Probably
> best to leave out the timezone as other grabbers do.
>

The DTD does state:

"All dates and times in this DTD follow the same format, loosely based
on ISO 8601.  They can be 'YYYYMMDDhhmmss' or some initial
substring, for example if you only know the year and month you can
have 'YYYYMM'.  You can also append a timezone to the end; if no
explicit timezone is given, UTC is assumed.  Examples:
'200007281733 BST', '200209', '19880523083000 +0300'.  (BST == +0100.)"

I would assume that you should only append a timezone if you actually
included a time, although I guess that isn't strictly specified in the
DTD.  And since the Schedules Direct data only includes year/month/day the
xmltv output should only include year/month/day.

However, I have found that older versions of MythTV do not work correctly
if a time is not included for previously-shown. This is why in the
tv_grab_sd_json grabber I added a configuration option (not in the current
release) to use just the date (the default setting) or date and time (for
which noon in the local time zone is used).


Kevin

--001a1141e6ba382e41053e12cdcd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Oct 4, 2016 at 6:10 PM, Robert Eden <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:[email protected]" target=3D"_blank">[email protected]</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <div class=3D"gmail-m_106470799603057278moz-cite-prefix">On 10/4/2016 3=
:25 PM, Nigel Jewell
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      ..... <br>
      tv_grab_zz_sdjson_sqlite output <br>
      <br>
      ...<span class=3D"gmail-"><br>
      <p> =C2=A0 &lt;previously-shown start=3D&quot;<b>20110904 +0000</b>&q=
uot; /&gt;<br>
      </p>
    </span></blockquote>
    <br>
    The DTD doesn&#39;t specify a value for start, but it would make sense
    to be similar to other time values in the DTD.=C2=A0 Technically this
    does seem to meet the DTD, but since the SD data doesn&#39;t actually
    include the timezone on the Original Air Date, +0000 is not
    necessarily accurate.=C2=A0=C2=A0 Probably best to leave out the timezo=
ne as
    other grabbers do.<br></div></blockquote></div><br></div><div class=3D"=
gmail_extra">The DTD does state: <br><br>&quot;All dates and times in this =
DTD follow the same format, loosely based<br>on ISO 8601.=C2=A0 They can be=
 &#39;YYYYMMDDhhmmss&#39; or some initial<br>substring, for example if you =
only know the year and month you can<br>have &#39;YYYYMM&#39;.=C2=A0 You ca=
n also append a timezone to the end; if no<br>explicit timezone is given, U=
TC is assumed.=C2=A0 Examples:<br>&#39;200007281733 BST&#39;, &#39;200209&#=
39;, &#39;19880523083000 +0300&#39;.=C2=A0 (BST =3D=3D +0100.)&quot;<br><br=
></div><div class=3D"gmail_extra">I would assume that you should only appen=
d a timezone if you actually included a time, although I guess that isn&#39=
;t strictly specified in the DTD.=C2=A0 And since the Schedules Direct data=
 only includes year/month/day the xmltv output should only include year/mon=
th/day.<br><br></div><div class=3D"gmail_extra">However, I have found that =
older versions of MythTV do not work correctly if a time is not included fo=
r previously-shown. This is why in the=20
      tv_grab_sd_json grabber I added a configuration option (not in the cu=
rrent release) to use just the date (the default setting) or date and time =
(for which noon in the local time zone is used).<br><br><br></div><div clas=
s=3D"gmail_extra">Kevin<br></div></div>

--001a1141e6ba382e41053e12cdcd--


--===============0888215108459718342==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===============0888215108459718342==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
xmltv-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-users

--===============0888215108459718342==--