On 1/14/06, Sam Ruby <[EMAIL PROTECTED]> wrote:
>
> Simply scheduling all Paces which are not obviously withdrawn, results in:
>
> = Currently Under Discussion By WG =
> PaceAnchorSupport
I thought we were in last call over APP paces, this pace
and PaceDifferentRelValue are autodiscovery Paces and
I believe they should be discussed on [atom-syntax].
> PaceCategoryListing
0
> PaceClarifyMediaResourceLinks
+1 With the caveat that while this does enable editing of metadata for
media resources, it also loses the ability to have
two different URIs for the media itself, on for the editable version
and the other for the read-only version.
> PaceClarifyTitleHeader
+1
> PaceDontUseContentSrc
-1 Metadata in not an 'alternate' for the media it is describing.
> PaceEditLinkMustToMay
+1
> PaceExamples05
+1
> PaceLinkIntrospection
-1 Autodiscovery is a separate spec for the format and it
should also be a separate document here also.
> PaceMissingDraftHasNoMeaning
+1
> PacePreserveForeignMarkup
+1 But incomplete since the spec makes no mention of server
handling of ForeignMarkup nor does it mention preserving
non-foreign markup handling of the client and server.
> PaceRemoveMemberTypeMust
-1
> PaceRemoveMemberTypePostMust
-1
> PaceRemoveTitleHeader
-1
> PaceRequestURI
+1
> PaceServiceMayHaveWorkspaces
-1
> PaceServiceShouldHaveWorkspaces
-1
> PaceSimpleIntroduction
-1
> PaceSparqlLink
-1
> PaceTitleHeaderOnlyInMediaCollections
+1
> PaceTwoPrimaryCollections
-1 This is already handled by saying that the first
collection of a type is considered the primary collection.
> PaceUseLinkHeaders
+1
> PaceWorkflows
+1
> PaceWorkspaceMayHaveCollections
-1
> PaceWorkspaceShouldHaveCollection
-1
And since this is feedback on -07, please add back in the
diagram [1] or write a Pace to have it removed.
[1]
http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-06.html#rfc.section.4
-joe
--
Joe Gregorio http://bitworking.org
