In the case of Google Scholar, I found the guidelines to be a bit
intimidating:
http://scholar.google.com/intl/en/scholar/inclusion.html
but not something that would be hard for the RFC publisher to set up in
a few hours based on the PDF form of the RFCs and the rfc-index.xml file.
Actually,
On 05/10/11 17:28, John Levine wrote:
In the case of Google Scholar, I found the guidelines to be a bit
intimidating:
http://scholar.google.com/intl/en/scholar/inclusion.html
but not something that would be hard for the RFC publisher to set up in
a few hours based on the PDF form of the RFCs
On May 10, 2011, at 8:41 AM, Harald Alvestrand wrote:
For some reason, scholar has indexed 151 docs from tools.ietf.org and then
stopped.
If only there was someone who worked at Google on this list who could send an
internal message to get this rectified :-)
--Paul Hoffman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/10/11 6:14 PM, Paul Hoffman wrote:
On May 10, 2011, at 8:41 AM, Harald Alvestrand wrote:
For some reason, scholar has indexed 151 docs from tools.ietf.org and then
stopped.
If only there was someone who worked at Google on this list
--On Tuesday, May 10, 2011 20:22 +0200 Harald Alvestrand
har...@alvestrand.no wrote:
If only there was someone who worked at Google on this list
who could send an internal message to get this rectified
:-)
From what I could tell from the instructions, Scholar is
using some heuristics
On 05/10/2011 10:08 PM, John C Klensin wrote:
--On Tuesday, May 10, 2011 20:22 +0200 Harald Alvestrand
har...@alvestrand.no wrote:
If only there was someone who worked at Google on this list
who could send an internal message to get this rectified
:-)
From what I could tell from the
