I'm not really familiar with C32, so I won't say -- but my strong guess is
labs should have a single effectiveTime point (not a low + high).


On Wed, Oct 9, 2013 at 11:41 AM, Tyler Hayes <notifications@github.com>wrote:

> In lib/c32/labs.js:
>
> > @@ -29,13 +29,17 @@ C32.Labs = function () {
> >
> >      for (var i = 0; i < entries.length; i++) {
> >        entry = entries[i];
> > +
> > +      el = entry.tag('effectiveTime');
> > +      var start_date = parseDate(el.tag('low').attr('value')),
>
> @jmandel <https://github.com/jmandel> Thanks. We'll add something like
> that. For this specific pull request then I'm curious if we should always
> assume C32 labs will have points, ranges, or never make an assumption and
> add logic that can dynamically parse either possibility (again, for C32
> labs specifically).
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/blue-button/bluebutton.js/pull/69/files#r6865682>
> .
>