Application for addition to Atom Registry of Link Relations
The following is an application for a link relation value, as specified in the Atom Syndication Format. https://datatracker.ietf.org/public/idindex.cgi?command=id_detailfilename=draft-ietf-atompub-format https://datatracker.ietf.org/public/idindex.cgi?command=id_detailfilename=draft-ietf-atompub-format Thank you - James Snell == Registry == http://www.iana.org/assignments/link-relations == Attribute Value == license == Description == http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-license-03.txt == Display Characteristics == http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-license-03.txt == Security Considerations == http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-license-03.txt
Re: Application for addition to Atom Registry of Link Relations
Antone Roundy wrote: The following two bits seem incompatible with each other: o atom:entry, atom:feed and atom:source elements MUST NOT contain more than one 'license' link relation with the same combination of type and hreflang attribute values. Note the caveat, with the same combination of type and hreflang attribute values. The idea is to prevent a single license from being appearing more than once. Multiple license link relations MAY be used to indicate that the informational content has been published under multiple copright licenses. In such instances, each of the linked licenses is considered to be mutually exclusive of the others.
Re: Application for addition to Atom Registry of Link Relations
On 22/10/05 4:48 AM, James M Snell [EMAIL PROTECTED] wrote: Note the caveat, with the same combination of type and hreflang attribute values. The idea is to prevent a single license from being appearing more than once. Multiple license link relations MAY be used to indicate that the informational content has been published under multiple copright licenses. In such instances, each of the linked licenses is considered to be mutually exclusive of the others. but the second bit of text suggests that the following is allowable: link rel=license href=pay-me-for-commercial-use / link rel=license href=barter-for-commercial-use / link rel=license href=free-for-non-commercial-use / which is a situation which should be allowable (IMHO), and so the restriction should be removed: o atom:entry, atom:feed and atom:source elements MUST NOT contain more than one 'license' link relation with the same combination of type and hreflang attribute values. e.
