This template, but itself, creates an empty `<time>` element. It's depending on the `timeago` plugin to fill in the value later. I considered a different approach that is more robust, but does require extra work. The alternative is to initially fill in the time with a standard timestamp, so, e.g.:

```
<time datetime="${activity.published}">oae.api.l10n.transformDateTime(activity.published, true)</time>
```

This would provide a default value if, for some reason, `timeago` wasn't properly run on the template. Though not as user friendly as "time ago" value, it would show, for example:

> Stephen Thomas updated the file "Uploading a folder screen capture"
> 4/15/14, 6:55 AM

If we followed up on this approach, we'd also want to use a `data-` attribute rather than `datetime` to store the epoch milliseconds. HTML5 doesn't officially support epoch milliseconds so the current template isn't technically valid as HTML. That's not a problem so long as `timeago` runs, because `timeago` adjusts the `datetime` to make it valid.

Advantages of the alternative approach:

* The HTML output is both usable and valid if `timeago` doesn't run correctly.

Disadvantages of the alternative approach:

* Extra code to develop, test, maintain, etc.
* Excess markup (the `data-` attribute) remains in the page even though is no longer useful once `timeago` runs.

Easy enough to change to the alternative if it's desirable.