Hi all. The ocoins.info "spec" contains an example which includes:
&rft_val_fmt=info:ofi/fmt:kev:mtx:journal When I first saw that, I thought, gee, shouldn't that be escaped/encoded somehow? If I were creating an SAP1 KEV context object, I believe (I confess escaping/encoding still confuses me) would need to encode this like: &rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal If I'm putting an SAP1 KEV context object into my COinS, then I'd think I'd leave it alone just like that---except the example makes different choices about escaping. Nowhere in the ocoins.info "spec" is the word escape or escaping mentioned, or encode/encoding in the context of this question. So it's a bit confusing what is supposed to be reccommended/required here. All we have is the example to look at. Can we get some clarity as to how a COinS should be encoded/escaped, and maybe put it on ocoins.info? To me, again, a COinS should probably be encoded just like a SAP1 KEV, and then nobody needs to specify anything else. Or at least that should be an option that applications are required to support (it's been suggested to me that Zotero may not support escaped COinS). If you aren't going to say "just like" something else, then I guess ocoins.info needs to spell out how things should be escaped/encoded itself. One way or another, the current vagueness and spec only by one example seems to be leading to confusion? Thanks, Jonathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
