Re: [ietf-types] Registration of media type application/opensearchdescription+xml

Frank,

My comments are that of a dilletante in the field. 
I hope someone will review the formal aspects of the procedure.

This is an interesting registration and it seems to be in good shape.

My usual suggestion is: what about clipboards? 
OpenSearch Description Documents sound to be a natural candidate to be exchanged in clipboards (be copied-and-pasted, be drag-and-dropped, ...). Do I mistake?
Hence I would like to suggest you add two lines in the additional information section such as the following:
- Windows Clipboard Flavor Name: "OpenSearch Description Document"
- Macintosh Uniform Type Identifier: org.opensearch.description conforms to public.xml

My guts feelings about the "responsibility" part of the registration is that it lacks a tiny bit of formality:
- isn't the WhatWG HTML a "place" for drafting a format that will hopefully end up be a W3C standard? I would prefer a W3C document to be referred to.
- a google-group as the contact is really volatile. Is there no way to put a legally registered entity instead? I think even a9.com would be better. 
- Similarly http://www.opensearch.org/ is rather a volatile change controller. Provided a domain is more or less what its whois entry is, it means A9.com is the controller (the registered company in the US). Rather say that.

paul

Le 20 oct. 2011 à 13:03, Frank Ellermann a écrit :

>   Type name:      application
> 
>   Subtype name:   opensearchdescription+xml
> 
>   Required parameters:
>                   There are no required parameters.
> 
>   Optional parameters:
>                   charset (defaults to "UTF-8")
> 
>   Encoding considerations:
>                   Identical to those of "application/xml" as described
>                   in RFC 3023; especially "UTF-8" (RFC 3629) and its
>                   proper subset "US-ASCII" are supposed to work.
>                   For non-ASCII documents served as "text/xml" the
>                   "charset" parameter is required; this might be
>                   relevant when authors are unable to configure the
>                   server hosting their OSDD (OpenSearch Description
>                   Document).
> 
>   Security considerations:
>                   All general security and privacy considerations for
>                   sending queries to servers specified in an URL are
>                   applicable.
> 
>                   Where clients support the optional update feature in
>                   OSDDs it affects the privacy of users.
> 
>                   The Ecmascript API AddSearchProvider() typically
>                   enforces a "same origin" policy for the OSDD; the URL
>                   element within the OSDD can designate a third party
>                   as search provider.
> 
>                   An OSDD can claim to be a search description for X,
>                   but actually do something else.
> 
>   Interoperability considerations:
>                   OSDDs use the <http://a9.com/-/spec/opensearch/1.1/>
>                   XML name space, optionally in conjunction with other
>                   XML name spaces for extensions or application specific
>                   purposes.
> 
>   Published specification:
>                   <http://www.opensearch.org/Specifications/OpenSearch/1.1>
> 
>   Applications that use this media type:
>                   Various Web browsers, search engines, and software
>                   libraries support OSDDs.  The "search" link relation
>                   is used on many Web pages with this media type.
> 
>                   The Ecmascript API AddSearchProvider() documented for
>                   WhatWG HTML uses this media type.
> 
>   Additional information:
>                   OSDDs have no "magic numbers" as defined in RFC 4288.
>                   There are no special "common file name extensions" for
>                   OSDDs, OSDDs are XML documents.  If specific extensions
>                   are desired ".a9.xml" (or similar) might do the trick.
> 
>   Person & email address to contact for further information:
>                   <http://groups.google.com/group/opensearch>
>                   <http://www.opensearch.org/Community/Guidelines>
> 
>   Intended usage: COMMON
> 
>   Restrictions on usage:
>                   None
> 
>   Author:         DeWitt Clinton
> 
>   Change controller:
>                   <http://www.opensearch.org/>
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types