[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DEFECT in SearchRetrieve (FW: Question about searchRetrieve 1.0 'recordIdentifier' element)
I believe there is a defect (minor) in the sruResponse.xsd schema. Note in: The element <recordIdentifier> is defined. It is omitted in the schema and should have been included. See below. Please let me know if you agree with my assessment that this is a defect. Chet - what is the procedure for fixing this? --Ray From sru2.0.html: Each <record> element is structured into the elements shown in the following table. Table 3: Structure of the <Record> Element
From the Schema (note omission of recordIdentifier): <!-- recordDefinition--> <xs:complexType name="recordDefinition"> <xs:sequence> <xs:element ref="recordSchema"/> <xs:element ref="recordPacking" minOccurs="0"/> <!-- recordPacking has different meaning when used for versions 1.2 or earlier than for 2.0 or later. --> <xs:element ref="recordXMLEscaping" minOccurs="0"/> <!-- recordXMLEscaping valid only for 2.0 or later. --> <xs:element ref="recordData"/> <xs:element ref="recordPosition" minOccurs="0"/> <xs:element ref="extraRecordData" minOccurs="0"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> -----Original Message----- Hi Jörg - recordIdentifier was intended to be included in the schema (within recordDefinition). Its omission is a defect. Thanks for catching this. As this is the first defect reported I will need to investigate the process to get it fixed. I'll get back to you, thanks again. Ray > -----Original Message----- > From: Jörg Prante [mailto:prante@hbz-nrw.de] > Sent: Wednesday, June 19, 2013 9:42 AM > To: Denenberg, Ray > Cc: Bernhard Assmann > Subject: Question about searchRetrieve 1.0 'recordIdentifier' element > > Hi, > > I'd like to know whether it is allowed to use a "recordIdentifier" > element in searchRetrieve 1.0 or not. > > In the XML schema at > > http://docs.oasis-open.org/search- > ws/searchRetrieve/v1.0/os/schemas/sruResponse.xsd > > it is missing. So, when generating valid SRU 2.0 responses, I am > forced to drop the "recordIdentifier" element. > > But, in the specification at > > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/os/part3- > sru2.0/searchRetrieve-v1.0-os-part3-sru2.0.html#_Toc324162490 > > it is listed as optional, and it seems it is allowed for use in SRU > 2.0 responses. > > Do I miss something? I can't figure out what is correct. > > Thanks in advance for your help. > > Best regards, > > Jörg > > > > -- > Jörg Prante > hbz, Gruppe Portale > - Digitale Bibliothek und Online-Fernleihe - Postfach 270451, 50510 > Köln, Deutschland Telefon +49-221-40075-156, Fax +49-221-40075-190 > prante@hbz-nrw.de http://www.hbz-nrw.de |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]