Thanks Chris The only other alternative I can think of would be an additional property or to record it in metadata, but neither of these would supply it in the headers to the client without some code changes.
Steve > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Chris Wilper > Sent: 12 August 2010 02:00 > To: Steve Bayliss > Cc: [email protected] > Subject: Re: [fcrepo-dev] Correct place to record character > encoding for Managed datastreams > > > Hi Steve, > > On Wed, Aug 11, 2010 at 3:36 PM, Steve Bayliss > <[email protected]> wrote: > > If a managed datastream is storing text or XML, then what > is the correct way > > to persist the character encoding of the stream? > > > > I've experimented setting the MIMEType of the datastream > to, eg, "text/xml; > > charset=UTF-8" - and this does get returned in the http headers when > > accessing the datastream. Is this the intended location > for storing this > > information? > > Putting the character encoding in as a MIME parameter is something > I've seen others do for Feodra datastreams as well. Honestly, I don't > think we originally anticipated that the MIME type field for > datastreams would be used with parameters, but in retrospect, this > seems to be a fine place to persist the character encoding. > > - Chris > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
