[jira] [Comment Edited] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified

["Michael Osipov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219629#comment-15219629 ] 

Michael Osipov edited comment on DOXIASITETOOLS-164 at 3/31/16 9:16 AM:
------------------------------------------------------------------------

I don't like the commit and the approach. I will tell you why:

- Missing semantics make it impossible to use in a skin
- The new meta header is useless just like the previous one because there is no standard semantic for which search engines may read
- People are lazy and believe me, almost no one will update the date manually. People expect a CMS to do this for them: creation and modification date
- Pages are updated with releases only, it is quite irrelevant then when a document has been created or updated, it lives from release to release
- A clean approach would query Git/Subversion log, at best with an abstraction layer

At the end, I would deprecate and remove it after all in 2.0. The information is of little use for the rendered page. We should not ride a dead horse and try to revive it. Regarding parsing of files, simply abandon the value but do not fail.


was (Author: michael-o):
I don't like the commit and the approach. I will tell you why:

- Missing semantics make it impossible to use in a skin
- The new metaheader is useless just like the previous one because there is no standard semantic for which search engines may read
- People are lazy and believe me, almost no one will update the date manually. People expect a CMS to do this for them: creation and modification date
- Pages are updates with releases only, it is quite irrelevant then when a document has been created or updated, it lives from release to release
- A clean approach would query Git/Subversion log

At the end, I would deprecate and remove it after all in 2.0. The information is of little use for the rendered page. We should ride a dead horse and try to revive it. Regarding parsing of files, simply abandon the value but do not fail.

> don't use document date from Sink API as creation date but as "date" without precision on created or last modified
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DOXIASITETOOLS-164
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-164
>             Project: Maven Doxia Sitetools
>          Issue Type: Bug
>          Components: Site renderer
>    Affects Versions: 1.7
>            Reporter: Hervé Boutemy
>             Fix For: 1.7.1
>
>
> as seen in DOXIA-541, the meaning of the date is not defined in Doxia: then it seems it's up to the content writer to choose...
> and it was a wrong choice to name the content of date field of the document as {{dateCreation}} variable in DOXIA-315 / DOXIASITETOOLS-20 [r771801|http://svn.apache.org/r771801] in 2009
> let's start by showing the weak sematic before choosing what to do: creation date, last modification date, or even add some more features like multiple dates (for example "created : last modified")?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)