MessageHi AsgerThat's a good point. Presumably a definition as per http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17 with the media types as per http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7So from that the main type has to go first and my guess is that the order of the parameters is not important. Though I wonder if there are further levels of complexity; eg could charset be utf-8 and UTF-8 and both be equivalent? (It looks like utf-8 is the canonical form though for text/xml)Steve-----Original Message-----Yes, but we would need to specify some rules then.
From: Asger Askov Blekinge [mailto:email@example.com]
Sent: 19 December 2011 14:29
Subject: Re: [fcrepo-user] ECM validation of MIMETYPE
charset is not the only subtype allowed, I do believe this is an openended set. I do know people have been using "version" as well.
So, I would need to know how to split a mime-type and if the order of the subtypes are important?
Secondly, you can of course specify multiple form statements in the content model, the requirement is just that ONE of them match. So, specify the various allowed charsets, and one without charset, and you should be safe.
On 12/15/2011 01:03 PM, Stephen Bayliss wrote:
As far as I can tell, ECM validation of a datastream’s MIMETYPE is strict – the entire MIMETYPE property contents have to match that declared in the content model.
What about the case where one might want to specify the MIMETYPE of a datastream in the CModel, but not the character set? If I specify MIMETYPE as “text/xml” in the CModel and as “text/xml; charset=UTF-8” in the object, it fails validation.
Would it make sense to only validate charset if it is defined in the content model?