RE: [search-ws] Parameter name mismatch, responseType, APD and SRU

["Ray Denenberg, Library of Congress" <rden@loc.gov>]

I meant "I suggest the first" not "latter".

-----Original Message-----
From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov] 
Sent: Monday, September 13, 2010 6:00 PM
To: 'OASIS SWS TC'
Subject: RE: [search-ws] Parameter name mismatch, responseType, APD and SRU

Sorry I meant to get this on the agenda for this morning and forgot. But I'd
like to get a quick resolution and it is a small problem.

So we have two choices:

1. change the name of responseType in the APD to something else. 
2. Change the name of responseType in SRU to something else.

I suggest the latter. Change the name of ResponseType in the APD to
responseFormat.  Why? Because (paradoxically) the parameter is more abstract
in SRU than it is in the APD, and ResponseType seems more abstract than
responseFormat.

--Ray

-----Original Message-----
From: Denenberg, Ray [mailto:rden@loc.gov]
Sent: Friday, September 10, 2010 11:29 AM
To: 'OASIS SWS TC'
Subject: [search-ws] Parameter name mismatch, responseType, APD and SRU

As I am reviewing the APD (haven't looked at it for a couple months) I am
suddenly reminded that 

- we have an abstract parmeter named 'responseType', which binds to concrete
SRU parmeter httpAccept.
- we have (relatively recently) introduced the parameter 'responseType' into
SRU not based on any abstract parameter. ("The request parameter
'responseType', paired with the internet media type specified for the
response (via either the httpAccept parameter or http accept header)
determines the schema for the response.")

Not that this is "illegal" but it does seem rather sloppy to change the one
abstract parameter name (that we named) and then invent a new parameter
using the discarded name; it detracts from the credibility of the abstract
model.   

So I suggest that we need to change the name of responseType, either in SRU
or in the APD.  

Suggestions?

(For discussion Monday. Agenda coming, late today.)

--Ray

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php