* pkeane <[EMAIL PROTECTED]> [2007-10-05 07:00]: > <item serial_number="000435213"> > <metadata > ascii_id="admin_checksum">630230b057c511cbee87447960fff02e</metadata> > <metadata ascii_id="admin_filename">62-GT-06.jpg</metadata> > <metadata ascii_id="admin_file_size">318642</metadata> > <metadata ascii_id="admin_image_height">576</metadata> > <metadata ascii_id="admin_image_width">720</metadata> > <metadata ascii_id="admin_mime_type">image/jpeg</metadata> > <metadata ascii_id="admin_serial_number">000435213</metadata> > <metadata ascii_id="admin_upload_date_time">2007-07-18T15:59:28</metadata> > <metadata ascii_id="credit">Photographer: Unknown</metadata> > <metadata ascii_id="dase_rights">Restricted</metadata> > <metadata ascii_id="description">photo of Ben Barnes while Speaker, black > and white</metadata> > <metadata ascii_id="keyword">Ben Barnes</metadata> > <metadata ascii_id="keyword">Capitol Building interior</metadata> > <metadata ascii_id="keyword">Lieutenant Governor</metadata> > <metadata ascii_id="keyword">Speaker of the House</metadata> > <metadata ascii_id="original_filename">62-GT-06.jpg</metadata> > <metadata ascii_id="rights_owner">Senate Media Services</metadata> > <metadata ascii_id="rights_status">Use in Texas Politics content</metadata> > <metadata ascii_id="scratch_pad">/62-GT-06.jpg</metadata> > <metadata ascii_id="title">Ben Barnes</metadata> > <metadata ascii_id="used_in_chapter">none</metadata> > <media_file filename="000435213_800.jpg" size="medium" height="576" > width="720" mime_type="image/jpeg" /> > <media_file filename="000435213_100.jpg" size="thumbnail" height="80" > width="100" mime_type="image/jpeg" /> > <media_file filename="000435213_640.jpg" size="small" height="480" > width="600" mime_type="image/jpeg" /> > </item> > > Any thoughts on the benefits of using atom here?
I don’t see the problem. Atom gives you an Entry where you can put the metadata for a media resource. You have a bunch of attributes that should be mapped to Atom elements; the rest you stick into the content, possibly as RDF since your ad-hoc vocab is more or less along those lines anyway. > I cannot get past the fact that my ultra-generic xml schema is > REALLY easy to deal with It’s not actually very generic. It’s a very limited vocabulary that expresses barely any more than a map of key-value pairs. Of course such a simple data structure is easy to deal with. The only genericity there is that the keys are arbitrary strings. It looks easy now because you have to do almost no work up front: the structure is rigid and the semantics are completely ad-hoc. It won’t look very easy at all once you have a large dataset with an inconsistent mess of key names. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
