[ 
http://opensource.atlassian.com/projects/roller/browse/ROL-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

linda skrocki updated ROL-1358:
-------------------------------

    Fix Version/s: 4.1

> Minor Edit button in edit entry forms
> -------------------------------------
>
>                 Key: ROL-1358
>                 URL: 
> http://opensource.atlassian.com/projects/roller/browse/ROL-1358
>             Project: Roller
>          Issue Type: New Feature
>          Components: Newsfeed Aggregation, Weblog Editor
>    Affects Versions: 3.0
>         Environment: all
>            Reporter: Henry Story
>            Assignee: Roller Unassigned
>             Fix For: 4.1
>
>
> There is a serious need for a "minor edit" button on the editing forms, that 
> would allow an author specify that an update he is about to make is 
> insignificant [1], and so that the updated time stamp of the associated atom 
> feed should not be updated.
> Insignificant changes include things such as:
>    - html or markup fixes
>    - link renaming (perhaps a remote resource was moved, deleted, hijacked, 
> or some such...)
>    - minor spelling or grammatical corrections
>    - add or delete tags, or change the category of a post
>   ...
> Currently any of the above changes the update time stamp, which will appear 
> to many aggregators as spam. This is because people are interested in updates 
> to articles, be they blog articles or wiki articles [2]. But if absolutely 
> minor changes have the effect of changing the updated time stamp, then the 
> value of the updated time stamp is lost. Currently I am having this problem 
> with any minor edit affecting the panetrdf feed. [3]
> There is one very simple solution to this problem:
>  Add a "minor update" check box to the entry field. If checked the updated 
> time stamp does not get changed.
> The Atom Application Protocol does make an app:edited [4] time stamp 
> available, to allow clients to synchronise their state up to minor edits with 
> the server. This could also be made available in the server, and will 
> probably be important at some point in the future. This will require a change 
> to the database. This feature request does not require it.
> Henry Story
> [1] to use the terminology of Atom rfc 4287 
> http://www.atompub.org/rfc4287.html#element.updated
> [2] Tim Bray made the point in the atom application protocol mailing list 
> http://www.imc.org/atom-protocol/mail-archive/msg05601.html
> [3] http://blogs.sun.com/bblfish/entry/sorry_for_the_updates
> [4] 
> http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-13.html#rfc.section.10.2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to