Re: Issue 74 in void-impl: Revisiting voiD discovery
void...@googlecode.com
http://code.google.com/p/void-impl/issues/detail?id=74
This issue is no longer blocking issue 82.
See http://code.google.com/p/void-impl/issues/detail?id=82
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
void...@googlecode.com
Comment #4 on issue 74 by rich...@cyganiak.de: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
I think in detail we should do this, in order:
1. Remove Section 7.2 from the Guide
2. Explain in the beginning of Section 7 that previous versions of voiD had
a discovery mechanism based on robots.txt and Semantic Sitemaps, which was
deprecated because it was not widely adopted. Include a link to
http://vocab.deri.ie/void/guide/2009-01-29
3. Explain in the beginning of Section 7 that a new discovery mechanism
will be defined in the future in a separate document, linking to
http://vocab.deri.ie/void/autodiscovery
4. Create a one-sentence placeholder document at
http://vocab.deri.ie/void/autodiscovery
5. Get the *draft* of the Note published in W3C space
6. Write a submission to IETF for a name under .well-known.
7. Draft the autodiscovery document: Describe the .well-known mechanism,
and explain that IETF approval is pending.
void...@googlecode.com
Comment #5 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
Done step 1-3 in r172 however, vocab.deri.ie is down ATM, so need to wait
till this is sorted to do the rest
void...@googlecode.com
Comment #6 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
Update: vocab.deri.ie is back online, added
http://vocab.deri.ie/void/autodiscovery - please review content
void...@googlecode.com
http://code.google.com/p/void-impl/issues/detail?id=74
This issue is no longer blocking issue 85.
See http://code.google.com/p/void-impl/issues/detail?id=85
void...@googlecode.com
Comment #7 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
Notes that the registry is located at
http://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml
void...@googlecode.com
Comment #8 on issue 74 by uoc...@googlemail.com: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
hi - Have steps 5-7 and a submission to IETF taken place yet ? In the
interim, if Im creating a VoID document, should I continue with
sitemap/robots or use the .well-known mechanism ?
void...@googlecode.com
Comment #9 on issue 74 by rich...@cyganiak.de: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
Submission has not yet taken place. I expect that the entire registration
process will take at least another few weeks.
My recommendation: If you already have the robots.txt/sitemap thing in
place, then just leave it like that. Otherwise, publish the voiD file
without autodiscovery, and wait for the process to complete.
void...@googlecode.com
Comment #10 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
I've implemented all the changes as discussed during today's (2011-01-20)
voiD editor's call and now ready to submit to IETF.
void...@googlecode.com
Comment #11 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
The request has been sent [1] - review period ends in 14 days (that is, 3
Feb 2011).
[1] https://groups.google.com/d/topic/void-discussion/EnADedkV9kU/discussion
void...@googlecode.com
Comment #12 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
As per today's (2011-02-01) editors call we decided that we'll publish the
VoID guide as SWIG Note and then come back to IETF to register it (ETA:
mid/end of Feb 2011)
void...@googlecode.com
Comment #13 on issue 74 by rich...@cyganiak.de: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
I took an action to draft a replacement for the placeholder autodiscovery
section 7.2, along with clarifications regarding the relationship between
hostnames and datasets. Proposed text is below.
Replace Section 7.2, “Discovery with well-known URI”:
<p><a href="http://tools.ietf.org/html/rfc5785">RFC 5758</a> [<a
href="#ref-RFC5758">RFC5758</a>] defines a mechanism for reserving
“well-known” URIs on any web server.</p>
<p>The URI <code>/.well-known/void</code> on any web server is reserved for
a VoID description of any datasets hosted on that server. For example, on
the host <code>www.example.com</code>, this URI would be
<code>http://www.example.com/.well-known/void</code>.</p>
<p>This URI may be an HTTP redirect to the location of the actual VoID
file. The most appropriate HTTP redirect code is 302. Clients accessing
this well-known URI MUST handle HTTP redirects.</p>
<p>The VoID file accessible via the well-known URI should contain
descriptions of all RDF datasets hosted on the server. This includes any
datasets that have resolvable URIs, a SPARQL endpoint, a data dump, or any
other access mechanism (see <a href="#access">Section 3</a>) whose URI is
on the server's hostname.</p>
<p>Any VoID file accessible via the well-known URI should follow the
guidelines set out in <a
href="http://www.w3.org/2001/sw/interest/ED-void-20101216/#void-file">Section
6.2, <em>Publishing a voiD file alongside a dataset</em></a>.</p>
In addition, add this to the end of Section 6.2, “Publishing a voiD file
alongside a dataset”:
<p class="note">In cases where multiple different
<code>void:Dataset</code>s are published on the same website, the easiest
option is usually to create a single <code>void:DatasetDescription</code>
document that describes all of them.</p>
void...@googlecode.com
Status: Started
Comment #14 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
Implemented changes re auto-discovery in VoID guide as of comment #13, see
r185
void...@googlecode.com
Comment #15 on issue 74 by rich...@cyganiak.de: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
FYI: I tweaked the formatting of the text in the IETF registration box in
r186.
void...@googlecode.com
Blockedon: 85
Comment #16 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
(No comment was entered for this change.)
void...@googlecode.com
Status: Fixed
Comment #17 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
Yey! IANA registration completed - see announcement at [1]. Guess it's time
to close the last v2 issue then ;) *party*
void...@googlecode.com
Comment #18 on issue 74 by Michael.Hausenblas: Revisiting voiD discovery
http://code.google.com/p/void-impl/issues/detail?id=74
... and I sure did forget the pointer to the announcement ... here it comes:
https://groups.google.com/d/topic/void-discussion/HNhZeyhYVAs/discussion