[OAI-implementers] Requesting a part of a record possible wit
Thu, 22 Jan 2004 11:27:19 +0200
it looks most interesting ... here are some thoughts:
- your descriptions are for an independent external registry, while i
was proposing a "friends"-like services offered on the same archive. as
such, "title" would be a moot point, while you (rightly) require it.
- your service identifiers are assigned by a central authority - with a
self-description, that should not be necessary (and may even violate
some information independence principles)
- you do not have a formal identifier for the protocol and i think that
is quite important to match clients and servers for services. i was
suggesting the canonical URI of the protocol specification. if someone
comes up with a new CGI-based protocol, they SHOULD have a specification
written down somewhere, otherwise i don't see the point of advertising
the interface publicly.
- WSDL is tricky. did you use the draft spec or the technical note?
there are encoding differences between the two, so until this becomes a
standard, i am keeping my distance.
- access rights may be useful. administrator may be covered already (by
adminEmail). contributor is again not relevant in this case, but i see
that that is optional anyway so it doesnt matter.
so ... do you think these differing requirements can be merged? (im
still not sure where/how i will use this yet, but at least a few other
seem interested as well).
Andy Powell wrote:
> On Wed, 21 Jan 2004, Young,Jeff wrote:
>>I was thinking of using custom description schemas to define these things
>>for the ERRoL service, but if there is a commonly accepted mechanism, all
> The JISC Information Environment Service Registry Pilot Project (cor
> blimey, that's a bit of a mouthful! :-) ) is developing an experimental
> registry of the collections and services that make up the UK higher
> education information landscape. See
> for details. As part of this work, the project has developed an
> 'application profile' for describing various kinds of services, including
> Z, SRW, SOAP, CGI, RSS, OAI-PMH, etc.
> I'm not sure how easy you'll find it to work your way thru the pages, but
> the application profile and some examples are linked from:
> You'll note that for SOAP-based services like SRW, the 'service'
> descriptions link to an external WSDL file, rather than re-inventing the
> Distributed Systems, UKOLN, University of Bath, Bath, BA2 7AY, UK
> http://www.ukoln.ac.uk/ukoln/staff/a.powell/ +44 1225 383933
> Resource Discovery Network http://www.rdn.ac.uk/
> OAI-implementers mailing list
> List information, archives, preferences and to unsubscribe:
hussein suleman ~ firstname.lastname@example.org ~ http://www.husseinsspace.com