From daniel.chudnov at yale.edu Wed Jun 14 17:20:04 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Wed Jun 14 17:20:42 2006 Subject: [gcs-pcs-list] update. Message-ID: <20060614212004.GH7339@sildin.med.yale.edu> So I'm at this conference in Ohio yesterday and somebody gets up to talk about their new library OPAC and one of their slides says "it supports unAPI". Okay, well, it was people from Evergreen, so, it wasn't a complete surprise, but, still, pretty cool, no? Our deadline for unAPI Version One is soon (next week), but so far no issue have been raised against revision 3. So, if you have issues, let them be known now! Separately, there's an opportunity to write an introduction to unAPI for one of the more-prominent non-peer-reviewed digital library journals. I'd like to invite everybody who's helped with the spec so far, or done any implementation, to help put that article together or at least submit a screenshot or description of how you're using it in your application. I'm starting to put the text together and will need help editing and rounding out the article, too. The article has a short turnaround - it's due the first week of July. But, it shouldn't be too hard to get done. This is a great opportunity to showcase how so many of us from somewhat-far reaches of the library world were able to assemble a new and useful specification quickly and successfully, and the more co-authors we can credit, the better! Let me know if you're interested offline and I'll start up a private thread so we don't bombard the list with details. If you haven't set aside time to try unAPI yet and are looking for a good reason, contributing to the article and offering feedback for the pending unAPI Version One release are the best reasons yet. Thanks, -Dan -- Daniel Chudnov Yale Center for Medical Informatics (203) 737-5789 From daniel.chudnov at yale.edu Wed Jun 21 09:31:28 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Wed Jun 21 09:32:03 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow Message-ID: <20060621133128.GA25390@sildin.med.yale.edu> unapi.info claims that unAPI Version 1 will be released tomorrow. Thoughts? Issues? Reflections? Haiku? -dc -- Daniel Chudnov Yale Center for Medical Informatics (203) 737-5789 From ross.singer at library.gatech.edu Wed Jun 21 09:43:29 2006 From: ross.singer at library.gatech.edu (Ross Singer) Date: Wed Jun 21 09:45:09 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow In-Reply-To: <20060621133128.GA25390@sildin.med.yale.edu> References: <20060621133128.GA25390@sildin.med.yale.edu> Message-ID: <23b83f160606210643v68bb8491x454171f47fbb5e6e@mail.gmail.com> The unAPI spec is due out tomorrow. Anything to show? -Ross. On 6/21/06, Daniel Chudnov wrote: > > unapi.info claims that unAPI Version 1 will be released tomorrow. > > Thoughts? Issues? Reflections? Haiku? > > -dc > > > -- > Daniel Chudnov > Yale Center for Medical Informatics > (203) 737-5789 > _______________________________________________ > gcs-pcs-list mailing list > gcs-pcs-list@cipolo.med.yale.edu > http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cipolo.med.yale.edu/pipermail/gcs-pcs-list/attachments/20060621/7a1c11ec/attachment.htm From daniel.chudnov at yale.edu Wed Jun 21 10:01:52 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Wed Jun 21 10:02:25 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow In-Reply-To: <23b83f160606210643v68bb8491x454171f47fbb5e6e@mail.gmail.com> References: <20060621133128.GA25390@sildin.med.yale.edu> <23b83f160606210643v68bb8491x454171f47fbb5e6e@mail.gmail.com> Message-ID: <20060621140150.GB25390@sildin.med.yale.edu> Ross Singer wrote, on Wed, Jun 21, 2006 at 09:43:29AM -0400: > The unAPI > spec is due out tomorrow. > Anything to show? I heard your umlaut would support unAPI; ain't seen that yet though. :P -- Daniel Chudnov Yale Center for Medical Informatics (203) 737-5789 From ross.singer at library.gatech.edu Wed Jun 21 11:40:22 2006 From: ross.singer at library.gatech.edu (Ross Singer) Date: Wed Jun 21 11:41:58 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow In-Reply-To: <20060621140150.GB25390@sildin.med.yale.edu> References: <20060621133128.GA25390@sildin.med.yale.edu> <23b83f160606210643v68bb8491x454171f47fbb5e6e@mail.gmail.com> <20060621140150.GB25390@sildin.med.yale.edu> Message-ID: <23b83f160606210840h3ddbd696hc0ccd04c2ad1374@mail.gmail.com> The umlaut used to work with the first revision not anymore though. I'll fix it today. -Ross. On 6/21/06, Daniel Chudnov wrote: > > Ross Singer wrote, on Wed, Jun 21, 2006 at 09:43:29AM -0400: > > The unAPI > > spec is due out tomorrow. > > Anything to show? > > I heard your umlaut > would support unAPI; > ain't seen that yet though. :P > > > -- > Daniel Chudnov > Yale Center for Medical Informatics > (203) 737-5789 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cipolo.med.yale.edu/pipermail/gcs-pcs-list/attachments/20060621/0eafd4dc/attachment.htm From ehs at pobox.com Wed Jun 21 13:31:53 2006 From: ehs at pobox.com (Edward Summers) Date: Wed Jun 21 13:33:11 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow In-Reply-To: <20060621133128.GA25390@sildin.med.yale.edu> References: <20060621133128.GA25390@sildin.med.yale.edu> Message-ID: <5954B3F3-B1BF-4CF2-8238-CB6780E0E385@pobox.com> On Jun 21, 2006, at 9:31 AM, Daniel Chudnov wrote: > unapi.info claims that unAPI Version 1 will be released tomorrow. > > Thoughts? Issues? Reflections? Haiku? The validator once validated now it's invalid //Ed From fawcett at uwindsor.ca Wed Jun 21 13:51:48 2006 From: fawcett at uwindsor.ca (Graham Fawcett) Date: Wed Jun 21 13:52:43 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow In-Reply-To: <20060621133128.GA25390@sildin.med.yale.edu> References: <20060621133128.GA25390@sildin.med.yale.edu> Message-ID: <44998734.1000300@uwindsor.ca> On 21/06/2006 9:31 AM, Daniel Chudnov wrote: > unapi.info claims that unAPI Version 1 will be released tomorrow. > Thoughts? Issues? Reflections? Haiku? > long-tail apps blooming-- a thousand cherry blossoms!-- one the spec is baked. he who asks for thoughts, issues, reflections, haiku, gets only haiku. --g From daniel.chudnov at yale.edu Thu Jun 22 13:28:58 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Thu Jun 22 13:29:53 2006 Subject: [gcs-pcs-list] one day. Message-ID: ...and the wind whispers: Unless somebody speaks up, unAPI one's done. -- Daniel Chudnov Yale Center for Medical Informatics (203) 737-5789 From daniel.chudnov at yale.edu Thu Jun 22 13:32:24 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Thu Jun 22 13:33:16 2006 Subject: Fwd: RE: [gcs-pcs-list] unAPI due date tomorrow References: Message-ID: <72635C60-1116-4439-B837-A2CFFD5A8F74@yale.edu> This message got bounced for no obvious reason... sorry, Peter. -dc Begin forwarded message: > From: "Binkley, Peter" > Date: June 22, 2006 12:57:06 PM EDT > To: gcs-pcs-list-bounces@cipolo.med.yale.edu > Subject: RE: [gcs-pcs-list] unAPI due date tomorrow > > > Winds whip the opac; > Shuddering, it stands and serves: > It is compliant. > > I think. > > Try this to get an opac record: > > http://ualweb.library.ualberta.ca/uhtbin/cgisirsi/x/0/0/57/5? > user_id=WUA > ARCHIVE&searchdata1=1565847547{020} > > I can't get Xioming's Greasemonkey scripts, and the validator isn't > working, but I think everything's ok: the unapi-server link and the > unapi abbr tag are both there, and the unapi server is returning mods, > marcxml and dc records: > > http://chelsea.library.ualberta.ca:8090/unapi/server? > id=2623311&format=m > ods > > There's some error-handling fixes that need to be done (a bad id > gets an > empty xml file instead of a 404) and such, but it should be working > otherwise. > > Peter From Peter.Binkley at ualberta.ca Fri Jun 23 14:18:16 2006 From: Peter.Binkley at ualberta.ca (Binkley, Peter) Date: Fri Jun 23 14:25:41 2006 Subject: [gcs-pcs-list] unAPI due date tomorrow Message-ID: <908893006339C0409519E4065DF3B24901571330@mailserver.ualibrary.ualberta.ca> Xiaoming pointed out that my server wasn't available outside our firewall; this is fixed now. Peter -----Original Message----- From: gcs-pcs-list-bounces@cipolo.med.yale.edu [mailto:gcs-pcs-list-bounces@cipolo.med.yale.edu] On Behalf Of Daniel Chudnov Sent: Thursday, June 22, 2006 11:32 AM To: gcs-pcs-list@cipolo.med.yale.edu Subject: Fwd: RE: [gcs-pcs-list] unAPI due date tomorrow This message got bounced for no obvious reason... sorry, Peter. -dc Begin forwarded message: > From: "Binkley, Peter" > Date: June 22, 2006 12:57:06 PM EDT > To: gcs-pcs-list-bounces@cipolo.med.yale.edu > Subject: RE: [gcs-pcs-list] unAPI due date tomorrow > > > Winds whip the opac; > Shuddering, it stands and serves: > It is compliant. > > I think. > > Try this to get an opac record: > > http://ualweb.library.ualberta.ca/uhtbin/cgisirsi/x/0/0/57/5? > user_id=WUA > ARCHIVE&searchdata1=1565847547{020} > > I can't get Xioming's Greasemonkey scripts, and the validator isn't > working, but I think everything's ok: the unapi-server link and the > unapi abbr tag are both there, and the unapi server is returning mods, > marcxml and dc records: > > http://chelsea.library.ualberta.ca:8090/unapi/server? > id=2623311&format=m > ods > > There's some error-handling fixes that need to be done (a bad id gets > an empty xml file instead of a 404) and such, but it should be working > otherwise. > > Peter _______________________________________________ gcs-pcs-list mailing list gcs-pcs-list@cipolo.med.yale.edu http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list From daniel.chudnov at yale.edu Fri Jun 23 20:24:51 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Fri Jun 23 20:25:59 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 Message-ID: Toll the bells, Alert the whole media! unAPI 1's done! Just one API for all your identified objects and formats; Just one simple way to tell the world: "Here, copy our stuff! Use the IDs!" We battled some -- sometimes identifiers will lead to battles. But then we converged, coagulated, even, after Corvallis. And now we all know: for macroformat copies, just use unAPI. Long live ROGUE '05! (So we took an extra month... who cares? It's done now.) Beers for everybody -- I'm buying! Not in New Haven? Next conference, then. Until then, toll bells, unAPIfy your webapps, and blog all the links! Or even better, help write the intro paper! Send text, and screenshots. Please! Please, please, please, please! (Please X7) (Please x5) Oh yeah -- one more thing. Where should you go for the specs? unapi.info! (Thanks everybody! -Dan) From mrylander at gmail.com Fri Jun 23 21:35:27 2006 From: mrylander at gmail.com (Mike Rylander) Date: Fri Jun 23 21:37:02 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: References: Message-ID: "It's ... so ... beautiful." miker_ weeps like a baby, for un appy 1. :) On 6/23/06, Daniel Chudnov wrote: > Toll the bells, > Alert the whole media! > unAPI 1's done! > > Just one API > for all your identified > objects and formats; > > Just one simple way > to tell the world: "Here, copy > our stuff! Use the IDs!" > > We battled some -- > sometimes identifiers > will lead to battles. > > But then we converged, > coagulated, even, > after Corvallis. > > And now we all know: > for macroformat copies, > just use unAPI. > > Long live ROGUE '05! > (So we took an extra month... > who cares? It's done now.) > > Beers for everybody -- > I'm buying! Not in New Haven? > Next conference, then. > > Until then, toll bells, > unAPIfy your webapps, > and blog all the links! > > Or even better, > help write the intro paper! > Send text, and screenshots. > > Please! Please, please, please, please! > (Please X7) > (Please x5) > > Oh yeah -- one more thing. > Where should you go for the specs? > unapi.info! > > > > (Thanks everybody! -Dan) > > > > _______________________________________________ > gcs-pcs-list mailing list > gcs-pcs-list@cipolo.med.yale.edu > http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list > -- Mike Rylander mrylander@gmail.com GPLS -- PINES Development Database Developer http://open-ils.org From lists at hubmed.org Mon Jun 26 06:21:22 2006 From: lists at hubmed.org (Alf Eaton) Date: Mon Jun 26 06:25:29 2006 Subject: [gcs-pcs-list] templated links Message-ID: While unAPI ended up using variables in its URLs - so as to be simple to implement - the idea of link templating: http://www.mnot.net/blog/2006/06/22/link and http://lists.w3.org/Archives/Public/www-tag/2006Jun/0008 looks like it could still be relevant (perhaps)... alf. From lists at hubmed.org Mon Jun 26 08:31:22 2006 From: lists at hubmed.org (Alf Eaton) Date: Mon Jun 26 08:35:24 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: References: Message-ID: On 24 Jun 2006, at 01:24, Daniel Chudnov wrote: > > Where should you go for the specs? > unapi.info! > I know it says in the spec that "URIs intentionally not URL-encoded for readability", but I only found that after searching for anything about encoding... I think that the identifiers in the spec should be uri-encoded and this should be stated explicitly. alf. From ross.singer at library.gatech.edu Mon Jun 26 09:43:59 2006 From: ross.singer at library.gatech.edu (Ross Singer) Date: Mon Jun 26 09:50:48 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: References: Message-ID: <23b83f160606260643v7d13dbdbw517a12e4fd2295f9@mail.gmail.com> On 6/26/06, Alf Eaton wrote: > I know it says in the spec that "URIs intentionally not URL-encoded > for readability", but I only found that after searching for anything > about encoding... I think that the identifiers in the spec should be > uri-encoded and this should be stated explicitly. +1 -Ross. > > alf. > _______________________________________________ > gcs-pcs-list mailing list > gcs-pcs-list@cipolo.med.yale.edu > http://cipolo.med.yale.edu/mailman/listinfo/gcs-pcs-list > > From daniel.chudnov at yale.edu Mon Jun 26 11:25:19 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Mon Jun 26 11:25:51 2006 Subject: [gcs-pcs-list] templated links In-Reply-To: References: Message-ID: <20060626152516.GC32025@sildin.med.yale.edu> Alf Eaton wrote, on Mon, Jun 26, 2006 at 11:21:22AM +0100: > While unAPI ended up using variables in its URLs - so as to be simple > to implement - the idea of link templating: > http://www.mnot.net/blog/2006/06/22/link > and > http://lists.w3.org/Archives/Public/www-tag/2006Jun/0008 > looks like it could still be relevant (perhaps)... unAPI only includes the microformat and the link pattern because there weren't already obvious and simple-enough ways to do either. We should be able to project an unAPI service into link templates easily, right? e.g.: Link-Template: ; rel="unapi" This seems like a good idea. Maybe an object-view page could even enumerate its formats with Link: headers too. -Dan -- Daniel Chudnov Yale Center for Medical Informatics (203) 737-5789 From lists at hubmed.org Tue Jun 27 10:03:05 2006 From: lists at hubmed.org (Alf Eaton) Date: Tue Jun 27 10:07:25 2006 Subject: [gcs-pcs-list] unapi discovery with greasemonkey Message-ID: <3BE3D74A-0852-4972-80FE-D631761F4A1F@hubmed.org> Here's a greasemonkey script, based on Xiaoming's earlier version, that puts a link (unicode scissors for now) wherever there's a unapi id. When clicked, the link shows a list of available export formats. http://alf.hubmed.org/unapi_link_b.user.js I've tried to restrict the unapi server to the same domain as the original page, though not entirely successfully yet. I'm still trying to figure out whether allowing any domain is a security problem or not. You can try it here: http://www.hubmed.org/search.cgi?q=test alf. From daniel.chudnov at yale.edu Tue Jun 27 10:32:38 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Tue Jun 27 10:34:16 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: References: Message-ID: <9550DEDA-975A-4ECF-BD4C-E2C51AD3DCAE@yale.edu> On Jun 26, 2006, at 8:31 AM, Alf Eaton wrote: > > I know it says in the spec that "URIs intentionally not URL-encoded > for readability", but I only found that after searching for > anything about encoding... I think that the identifiers in the > spec should be uri-encoded and this should be stated explicitly. This issue was raised during development, and, for better or worse, the present changes were found acceptable. That said, it seems useful to move that statement up a little higher to where the first identifier occurs; also, it should say "identifier", not "URI". So - you're right, it would be better with these fixes. But, the spec is done; the process is over. It seems worthwhile to fix the typo and move the existing explanatory text up, but not worthwhile to overturn a group decision to newly encode the identifiers. -Dan From lists at hubmed.org Tue Jun 27 10:47:54 2006 From: lists at hubmed.org (Alf Eaton) Date: Tue Jun 27 10:48:55 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: <9550DEDA-975A-4ECF-BD4C-E2C51AD3DCAE@yale.edu> References: <9550DEDA-975A-4ECF-BD4C-E2C51AD3DCAE@yale.edu> Message-ID: <564F6570-D9B3-4DE1-8FE2-28C4A01BBED2@hubmed.org> On 27 Jun 2006, at 15:32, Daniel Chudnov wrote: > On Jun 26, 2006, at 8:31 AM, Alf Eaton wrote: >> >> I know it says in the spec that "URIs intentionally not URL- >> encoded for readability", but I only found that after searching >> for anything about encoding... I think that the identifiers in >> the spec should be uri-encoded and this should be stated explicitly. > > This issue was raised during development, and, for better or worse, > the present changes were found acceptable. That said, it seems > useful to move that statement up a little higher to where the first > identifier occurs; also, it should say "identifier", not "URI". > > So - you're right, it would be better with these fixes. But, the > spec is done; the process is over. It seems worthwhile to fix the > typo and move the existing explanatory text up, but not worthwhile > to overturn a group decision to newly encode the identifiers. I'm looking, but all I can find in the archives is the bit where we decided *not* to remove the line "URIs in unAPI HTTP calls must be url-encoded", and nothing about the examples. Does anyone have a link to the discussion? alf. From daniel.chudnov at yale.edu Tue Jun 27 11:43:02 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Tue Jun 27 11:44:40 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: <564F6570-D9B3-4DE1-8FE2-28C4A01BBED2@hubmed.org> References: <9550DEDA-975A-4ECF-BD4C-E2C51AD3DCAE@yale.edu> <564F6570-D9B3-4DE1-8FE2-28C4A01BBED2@hubmed.org> Message-ID: On Jun 27, 2006, at 10:47 AM, Alf Eaton wrote: >> >> So - you're right, it would be better with these fixes. But, the >> spec is done; the process is over. It seems worthwhile to fix the >> typo and move the existing explanatory text up, but not worthwhile >> to overturn a group decision to newly encode the identifiers. > > I'm looking, but all I can find in the archives is the bit where we > decided *not* to remove the line "URIs in unAPI HTTP calls must be > url-encoded", and nothing about the examples. Does anyone have a > link to the discussion? Reviewing things, it looks like you're right that nothing was explicitly agreed about the examples. On the other hand, many weeks passed after the rewrite and this issue was not brought up again, so, "it was found acceptable" isn't totally inaccurate, though calling it "a group decision" was wrong on my part. There's no other way to say this: the spec is done, the time for discussion is over. I can make the changes listed above, which directly address the clarity and accuracy of the spec as written, but that's it. We all need to move on and get on with using unAPI instead of fiddling over it... it's good enough. -Dan From jeremy.frumkin at oregonstate.edu Tue Jun 27 13:02:07 2006 From: jeremy.frumkin at oregonstate.edu (Jeremy Frumkin) Date: Tue Jun 27 13:03:15 2006 Subject: [gcs-pcs-list] Additional Supporting Docs? [Was: unAPI Version 1] Message-ID: Alf mused: "I know it says in the spec that "URIs intentionally not URL-encoded for readability", but I only found that after searching for anything about encoding... I think that the identifiers in the spec should be uri-encoded and this should be stated explicitly." I think it would be great to have examples of uri-encoded identifiers - but I also agree that the spec is written and there was sufficient time for input prior to it being published. I do see an opportunity here, though. Alf - how about creating a supplemental doc that provides examples of URI-encoding identifiers within the unAPI spec? I believe this would be a good way to accommodate this, and it also enhances the unAPI effort by starting the process of creating supplementary docs which help developers, implementers, etc. (As a suggestion, this document could be created directly on the wiki (http://unapi.stikipad.com/unapi/show/HomePage), or placed there once written.) -- jaf =============================================== Jeremy Frumkin The Gray Chair for Innovative Library Services 121 The Valley Library, Oregon State University Corvallis OR 97331-4501 Jeremy.Frumkin@oregonstate.edu 541.737.9928 541.737.3453 (Fax) 541.230.4483 (Cell) =============================================== " Without ambition one starts nothing. Without work one finishes nothing. " - Emerson From lists at hubmed.org Tue Jun 27 13:11:22 2006 From: lists at hubmed.org (Alf Eaton) Date: Tue Jun 27 13:12:22 2006 Subject: [gcs-pcs-list] Additional Supporting Docs? [Was: unAPI Version 1] In-Reply-To: References: Message-ID: <1CD462BF-6345-4CA4-ADEB-16FFD3B86FB8@hubmed.org> On 27 Jun 2006, at 18:02, Jeremy Frumkin wrote: > Alf mused: > > "I know it says in the spec that "URIs intentionally not URL-encoded > for readability", but I only found that after searching for anything > about encoding... I think that the identifiers in the spec should be > uri-encoded and this should be stated explicitly." > > I think it would be great to have examples of uri-encoded > identifiers - but > I also agree that the spec is written and there was sufficient time > for > input prior to it being published. I do see an opportunity here, > though. There was time for input, and in that time we agreed not to take out the line about identifiers being URI-encoded, but somehow it disappeared. Unfortunately I was busy the last few weeks and didn't have a chance to try out the spec. Personally I don't think it's a good idea to freeze a spec until it's been properly tested in practice (which this hasn't been, yet, in my opinion). > Alf - how about creating a supplemental doc that provides examples of > URI-encoding identifiers within the unAPI spec? I believe this > would be a > good way to accommodate this, and it also enhances the unAPI effort by > starting the process of creating supplementary docs which help > developers, > implementers, etc. (As a suggestion, this document could be created > directly > on the wiki (http://unapi.stikipad.com/unapi/show/HomePage), or > placed there > once written.) I think this is such a fundamental part of the specification that it should be included in the main document. alf. From jeremy.frumkin at oregonstate.edu Tue Jun 27 13:26:34 2006 From: jeremy.frumkin at oregonstate.edu (Jeremy Frumkin) Date: Tue Jun 27 13:27:41 2006 Subject: [gcs-pcs-list] Additional Supporting Docs? [Was: unAPI Version 1] In-Reply-To: <1CD462BF-6345-4CA4-ADEB-16FFD3B86FB8@hubmed.org> Message-ID: Alf stated: > > I think this is such a fundamental part of the specification that it > should be included in the main document. Be that as it may, the spec is at 1.0 and I don?t believe it is going to change now. So, given that constant, I still think a viable option is to produce a supplementary doc. -- jaf =============================================== Jeremy Frumkin The Gray Chair for Innovative Library Services 121 The Valley Library, Oregon State University Corvallis OR 97331-4501 Jeremy.Frumkin@oregonstate.edu 541.737.9928 541.737.3453 (Fax) 541.230.4483 (Cell) =============================================== " Without ambition one starts nothing. Without work one finishes nothing. " - Emerson -------------- next part -------------- An HTML attachment was scrubbed... URL: http://cipolo.med.yale.edu/pipermail/gcs-pcs-list/attachments/20060627/749af09d/attachment.htm From liu_x at lanl.gov Tue Jun 27 13:45:32 2006 From: liu_x at lanl.gov (Xiaoming Liu) Date: Tue Jun 27 13:44:29 2006 Subject: [gcs-pcs-list] Additional Supporting Docs? [Was: unAPI Version 1] In-Reply-To: References: Message-ID: On Tue, 27 Jun 2006, Jeremy Frumkin wrote: > Alf stated: >> >> I think this is such a fundamental part of the specification that it >> should be included in the main document. > > > Be that as it may, the spec is at 1.0 and I don?t believe it is going to > change now. So, given that constant, I still think a viable option is to > produce a supplementary doc. w3c recommendation has an errata section, such as: http://www.w3.org/TR/REC-xml-names/ http://www.w3.org/XML/xml-names-19990114-errata The errata page is directly linked from the spec, so this might be a pattern we can use? xiaoming From eric at openly.com Wed Jun 28 12:43:33 2006 From: eric at openly.com (Eric Hellman) Date: Wed Jun 28 12:45:24 2006 Subject: [gcs-pcs-list] [ANNOUNCE] unAPI Version 1 In-Reply-To: <9550DEDA-975A-4ECF-BD4C-E2C51AD3DCAE@yale.edu> References: <9550DEDA-975A-4ECF-BD4C-E2C51AD3DCAE@yale.edu> Message-ID: I found the discussion of the URL encoding stuff very confused when I brought it up way back when, and I apologize for wandering off.. >On Jun 26, 2006, at 8:31 AM, Alf Eaton wrote: >> >>I know it says in the spec that "URIs intentionally not URL-encoded >>for readability", but I only found that after searching for >>anything about encoding... I think that the identifiers in the >>spec should be uri-encoded and this should be stated explicitly. > >This issue was raised during development, and, for better or worse, >the present changes were found acceptable. That said, it seems >useful to move that statement up a little higher to where the first >identifier occurs; also, it should say "identifier", not "URI". > >So - you're right, it would be better with these fixes. But, the >spec is done; the process is over. It seems worthwhile to fix the >typo and move the existing explanatory text up, but not worthwhile >to overturn a group decision to newly encode the identifiers. > > -Dan -- Eric Hellman, Director OCLC Openly Informatics Division eric@openly.com 2 Broad St., Suite 208 tel 1-973-509-7800 fax 1-734-468-6216 Bloomfield, NJ 07003 http://www.openly.com/1cate/ 1 Click Access To Everything From daniel.chudnov at yale.edu Wed Jun 28 15:20:01 2006 From: daniel.chudnov at yale.edu (Daniel Chudnov) Date: Wed Jun 28 15:20:34 2006 Subject: [gcs-pcs-list] *scheduled downtime* - this list, soon Message-ID: <20060628192001.GE3717@sildin.med.yale.edu> Due to substantial building maintenance, the host that serves this list will be unavailable for several hours starting almost *immediately*. It will likely remain unavailable until late tonight or early tomorrow, at which time this list should return to service as usual. I'm sorry for the late warning. -Dan -- Daniel Chudnov Yale Center for Medical Informatics (203) 737-5789