Subject: Re: [media-types] Request even more review for application/senml+xml and application/sensml+xml

From: Paul Libbrecht <[email-masked]>
Date: Tue, 1 Nov 2016 19:37:39 +0100

Hello Cullen,

it seems to me that all the content-types you have been describing about senML are candidate content types to be exchanged over the clipboard of a normal mobile or desk computer; e.g. from a reading app to another, … Do you agree on this?
If yes, then I’d like to recommend to add:
- MacOS Uniform Type Identiers
- Windows Clipboard Name
for each of the content-types.

If there is earlier experience in this realm, probably this should be taken, otherwise, I can probably suggest some clipboard names.
Standardising such at the Media-Type declaration level allows to set a reference frame so that other implementations can follow, just as the content-type name.

For examples of including this in the media-type registration, see that of SVG or MathML.

thanks in advance.

Paul

> On 31 Oct 2016, at 22:07, Cullen Jennings <[email-masked]> wrote:
> 
> 
> In the registration below, RFC-AAAA would point at an RFC based on draft-ietf-core-senml-04
> 
> 
>  Type name: application
> 
>  Subtype name: senml+xml and sensml+xml
> 
>  Required parameters: none
> 
>  Optional parameters: none
> 
>  Encoding considerations: Must be encoded as using
>  [W3C.REC-xml-20081126].  See RFC-AAAA for details.
> 
>  Security considerations: Sensor data can contain a wide range of
>  information ranging from information that is very public, such the
>  outside temperature in a given city, to very private information that
>  requires integrity and confidentiality protection, such as patient
>  health information.  This format does not provide any security and
>  instead relies on the transport protocol that carries it to provide
>  security.  Given applications need to look at the overall context of
>  how this media type will be used to decide if the security is
>  adequate.
> 
>  Interoperability considerations: Applications should ignore any tags
>  or attributes that they do not understand.  This allows backwards
>  compatibility extensions to this specification.  The "bver" attribute
>  in the senml tag can be used to ensure the receiver supports a
>  minimal level of functionality needed by the creator of the XML.
> 
>  Published specification: RFC-AAAA
> 
>  Applications that use this media type: The type is used by systems
>  that report e.g., electrical power usage and environmental
>  information such as temperature and humidity.  It can be used for a
>  wide range of sensor reporting systems.
> 
>  Additional information:
> 
>  Magic number(s): none
> 
>  File extension(s): senmlx and sensmlx
> 
>  Macintosh file type code(s): none
> 
>  Person & email address to contact for further information: Cullen
>  Jennings <[email-masked]>
> 
>  Intended usage: COMMON
> 
>  Restrictions on usage: None
> 
>  Author: Cullen Jennings <[email-masked]>
> 
>  Change controller: IESG
> 
> [W3C.REC-xml-20081126]
>             Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
>             F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
>             Edition)", World Wide Web Consortium Recommendation REC-
>             xml-20081126, November 2008,
>             <http://www.w3.org/TR/2008/REC-xml-20081126>.
> 
> _______________________________________________
> media-types mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/media-types