Thank you, Rebecca! I look forward to hearing from you. Best! Amy From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On Behalf Of Guenther, Rebecca Sent: Tuesday, March 26, 2013 11:07 AM To: [log in to unmask] Subject: Re: [PIG] Premis namespace We are exploring this-- our schema developer is out for a few days but we will get an answer to you soon. Rebecca Rebecca Squire Guenther Network Development & MARC Standards Office Library of Congress Washington, DC 20540 [log in to unmask]<mailto:[log in to unmask]> From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On Behalf Of Hatfield, Amy J Sent: Wednesday, March 20, 2013 4:21 PM To: [log in to unmask]<mailto:[log in to unmask]> Subject: [PIG] Premis namespace Greetings: Just signed up for the list. First post. Need a little help. We have implemented a metadata model for our research repository, consisting of datasets, that includes METS (wrapper), DC (description), MODS (personal name/owner information), and PREMIS (preservation) metadata. Our programmer is coding in PHP and is using the libxml2 library to handle the xml construct for our metadata. I recently went through the process of metadata validation and well-formed checking. We are good in that regard. However, my programmer just informed me that the libxml2 library blows up when it encounters the info:lc/xmlns/premis-v2 namespace because it is relative instead of absolute. Problem is, if I change the namespace URI, our metadata is no longer valid. Has anyone encountered this issue? What did you do as a workaround? Thanks for any guidance on the this issue. Best! Amy Amy J. Hatfield, MLS Assistant Professor of Library Science, Metadata Specialist Purdue University Libraries, Digital Programs (765) 494-6333 [log in to unmask]<mailto:[log in to unmask]> STEW, 279