Sorry for any confusion. SRU 2.0 is not a published standard, it is
currently a work in progress. (Whether you should be writing code to it is
a question that I suggest you take to the SRU list. The draft is mature
enough now that it is a reasonable question to discuss. There are people
writing code to it.)
OASIS wants to be sure that official copies (and they use that term,
"official", whether referring to an approved spec or a draft) reside on
their server. So the copies at LC must be called *unofficial copies* of
the draft (or the spec, when it becomes approved). Again, sorry for the
confusion.
--Ray
----- Original Message -----
From: "Jonathan Rochkind" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, May 17, 2010 3:17 PM
Subject: Re: [CODE4LIB] OASIS SRU and CQL, access to most-current drafts
> Wait, I'm so confused. Is SRU 2.0 actually a published standard, or are
> you just showing us a work in progress that nobody should be writing code
> to yet?
>
> I'm confused because I thought it was just a draft work in progress, but
> then you talk about official vs unofficial copies... an unofficial copy of
> a draft work in progress that isn't a spec yet anyway? Very confused.
>
> If I'm planning on writing software to SRU... do you recommend I use the
> (until now not publically available so I didn't have a choice)
> "unofficial" SRU 2.0 thing, or is that still just a draft work in progress
> nobody should be writing software to yet?
>
> Jonathan
>
> Ray Denenberg, Library of Congress wrote:
>> For those of you who have recently asked about current OASIS drafts of
>> SRU (2.0) and CQL ...
>>
>> The *official* versions reside at OASIS, but because of confusing (and
>> sometimes inaccessible) links, as well as uncertainty about status
>> (because of imbedded dates), we now maintain *unofficial copies* of the
>> most current versions at:
>>
>> http://www.loc.gov/standards/sru/oasis/current/sru-2-0.doc
>> http://www.loc.gov/standards/sru/oasis/current/cql.doc
>>
>> We will continue to maintain copies of the most current version at these
>> URLs.
>>
>> --Ray
>>
>>
|
