Many Atom-enabled tools have a need to control whether an entry is publicly-visible, or merely stored on the server in preparation for some future publication. This proposal defines an element for use in the APP to signal whether an entry is public.
The precise nature of "publicly-visible" is left to the implementation, but a loose definition is given, to the effect that the server should not include the entry in "public" resources.
The feature is common amongst Atom-enabled tools, but has no standard representation in Atom documents.
Insert a new subsection into the protocol spec, after section 6.2, called "Entry Properties" as follows:
6.3. Entry Properties
Besides those elements defined in the Atom format document (RFC xxxx), the following additional elements are defined for use within an atom entry element.
If present, the value of this element should be "true" or "false"; if absent, the value is effectively "false". The server SHOULD NOT reflect the contents or existence of a draft entry on any public (unauthenticated) resource.