[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222531#comment-15222531
]
Hervé Boutemy commented on DOXIASITETOOLS-164:
--
for Doxia 2.0, we have time to work on it, starting by checking how this date()
Sink API is used in every markup
then we'll see what we can do better than the current "date"
> 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)
[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222193#comment-15222193
]
Michael Osipov commented on DOXIASITETOOLS-164:
---
I agree here but if there is no semantics one cannot reasonably use it in our
skins and I guess that 90 % of the people use our skins and not customs one.
For a value which cannot reasonbly used, especially for SEO, *I would drop it
altogether*. People only look at "Last Published". They do not care when the
document has been modified last.
> 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)
[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220901#comment-15220901
]
Hervé Boutemy commented on DOXIASITETOOLS-164:
--
I agree in general with your remarks: the only part I'm not ok is "Pages are
updated with releases only": pages are updated or not with releases, they are
only published with releases (be it modified or not). And there is the case of
a site without code, which has no release (like Maven site or Doxia site)
IMHO, the issue has to be fixed in Doxia first, in every markup language): in
Doxia Siterenderer, it's too late to change anything
and definitely DOXIASITETOOLS-20 created a qui pro quo since it said the
semantics was defined when it was not, as the discussion on the mailing list
showed: for Dennis, apt date is clearly a modification date (even if not
exactly "last modified", but more "last sufficiently modified that the dev
takes time to update")
then the only solution I see is stop lying: document the issue and show that
Doxia document date is "a date" and that nobody agrees on general semantics
do you have any better idea?
> 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)
[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219629#comment-15219629
]
Michael Osipov commented on DOXIASITETOOLS-164:
---
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)
[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219473#comment-15219473
]
Hudson commented on DOXIASITETOOLS-164:
---
UNSTABLE: Integrated in doxia-all #284 (See
[https://builds.apache.org/job/doxia-all/284/])
[DOXIASITETOOLS-164] added documentDate variable, with it loose semantics (as
Doxia Sink date() API) and deprecated (and removed from default template)
dateCreation and revision date (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1737181])
*
./doxia-sitetools/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java
*
./doxia-sitetools/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site-macros.vm
*
./doxia-sitetools/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site.vm
* ./doxia-sitetools/doxia-site-renderer/src/site/apt/index.apt.vm
> 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)
[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217506#comment-15217506
]
Hervé Boutemy commented on DOXIASITETOOLS-164:
--
Yes, I'm thinking at it carefully to find the best option...
IMHO, dateCreation variable name and parsing the Doxia date (even if it was put
back as String) were mistakes (easy to say a few years later...)
if we:
1. remove that info from Velocity context, since we can't fill it
2. replace with {{documentDate}} variable and equivalent meta tag in default
site.vm
3. explain the situation in
http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/index.html#Site_Template
, ie the site developper has to make his own choice about the semantics
then we have something consistent and quite easy
it will let us time to improve the future:
- what if we propose content writers to write "created : lastModified" in their
APT header, ie both dates?
- what happens in other Doxia markiup languages (it seems to me apt is the only
format with such date)?
> 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)
[jira] [Commented] (DOXIASITETOOLS-164) don't use document date from Sink API as creation date but as "date" without precision on created or last modified
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216036#comment-15216036
]
Michael Osipov commented on DOXIASITETOOLS-164:
---
I understand but this remains unsolvable for the site creator. How do you want
to solve this?
> 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)
