Re: [cmis] Text encoding in AtomPub

[Al Brown <albertcbrown@us.ibm.com>]

Please see http://tools.ietf.org/html/rfc4287#page-14.

I read type="text" to map to text/plain. Other text/* media types can be specified. See clause #5.

   5.  If the value of "type" begins with "text/" (case insensitive),
      the content of atom:content MUST NOT contain child elements.
-Al

Al Brown
Emerging Standards and Industry Frameworks
CMIS: https://w3.tap.ibm.com/w3ki07/display/ECMCMIS/Home
Industry Frameworks: https://w3.tap.ibm.com/w3ki07/display/ECMIF/Home

Office 714 327 3453
Mobile 714 263 6441
Email albertcbrown@us.ibm.com
CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.

Florent Guillaume ---07/24/2009 05:29:02 AM---Hm you're right, AtomPub doesn't allow sending text/* in base64. I

From:	Florent Guillaume <fg@nuxeo.com>
To:	Florian Müller <Florian.Mueller@opentext.com>
Cc:	cmis@lists.oasis-open.org, Julian Reschke <julian.reschke@greenbytes.de>
Date:	07/24/2009 05:29 AM
Subject:	Re: [cmis] Text encoding in AtomPub

---

Hm you're right, AtomPub doesn't allow sending text/* in base64. I  
hadn't realized its model was so restrictive.

But anyway if you pick a file from the filesystem, how do you know  
that it's text, and that its media type is text/something?
If you have out-of-band information that gives a media type of text/ 
something, but without an encoding, then something is missing for it  
to be interpreted correctly anyway by a processor that cares about  
media type. But I agree that legacy systems may have such partial  
information. I'd say in that case just guess the encoding if you can,  
or otherwise pretend it's ISO-8859-1 which will allow all bytes to be  
transmitted and stored back in the same way.

Florent

On Jul 24, 2009, at 1:01 PM, Florian Müller wrote:

> If I treat it as a binary then I have to set a content type  
> different from text/* (see AtomPub spec 4.1.3.3). The only possible  
> content type would be application/octet-stream. That would be a loss  
> of information.
> Through the SOAP interface I can upload the content AND set a text/*  
> content type.
>
> Florian
>
>
> -----Original Message-----
> From: Florent Guillaume [mailto:fg@nuxeo.com]
> Sent: Friday, July 24, 2009 12:18 PM
> To: Florian Müller
> Cc: cmis@lists.oasis-open.org
> Subject: Re: [cmis] Text encoding in AtomPub
>
> Basically if you don't know the encoding, then it's not text, it's a
> binary.
>
> Florent
>
> On Jul 24, 2009, at 10:52 AM, fmueller@opentext.com wrote:
>
>> Hi,
>>
>> Here is a question to all the CMIS AtomPub client developers out
>> there:
>>
>> I got stuck with document creation. In order to comply with AtomPub,
>> text files must not be base64 encoded but enclosed in the <content>
>> tag as plain text. This text must use the same encoding as the Atom
>> XML around it.
>> If I pick up a text file from the file system I don't know the
>> encoding of this file and therefore I can't re-encode the text
>> correctly. If the original encoding of the text file and the
>> encoding of the Atom XML don't match by coincidence the document
>> content in the repository will be different from the original
>> content. That is, I can't rely on this method. Since creating
>> documents in two steps (entry first, then adding content) is not
>> supported by all repositories this is not viable option either.
>>
>> Do I make an error in reasoning or do we have a real issue here?
>>
>>
>> Thanks,
>>
>> Florian
>
> -- 
> Florent Guillaume, Head of R&D, Nuxeo
> Open Source, Java EE based, Enterprise Content Management (ECM)
> http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87
>

-- 
Florent Guillaume, Head of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php