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

[Paul Libbrecht <[e-mail]>]

Le 25 oct. 2011 à 17:10, Frank Ellermann a écrit :

>> My usual suggestion is: what about clipboards?
> 
> Dunno, is there any problem with XML and clipboards?

None, except showing its source to users is ugly.

>> 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?
> 
> All I ever wish to do with OSDs is (1) edit some details,
> or wrt the security considerations inspect their source,
> (2) adopt an OSD when the auto-detect link rel="search"
> worked as it should, (3) click on an AddSearchProvider()
> EcmaScript link for cases where link rel="search" is no
> option.  Where do clipboards enter this picture for you,

Does it make sense to exchange them between two browsers?
The clipboard is a prime place for this.

> and is it relevant for the IANA media type registration?

This is the right place I believe.

> 
>> - Macintosh Uniform Type Identifier:
>> org.opensearch.description conforms to public.xml
> 
> Sadly I've no idea how Mac Uniform type identifiers work,
> and the info published in RFC 4288 convinced me that it's
> not something to worry about.  If you have any "official"
> public source that this is a well-known Mac id.

about OSDs? I do not think so.
About UTIs... start at wikipedia.

> I add it, otherwise I prefer to stick to what I could defend in an IETF Last Call.

I do not think there's a lot of danger involved.

>> - Similarly http://www.opensearch.org/ is rather a
>> volatile change controller.
> 
> This actually is the "change controller" for some years,
> but IANAL and certainly not speaking for A9.

But that is owned by A9...

paul