[tdwg-tapir] TAPIR and the standardization of SRU
Hello TAPIRians,
I've recently moved from the library world into the biology world, and I'm noticing that TAPIR has a lot in common with the SRU standard that is gaining popularity in the library world. I would like to encourage collaboration between the two communities, and see whether it is possible to forge a single standard out of the two. One major difference is that TAPIR is database-oriented, while SRU is much more document-oriented, but this should be possible to overcome.
SRU has been recently been turned over to the OASIS standards body as source material for developing a general-purpose web services search standard. As a part of this standardization process, the initial draft document has been opened for public comments (see below). If you have comments, you can post them at the URL indicated. If you work for an institution that is a member of OASIS, I believe you can still join the committee and vote on issues related to the standardization.
--- Ryan Scherle --- Digital Data Repository Architect --- NESCent
Begin forwarded message:
---------- Forwarded message ---------- Date: Wed, 7 Nov 2007 14:57:11 -0500 From: Mary McRae mary.mcrae@oasis-open.org To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org Cc: search-ws@lists.oasis-open.org Subject: [search-ws] Public Review of Search Web Services v1.0 Discussion Document
To OASIS members, Public Announce Lists:
The OASIS Search Web Services TC has recently approved for public review the following Discussion Document:
Search Web Services v1.0 Discussion Document
This document: "Search Web Services Version 1.0 - Discussion Document - 2 November 2007", was prepared by the OASIS Search Web Services TC as a strawman proposal, for public review, intended to generate discussion and interest. It has no official status; it is not a Committee Draft. The specification is based on the SRU (Search Retrieve via URL) specification which can be found at http://www.loc.gov/standards/sru/. It is expected that this standard, when published, will deviate from SRU. How much it will deviate cannot be predicted at this time. The fact that the SRU spec is used as a starting point for development should not be cause for concern that this might be an effort to rubberstamp or fasttrack SRU. The committee hopes to preserve the useful features of SRU, eliminate those that are not considered useful, and add features that are not in SRU but are considered useful. The committee has decided to request OASIS to release this as a discussion document. Detailed review of this document is premature at this point and is not requested; feedback on the functionality and approach is solicited. Feedback is requested by December 7.
The public review starts today, 7 November 2007, and ends 7 December 2007. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. Please feel free to distribute this announcement within your organization and to other appropriate mail lists.
More non-normative information about the specification and the technical committee may be found at the public home page of the TC at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at http://www.oasis-open.org/committees/comments/index.php? wg_abbrev=search-ws.
Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at http://lists.oasis-open.org/archives/search-ws-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.
The specification document and related files are available here:
Editable Source: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.doc
PDF: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.pdf
HTML: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html
OASIS and the Search Web Services TC welcome your comments.
Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org web: www.oasis-open.org
Hi Ryan,
Thanks for bringing SRU to our attention. I became aware of the new search-ws OASIS committee when I was looking for more information about SRU (after you posted that question in our FAQ).
By coincidence, TDWG is just about to become an OASIS member to participate in a new biodiversity conservation steering committee. So SRU is now another reason for joining.
I'm still unfamiliar with the OASIS process, but it seems that when TDWG joins OASIS, any TDWG member will be able to get involved with any OASIS group. So if there's anyone in this condition interested in participating in the search-ws group, please let me know (OASIS seems to encourage its members to bring as many people as possible to participate in the groups). Markus and I will in principle become observers of the group.
TAPIR is already a major effort to unify two protocols, and we reached the point of having enough documentation and tools to enable wide adoption by our community - which already started to happen. So although I'm all in favor of joining efforts with other communities and adopting a single standard, I'm not sure what would be feasible (and reasonable) at this point. Anyway, I agree we should try to get involved and see if there are any real opportunities for integration.
Best Regards, -- Renato
On 7 Nov 2007 at 18:10, Ryan Scherle wrote:
Hello TAPIRians, I've recently moved from the library world into the biology world, and I'm noticing that TAPIR has a lot in common with the SRU standard that is gaining popularity in the library world. I would like to encourage collaboration between the two communities, and see whether it is possible to forge a single standard out of the two.One major difference is that TAPIR is database-oriented,while SRU is much more document-oriented, but this should be possible to overcome.
SRU has been recently been turned over to the OASIS standards body as source material for developing a general-purpose web services search standard. As a part of this standardization process, the initial draft document has been opened for public comments (see below). If you have comments, you can post them at the URL indicated. If you work for an institution that is a member of OASIS, I believe you can still join the committee and vote on issues related to the standardization.
--- Ryan Scherle --- Digital Data Repository Architect --- NESCent
Hi Ryan, there is indeed a good deal of similarity between the interfaces exposed by TAPIR and SRU. I suspect there would be mostly superficial alterations required to the TAPIR key+value URL interface to support much of SRU.
As an aside I find it interesting, and somewhat encouraging that the both SRU and TAPIR derive from a common ancestor (z39.50) and though taking divergent development streams, seem to arriving at similar outcomes. Convergent evolution of protocols.
Dave V.
On Nov 7, 2007 3:10 PM, Ryan Scherle res20@duke.edu wrote:
Hello TAPIRians,
I've recently moved from the library world into the biology world, and I'm noticing that TAPIR has a lot in common with the SRU standard that is gaining popularity in the library world. I would like to encourage collaboration between the two communities, and see whether it is possible to forge a single standard out of the two. One major difference is that TAPIR is database-oriented, while SRU is much more document-oriented, but this should be possible to overcome.
SRU has been recently been turned over to the OASIS standards body as source material for developing a general-purpose web services search standard. As a part of this standardization process, the initial draft document has been opened for public comments (see below). If you have comments, you can post them at the URL indicated. If you work for an institution that is a member of OASIS, I believe you can still join the committee and vote on issues related to the standardization.
--- Ryan Scherle --- Digital Data Repository Architect --- NESCent
Begin forwarded message: ---------- Forwarded message ---------- Date: Wed, 7 Nov 2007 14:57:11 -0500 From: Mary McRae mary.mcrae@oasis-open.org To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org Cc: search-ws@lists.oasis-open.org Subject: [search-ws] Public Review of Search Web Services v1.0 Discussion Document
To OASIS members, Public Announce Lists:
The OASIS Search Web Services TC has recently approved for public review the following Discussion Document:
Search Web Services v1.0 Discussion Document
This document: "Search Web Services Version 1.0 - Discussion Document - 2 November 2007", was prepared by the OASIS Search Web Services TC as a strawman proposal, for public review, intended to generate discussion and interest. It has no official status; it is not a Committee Draft. The specification is based on the SRU (Search Retrieve via URL) specification which can be found at http://www.loc.gov/standards/sru/. It is expected that this standard, when published, will deviate from SRU. How much it will deviate cannot be predicted at this time. The fact that the SRU spec is used as a starting point for development should not be cause for concern that this might be an effort to rubberstamp or fasttrack SRU. The committee hopes to preserve the useful features of SRU, eliminate those that are not considered useful, and add features that are not in SRU but are considered useful. The committee has decided to request OASIS to release this as a discussion document. Detailed review of this document is premature at this point and is not requested; feedback on the functionality and approach is solicited. Feedback is requested by December 7.
The public review starts today, 7 November 2007, and ends 7 December 2007. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. Please feel free to distribute this announcement within your organization and to other appropriate mail lists.
More non-normative information about the specification and the technical committee may be found at the public home page of the TC at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=search-ws.
Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at http://lists.oasis-open.org/archives/search-ws-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.
The specification document and related files are available here:
Editable Source: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.doc
PDF: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.pdf
HTML: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html
OASIS and the Search Web Services TC welcome your comments.
Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org web: www.oasis-open.org
tdwg-tapir mailing list tdwg-tapir@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir
Dave,
I suspect the convergence is because they are all heading towards a simple RESTful HTTP GET service rather than by dint of their common ancestry.
If one were to start from scratch today having never seen z39.50 then one would probably come up with something similar.
All the best,
Roger
On 8 Nov 2007, at 03:00, Dave Vieglais wrote:
Hi Ryan, there is indeed a good deal of similarity between the interfaces exposed by TAPIR and SRU. I suspect there would be mostly superficial alterations required to the TAPIR key+value URL interface to support much of SRU.
As an aside I find it interesting, and somewhat encouraging that the both SRU and TAPIR derive from a common ancestor (z39.50) and though taking divergent development streams, seem to arriving at similar outcomes. Convergent evolution of protocols.
Dave V.
On Nov 7, 2007 3:10 PM, Ryan Scherle res20@duke.edu wrote:
Hello TAPIRians,
I've recently moved from the library world into the biology world, and I'm noticing that TAPIR has a lot in common with the SRU standard that is gaining popularity in the library world. I would like to encourage collaboration between the two communities, and see whether it is possible to forge a single standard out of the two. One major difference is that TAPIR is database-oriented, while SRU is much more document-oriented, but this should be possible to overcome.
SRU has been recently been turned over to the OASIS standards body as source material for developing a general-purpose web services search standard. As a part of this standardization process, the initial draft document has been opened for public comments (see below). If you have comments, you can post them at the URL indicated. If you work for an institution that is a member of OASIS, I believe you can still join the committee and vote on issues related to the standardization.
--- Ryan Scherle --- Digital Data Repository Architect --- NESCent
Begin forwarded message: ---------- Forwarded message ---------- Date: Wed, 7 Nov 2007 14:57:11 -0500 From: Mary McRae mary.mcrae@oasis-open.org To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org Cc: search-ws@lists.oasis-open.org Subject: [search-ws] Public Review of Search Web Services v1.0 Discussion Document
To OASIS members, Public Announce Lists:
The OASIS Search Web Services TC has recently approved for public review the following Discussion Document:
Search Web Services v1.0 Discussion Document
This document: "Search Web Services Version 1.0 - Discussion Document - 2 November 2007", was prepared by the OASIS Search Web Services TC as a strawman proposal, for public review, intended to generate discussion and interest. It has no official status; it is not a Committee Draft. The specification is based on the SRU (Search Retrieve via URL) specification which can be found at http://www.loc.gov/standards/sru/. It is expected that this standard, when published, will deviate from SRU. How much it will deviate cannot be predicted at this time. The fact that the SRU spec is used as a starting point for development should not be cause for concern that this might be an effort to rubberstamp or fasttrack SRU. The committee hopes to preserve the useful features of SRU, eliminate those that are not considered useful, and add features that are not in SRU but are considered useful. The committee has decided to request OASIS to release this as a discussion document. Detailed review of this document is premature at this point and is not requested; feedback on the functionality and approach is solicited. Feedback is requested by December 7.
The public review starts today, 7 November 2007, and ends 7 December 2007. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. Please feel free to distribute this announcement within your organization and to other appropriate mail lists.
More non-normative information about the specification and the technical committee may be found at the public home page of the TC at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at http://www.oasis-open.org/committees/comments/index.php? wg_abbrev=search-ws.
Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at http://lists.oasis-open.org/archives/search-ws-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.
The specification document and related files are available here:
Editable Source: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.doc
PDF: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.pdf
HTML: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html
OASIS and the Search Web Services TC welcome your comments.
Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org web: www.oasis-open.org
tdwg-tapir mailing list tdwg-tapir@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir
tdwg-tapir mailing list tdwg-tapir@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir
Hi Roger, I was just pointing out the common ancestry as a curiosity, not implying functional significance. It is encouraging because as you mentioned, there is a general convergence by different communities toward common and hopefully compatible solutions.
Dave V.
Roger Hyam wrote:
Dave,
I suspect the convergence is because they are all heading towards a simple RESTful HTTP GET service rather than by dint of their common ancestry.
If one were to start from scratch today having never seen z39.50 then one would probably come up with something similar.
All the best,
Roger
On 8 Nov 2007, at 03:00, Dave Vieglais wrote:
Hi Ryan, there is indeed a good deal of similarity between the interfaces exposed by TAPIR and SRU. I suspect there would be mostly superficial alterations required to the TAPIR key+value URL interface to support much of SRU.
As an aside I find it interesting, and somewhat encouraging that the both SRU and TAPIR derive from a common ancestor (z39.50) and though taking divergent development streams, seem to arriving at similar outcomes. Convergent evolution of protocols.
Dave V.
On Nov 7, 2007 3:10 PM, Ryan Scherle res20@duke.edu wrote:
Hello TAPIRians,
I've recently moved from the library world into the biology world, and I'm noticing that TAPIR has a lot in common with the SRU standard that is gaining popularity in the library world. I would like to encourage collaboration between the two communities, and see whether it is possible to forge a single standard out of the two. One major difference is that TAPIR is database-oriented, while SRU is much more document-oriented, but this should be possible to overcome.
SRU has been recently been turned over to the OASIS standards body as source material for developing a general-purpose web services search standard. As a part of this standardization process, the initial draft document has been opened for public comments (see below). If you have comments, you can post them at the URL indicated. If you work for an institution that is a member of OASIS, I believe you can still join the committee and vote on issues related to the standardization.
--- Ryan Scherle --- Digital Data Repository Architect --- NESCent
Begin forwarded message: ---------- Forwarded message ---------- Date: Wed, 7 Nov 2007 14:57:11 -0500 From: Mary McRae mary.mcrae@oasis-open.org To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org Cc: search-ws@lists.oasis-open.org Subject: [search-ws] Public Review of Search Web Services v1.0 Discussion Document
To OASIS members, Public Announce Lists:
The OASIS Search Web Services TC has recently approved for public review the following Discussion Document:
Search Web Services v1.0 Discussion Document
This document: "Search Web Services Version 1.0 - Discussion Document - 2 November 2007", was prepared by the OASIS Search Web Services TC as a strawman proposal, for public review, intended to generate discussion and interest. It has no official status; it is not a Committee Draft. The specification is based on the SRU (Search Retrieve via URL) specification which can be found at http://www.loc.gov/standards/sru/. It is expected that this standard, when published, will deviate from SRU. How much it will deviate cannot be predicted at this time. The fact that the SRU spec is used as a starting point for development should not be cause for concern that this might be an effort to rubberstamp or fasttrack SRU. The committee hopes to preserve the useful features of SRU, eliminate those that are not considered useful, and add features that are not in SRU but are considered useful. The committee has decided to request OASIS to release this as a discussion document. Detailed review of this document is premature at this point and is not requested; feedback on the functionality and approach is solicited. Feedback is requested by December 7.
The public review starts today, 7 November 2007, and ends 7 December 2007. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. Please feel free to distribute this announcement within your organization and to other appropriate mail lists.
More non-normative information about the specification and the technical committee may be found at the public home page of the TC at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=search-ws.
Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at http://lists.oasis-open.org/archives/search-ws-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.
The specification document and related files are available here:
Editable Source: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.doc
PDF: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.pdf
HTML: http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html
OASIS and the Search Web Services TC welcome your comments.
Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org web: www.oasis-open.org
tdwg-tapir mailing list tdwg-tapir@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir
tdwg-tapir mailing list tdwg-tapir@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-tapir
participants (4)
-
Dave Vieglais -
Renato De Giovanni -
Roger Hyam -
Ryan Scherle