Following my nose through the specs (I've done similar before...), I find that (in the specific case cited, i.e. RDF/XML) the governing spec appears to be the media type registration for application/xml and the +xml suffix [1]. Looking at the media type for application/rdf+xml [2], it defers to [1]. [1] has fairly strong recommendations on both charset and encoding. Since OSLC defines its own RDF/JSON serialization, and that re-uses the JSON media type registration in [3], the latter would govern (see section 6, the RFC has no TOC so no direct link). Again, the reg entry has fairly strong recommendations on both. OSLC would theoretically be allowed to specify non-conflicting requirements (or change its media types and do what it likes), however imposing any new MUSTs on existing concepts (especially in Core) would raise compatibility issues. Do you find the language in the respective media type registrations sufficiently prescriptive for your scenarios?
[1] http://tools.ietf.org/html/rfc3023#section-3.2 [2] http://tools.ietf.org/html/rfc3870#section-2 [3] http://tools.ietf.org/html/rfc4627 Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario From: Frank Budinsky <[email protected]> To: [email protected] Date: 11/21/2011 02:55 PM Subject: [oslc-core] Encoding of OSLC resources Sent by: [email protected] I'm wondering if the OSLC core specification needs to say something about the encoding requirements for OSLC defined resources. Currently it seems to only specify the requirement to support application/rdf+xml content type, but there is no mention of charset. I was assuming that perhaps there might be a well known requirement for the encoding of application/rdf+xml documented somewhere else (e.g., in some w3c spec), but I've been unable to find anything concrete. Maybe I just haven't looked long enough? I think OSLC may need to specify something like: 1. Is an explicit charset required in a response header? If not, what is the default (e.g., UTF-8)? 2. What charsets MUST be supported by OSLC resource providers (e.g., UTF-8 only, or UTF-8 and UTF-16, or other)? Thoughts? Thanks, Frank._______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
