since Ross and I still don't understand each other's positions, I think it is premature to "vote" on anything.
I agree the COinS spec should clarify for the unbelieving that, yes you really have to url-encode and url-decode the KEV values like the Z39.88 standard says you have to, since rewriting that spec is not in scope of COinS. I hesitate to get into the double-url-encoding that you have to do in some cases, because that REALLY gets confusing. >Since Eric and I have been bantering back and forth all day (and >neither seems to be making much headway on the other), I say this >issue goes out for a vote. > >There are basically two items up for vote here: > >1) the COinS spec needs to say explicitly whether the KEV values are >to be URLencoded or not encoded inside the title tag > > >2) if #1 is true, the KEV value needs to be URLencoded inside the >title tag (vs. explicitly not encoding them) > >-Ross. -- Eric Hellman, Director OCLC Openly Informatics Division [EMAIL PROTECTED] 2 Broad St., Suite 208 tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 http://openly.oclc.org/1cate/ 1 Click Access To Everything --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gcs-pcs-list" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gcs-pcs-list?hl=en -~----------~----~----~----~------~----~------~--~---
