Re: Registration of the application/ld+json media type

This media type has been submitted. I apologize about the delay.


Here is the registration form result:

-------- Forwarded Message --------
From: IANA MIME Requests via RT <iana-mime@iana.org>
> Reply-to: iana-mime@iana.org
> To: plh@w3.org
> Subject: [IANA #688368] AutoReply: Request for MIME media type
Application/Standards Tree -
> Date: Fri, 7 Jun 2013 03:31:37 +0000
> 
> To whom it may concern:
> 
> This is an automatically generated message to notify you that we have
> received your request, and it has been recorded in our ticketing
> system with a reference number of 688368. To check the status
> of your request, please see:
> 
> https://tools.iana.org/ticket-status/app
> 
> If you have any problems accessing this page, please contact
> iana@iana.org.
> 
> There is no need to reply to this message right now. IANA staff will
> review your message shortly.
> 
> If this message is in reply to a previously submitted ticket, it is 
> possible that the previous ticket has been marked as closed. As we 
> review this ticket, we will also review previous correspondence and 
> take appropriate action.
> 
> To expedite processing, and ensure our staff can view the full
history 
> of this request, please make sure you include the follow exact text in
> the subject line of all future correspondence on this issue:
> 
>          [IANA #688368]
> 
> You can also simply reply to this message, as this tag is already in 
> the subject line.
> 
> Thank you,
> 
> The Internet Assigned Numbers Authority
> iana-mime@iana.org
> 
>
-------------------------------------------------------------------------
> 
> Name : Philippe Le Hegaret
> 
> Email : plh@w3.org
> 
> MIME media type name : Application
> 
> MIME subtype name : Standards Tree -ld+json
> 
> Required parameters : None
> 
> Optional parameters : 
> profile
> 
> A a non-empty list of space-separated URIs identifying specific
constraints or conventions that apply to a JSON-LD document according
[RFC6906]. A profile does not change the semantics of the resource
representation when processed without profile knowledge, so that clients
both with and without knowledge of a profiled resource can safely use
the same representation. The profile parameter may be used by clients to
express their preferences in the content negotiation process. It is
RECOMMENDED that profile URIs are dereferenceable and provide useful
documentation at that URI. For more information and background please
refer to [RFC6906].
> 
> This specification defines three values for the profile parameter. To
request or specify Expanded JSON-LD document form, the URI
http://www.w3.org/ns/json-ld#expanded SHOULD be used. To request or
specify Compacted JSON-LD document form, the URI
http://www.w3.org/ns/json-ld#compacted SHOULD be used. To request or
specify Flattened JSON-LD document form, the URI
http://www.w3.org/ns/json-ld#flattened SHOULD be used. Please note that,
according [HTTP11], the value of the profile parameter has to be
enclosed in quotes (") because it contains special characters and, if
multiple profiles are combined, whitespace.
> 
> When processing the "profile" media type parameter, it is important to
note that its value is contains one or more URIs and not IRIs. In some
cases it might therefore be necessary to convert between IRIs and URIs
as specified in section 3 Relationship between IRIs and URIs of
[RFC3987].
> 
> 
> Encoding considerations : 8bit
> 
> 
> Security considerations : 
> Since JSON-LD is intended to be a pure data exchange format for
directed graphs, the serialization SHOULD NOT be passed through a code
execution mechanism such as JavaScript's eval() function to be parsed.
> JSON-LD contexts that are loaded from the Web over non-secure
connections, such as HTTP, run the risk of modifying the JSON-LD active
context in a way that could compromise security. It is advised that any
application that depends on a remote context for mission critical
purposes vet and cache the remote context before allowing the system to
use it.
> Given that JSON-LD allows the substitution of long IRIs with short
terms, JSON-LD documents may expand considerably when processed and, in
the worst case, the resulting data might consume all of the recipient's
resources. Applications should treat any data with due skepticism.
> 
> Interoperability considerations : 
> 
> 
> Published specification : 
> http://www.w3.org/TR/json-ld
> 
> Applications which use this media : 
> Any programming environment that requires the exchange of directed
graphs. Implementations of JSON-LD have been created for JavaScript,
Python, Ruby, PHP, and C++. 
> 
> 
> Additional information :
> 
> 1. Magic number(s) : Not Applicable
> 2. File extension(s) : .jsonld
> 3. Macintosh file type code : TEXT
> 4. Object Identifiers: none
> 
> None
> 
> Person to contact for further information :
> 
> 1. Name : Ivan Herman
> 2. Email : ivan@w3.org
> 
> Intended usage : Common
> None
> 
> Author/Change controller : W3C
> 
> 
> 
> 
>

Received on Friday, 7 June 2013 03:34:17 UTC