New AtomPubIssuesList for 2004/09/24

[Sam Ruby <rubys@xxxxxxxxxxxxxxxx>]

For starters, PaceDatePublished is the Date proposal for this round. 
Tim suggested he would support it if the date were made optional, but 
even without Tim's support, this proposal has the most listed supporters 
of the remaining date proposals.

I agree with Tim that we seem to be converging on how to deal with the 
"textual" elements, so I am putting this back out for discussion.  For 
my part, I'm withdrawing PaceContentAsTextOrHtml.  Hopefully, we can get 
more proposals closed, and any issues that may exist on the remaining 
proposals come in the form of either new proposals or modifications to 
existing proposals.  The content related proposals scheduled for this 
cycle are as follows:

  PaceContentSrc
  PaceNukeMultipart
  PaceReformedContent
  PaceReformedContentRedux
  PaceSimpleContentType

Reviewing the ID related proposals, it occurred to me that 
PaceIdConstruct got partially incorporated; making all of the existing 
ID related Paces obsolete.  It seems to me that the workgroup would be 
best served by retiring the existing paces and soliciting proposals 
relative to the current document.  This can be accomplished by either 
updating the existing Paces (in which case, I'll move it back into an 
active status), or by opening up a new Pace.  The paces affected are:

  PaceBasicAtomID
  PaceComparingIds
  PaceCanonicalIds
  PaceIdConstruct2
  PaceRecommendIdScheme

Finally, PaceHeadInEntry has never been scheduled before, so I've put it 
on the list.

I don't feel guilty about not scheduling any protocol related Paces as 
the atom-protocol mailing list seems to be fairly active at the moment.

- Sam Ruby