Skip
repetitive navigational links
L-Soft  -  Home of  the  LISTSERV  mailing list  manager LISTSERV(R) 14.5
Skip repetitive navigational links
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (June 2005)Back to main MODS pageJoin or leave MODSReplyPost a new messageSearchProportional fontNon-proportional fontLog in
Date:         Mon, 6 Jun 2005 09:11:02 -0700
Reply-To:     Metadata Object Description Schema List <[log in to unmask]>
Sender:       Metadata Object Description Schema List <[log in to unmask]>
From:         Rick Beaubien <[log in to unmask]>
Subject:      Re: [METS] extension schemas
Comments: To: Metadata Encoding and Transmission Standard <[log in to unmask]>,
          [log in to unmask]
In-Reply-To:  <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1

> > I've also had to revert to METS v1.3 because when I use v1.4, I get the > following error message: > > Validation error in another file: > "http://www.loc.gov/standards/mods/xlink.xsd" > > For "http://www.loc.gov/standards/mods/xlink.xsd" I get the following: > > attribute 'xlink:to' is already declared in schema document > 'http://www.loc.gov/standards/mets/xlink.xsd' > Linda, I am cross posting this to the MODS list, as it connects with a discussion about xlink on the MODS list in early April. I wanted to respond as best I can to the second question in your recent extension schema memo. The METS on MODS schemas import what are I believe identical versions of the xlink schema from different locations.(As Ray Denenberg noted in his MODS list memo of April 4, w3c provides no normative version of the xlink schema). Prior to version 4 of METS, METS and MODS assigned different target namespaces to their respective versions of the xlink schema. But with version 4 of METS, the xlink target namespaces are now the same. Rightly or wrongly, when the 2005 version of XMLSpy goes to validate METS documents with embedded MODS metadata, it objects to the fact that two different schemas with same target namespace are referenced. (I can see the logic to this, and believe that the objections are probably justified. I don't believe that pre-2005 versions of XMLSpy cared, however). The simplest solution to this problem--especially if the two versions of the xlink schema are in fact identical and no one perceives a need for future divergence--would be for METS and MODS to import the same xlink schema from the same schemaLocation. The only way I can get the most recent version of XMLSpy to validate my v.4 METS documents with embedded MODS is to reference a local version of the mods schema that imports the mets version of the xlink schema. But clearly this is not a workable solution for a production environment. Rick -- Rick Beaubien Software Engineer, Research & Development Library Systems Office University of California, Berkeley Contact information: 88 Herrada Rd Santa Fe, NM 87508 505-466-6630 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/


Back to: Top of message | Previous page | Main MODS page

LISTSERV.LOC.GOV CataList email list search Powered by LISTSERV email list manager