[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on creation 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=15214551#comment-15214551 ] 

Michael Osipov commented on DOXIASITETOOLS-164:
-----------------------------------------------

Even if we would degregate it to {{documentDate}} how it the skin provider supposed to know what the author had in mind? Semantics should be obvious somewhere otherwise there is no need to have this value in the Velocity context at all but leave it to the APT file only. Even then, it would serve no purpose because you always have a Subversion/Git log for that file. So at the end, abandon it altogether?

> don't use document date from Sink API as creation date but as "date" without precision on creation 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)