Menu
▾
▴
Re: [Xena-devel] Xena, meta-data and export
|
From: Chris <ch...@te...> - 2004-09-17 10:28:30
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Chris Strusz wrote: <blockquote cite="mid2BC4D1CA28C5D511AA190002A574CADB0200D4DD@SPARMAIL3" type="cite"> <meta http-equiv="Content-Type" content="text/html; "> <title></title> <meta content="MSHTML 5.50.4522.1800" name="GENERATOR"> <div><font color="#000080" face="Book Antiqua" size="2"><span class="221190607-17092004">OK,</span></font></div> <div><font color="#000080" face="Book Antiqua" size="2"><span class="221190607-17092004">So let me try and get what you're suggesting. You're saying that we want to put metadata that identifies the source data object (by type, name, etc) in the content data rather than the metadata element of the package. The idea being that the content data type is preserved with the content data and any manipulation can be done independantly of the package wrapper.</span></font></div> <div><font color="#000080" face="Book Antiqua" size="2"><span class="221190607-17092004">So in an email, each part may include an element that identifies the original data type of the content of that part. So we could extract attachments independantly of the email, and un-normalise them based on the information contained in the part, ie the attachment.</span></font></div> <div><font color="#000080" face="Book Antiqua" size="2"><span class="221190607-17092004">So in a multipart piece of content data, each part would become self documenting with regard to it's file type. Essentially it would carry descriptive/interpretive data with the content data.</span></font></div> <div><font color="#000080" face="Book Antiqua" size="2"><span class="221190607-17092004">If this is the case, it makes a lot of sense. The question remains, how well does this work where we've used someone else's XML data format, eg OO.o? Which I believe is the question you asked. Does Simon's suggestion work for you?<br> </span></font></div> </blockquote> <br> What I am talking about is something like this....<br> <br> <package><br> <meta><br> <source><a class="moz-txt-link-freetext" href="file:///some/file/">file:///some/file/</a></source<br> </meta><br> <content><br> <email><br> <headers><header name="Subject">See attached document</header></headers><br> <part><br> <plaintext>Hello there!</plaintext><br> </part><br> <part><br> <package><br> <meta><br> <source><a class="moz-txt-link-freetext" href="file://statistics/myFactsAndFigures.doc">file://statistics/myFactsAndFigures.doc</a></source><br> </meta><br> <content><br> <binary-object>aatnsoehu9847p5rcahoeusnatoeh</binary-object><br> </content><br> </package><br> </part><br> </email><br> </content><br> </package><br> <br> </body> </html> |