OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] question w.r.t.: Extensible Markup Language (XML) 1.0 (Thi

[ Lists Home | Date Index | Thread Index ]
  • To: "Harrie Hazewinkel" <harrie@lisanza.net>, <xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] question w.r.t.: Extensible Markup Language (XML) 1.0 (Third Edition)
  • From: "Grand Christophe" <chgrand@sopragroup.com>
  • Date: Fri, 17 Sep 2004 11:57:18 +0200
  • Thread-index: AcScmURjH187HdORQ3e1aEa/b9rr3AAA2UXQ
  • Thread-topic: [xml-dev] question w.r.t.: Extensible Markup Language (XML) 1.0 (Third Edition)

Hello Harrie,

I think you have to change your <Meta> to:
<Meta>
<Type>text/x-vcalendar</Type>
<Format>b64</Format>
</Meta>
and then base64-encode your data in the <Data> element.

Regards,

Christophe

-----Message d'origine-----
De : Harrie Hazewinkel [mailto:harrie@lisanza.net]
Envoyé : vendredi 17 septembre 2004 11:29
À : xml-dev@lists.xml.org
Objet : [xml-dev] question w.r.t.: Extensible Markup Language (XML) 1.0
(Third Edition)


HI all,


I have a question with respect to the Extensible Markup Language (XML)
1.0 (Third Edition) standard of "http://www.w3.org/TR/REC-xml";.

In this section it specifies the handling of CRLF.

2.11 End-of-Line Handling

XML parsed entities are often stored in computer files which, for 
editing convenience, are organized into lines. These lines are typically 
separated by some combination of the characters CARRIAGE RETURN (#xD) 
and LINE FEED (#xA).

To simplify the tasks of applications, the XML processor MUST behave as 
if it normalized all line breaks in external parsed entities (including 
the document entity) on input, before parsing, by translating both the 
two-character sequence #xD #xA and any #xD that is not followed by #xA 
to a single #xA character.


But how about this piece of XML (part of SyncML),
<Add>
<CmdID>4</CmdID>
<Meta>
<Type>text/x-vcalendar</Type>
</Meta>
<Item>
<Source>
<LocURI>1095163651-912@icc.inet.it</LocURI>
</Source>
<Data>BEGIN:VEVENT^M
SUMMARY:group meeting^M
CLASS:PUBLIC^M
LOCATION:outer space^M
DESCRIPTION:~~~~~~~~~~~~~~~~~~~~\r\nOrganizer: Harrie^M
  Hazewinkel\r\nAttendees: \r\nHarrie Hazewinkel +\r\nAntonio Amadori^M
  ?\r\nGastone Amadori  ?\r\n~~~~~~~~~~~~~~~~~~~~\r\nI like to keep^M
  inviting you. :-)\r\n^M
DTSTAMP:20040914T120731Z^M
ORGANIZER:cap://cap.inet.it/harrie@ifm-test.inet.it^M
ATTENDEE:cap://cap.inet.it/harrie@ifm-test.inet.it^M
X-INE-OWNER:YES^M
DTSTART:20040908T090000Z^M
DTEND:20040908T110000Z^M
END:VEVENT^M
</Data>
</Item>
</Add>


The data is here between the <Data> and </Data> tags.
This is a calendar element which by mime type must keep
the CRLF after each line. This is made visible with the '^M'<linefeed>
(representation problem).

Would the lines describing the event also fall
under the section described above? If so XMl changes data and one
cannot get back it, I guess.

Would this not a problem with the current specification?
Any comments,

Harrie


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS