PaceRemoveRegistry

Abstract

Remove proposed IANA registry.

Rationale

The registry doesn't buy us anything, and isn't actually defined in draft-06.

Proposal

Delete from "7.3.4 The 'app:member-type' Element"

delete:

This specification defines two initial values for the app:member-type IANA registry...

delete:

In general the value of app:member-type MUST be a string that is non-empty, and matches either the "isegment-nz-nc" or the "IRI" production in [RFC3987]. Note that use of a relative reference other than a simple name is not allowed. If a name is given, implementations MUST consider the link relation type to be equivalent to the same name registered within the IANA Registry of Link Relations Section 14, and thus the IRI that would be obtained by appending the value of the rel attribute to the string "http://www.iana.org/assignments/member-type/".

It's been suggested that this Pace does not provide camera ready copy. That is incorrect. The element definition would read as follows:

7.3.4 The 'app:member-type' Element

The app:collection element MUST contain one 'app:member-type' element. The app:member-type element value specifies the types of members that can appear in the collection.

appMemberType =
   element app:member-type {
         appCommonAttributes,
         ( appTypeValue )
   }

appTypeValue = "entry" | "media"

An Entry POSTed to a collection MUST meet the constraints of the app:member-type element.

"entry" - The collection contains only member resources whose representation MUST be an Atom Entry. Further constraints on the representations of members in a collection of type "entry" are listed in Section 8.2.
"media" - The collection contains member resources whose representation can be of any media type. Additional constraints are listed in Section 8.3.

Notes

CategoryProposals