Re: [search-ws] application/sru+xml

I've put up a revision at:

http://www.loc.gov/standards/sru/oasis/sru-2-0-response.xsd

 

And all of the imported schemas are there 
at

http://www.loc.gov/standards/sru/oasis/

 

And in this revision I've left alone the 
extraResponseData and put xs:any along with it, and similar for 
extraRecordData.  That should address both Janifer's and Ralph's concerns. 

 

--Ray

 

 

----- Original Message ----- 

  
From: 
  LeVan,Ralph 

  
To: Ray Denenberg, Library of Congress ; OASIS SWS TC 

  
Sent: Thursday, January 28, 2010 9:58 
  AM

  
Subject: RE: [search-ws] 
  application/sru+xml

  

  

  
It 
  looks to me like you’ve dealt with <record> twice in that 
  response.  I’m hoping one of those was meant to be the 
  <searchRetrieveResponse>.

  
 

  
I’m 
  all in favor of adding the new xs:any element and deprecating the use of the 
  various extraDatas, but I don’t want to go so far as to unnecessarily break 
  any applications built on the use of extraData.

  
 

  
I 
  think there’s extraData in Scan responses too.

  
 

  
I 
  think this proposal is a nice compromise between my request for some well-know 
  DC elements in the record and Mike’s insistence that the idea is 
  foolish.  I suspect I’ll just populate the <record> element with 
  the appropriate atom elements and be done with it.

  
 

  
Ralph

  
 

  

  

  

  
From: Ray Denenberg, 
  Library of Congress [mailto:] 
Sent: Wednesday, January 
  27, 2010 6:03 PM
To: OASIS SWS TC
Subject: [search-ws] 
  application/sru+xml

  
 

  

  
I posted a 
  message several days ago suggesting that we consider looking at possible 
  changes to the default SRU 2.0 response, application/sru+xml, to allow 
  arbitrary, foreign (namespaced), ignorable elements.   There was no 
  discussion, does that mean nobody thinks it's a good idea or that nobody 
  cares?  

  

  
 

  

  
As of right now the 
  IETF draft ("00")  to register several mime types including SRU has 
  expired and I am in the process of "negotiating" draft "01" (an unpleasant 
  process, which you'll understand if you've ever negotiated with the IETF) 
  and it seems to me that this is an opportune time to consider possible tweaks 
  to this format.  

  

  
 

  

  
 

  

  
To begin, at the 
  top level of the schema the elements are

  
    
                  
                  
              
  <xs:element 
  ref="numberOfRecords" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="resultSetId" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="resultSetIdleTime" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="records" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="nextRecordPosition" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="echoedSearchRetrieveRequest" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="diagnostics" 
  minOccurs="0"/>

  
                                              
  <xs:element 
  ref="extraResponseData" 
  minOccurs="0" 
  maxOccurs="unbounded"/>

  
<!—the 
  above elements are carried over from SRU version 1.1; the following are new in 
  version 2 à

  
                                              
  <xs:element 
  ref="resultCountPrecision" 
  minOccurs="0" 
  maxOccurs="unbounded"/>

  
                                              
  <xs:element 
  ref="facetedResults" 
  minOccurs="0" 
  maxOccurs="unbounded"/>

  

  
                                              
  <xs:element 
  ref="searchResultAnalysis" 
  minOccurs="0" 
  maxOccurs="unbounded>

  

  
 

  

  
 

  

  
I 
  would like to think that we could keep the discussion bounded to the 
  <records> element. That is, not try to wedge arbitrary elements 
  elsewhere.

  

  
 

  

  
<records> 
  is:

  

  
                      
  <xs:sequence>

  
                                  
  <xs:element 
  ref="recordSchema"/>

  
                                  
  <xs:element 
  ref="recordPacking" 
  minOccurs="0"/>

  
                                  
  <xs:element 
  ref="recordData"/>

  
                                  
  <xs:element 
  ref="recordPosition" 
  minOccurs="0"/>

  
                                  
  <xs:element 
  ref="extraRecordData" 
  minOccurs="0"/>

  
                              
  </xs:sequence

  

  
 

  

  
My 
  first suggestion is to get rid of the element <extraRecordData> and 
  replace 

  

  
 

  

  
                                  
  <xs:element ref="extraRecordData" minOccurs="0"/>

  
with

  
 

  

  
                                  
  <xs:any   namespace= 
  "##other" minOccurs="0" 
  maxOccurs="unbounded"/>

  
 

  
 

  
                      
  Next,<record>is:

  
                      
  <xs:sequence>

  
                                  
  <xs:element 
  ref="recordSchema"/>

  
                                  
  <xs:element 
  ref="recordPacking" 
  minOccurs="0"/>

  
                                  
  <xs:element 
  ref="recordData"/>

  
                                  
  <xs:element 
  ref="recordPosition" 
  minOccurs="0"/>

  
                                  
  <xs:element 
  ref="extraRecordData" 
  minOccurs="0"/>

  
                      
  </xs:sequence>

  
 

  
My next 
  suggestion is to do the same thing with extraRecordData.

  
 

  
Please 
  comment!

  
 

  
--Ray