Re: Web Linking and @rev
Mark Nottingham wrote: Hi Kingsley, We've been back and forth on this issue a *lot*. The current solution is still to define the syntax, but not the semantics, of rev, because we can't come to consensus on it, and it's widely agreed that it isn't well-used in many cases (not necessarily yours). Regards, I know there has been a lot of back and forth on this matter. Situation as you describe it: Nobody has arrived a consensus about something that isn't widely used. Thus, our emerging use case should really be preserved since there isn't any collateral damage :-) I could understand if it was widely used in a variety of ways, but this clearly isn't the case, so I think we can also safely own the semantics of this for now since its being put into very practical use. Kingsley On 12/05/2010, at 11:00 PM, Kingsley Idehen wrote: Mark, I just read your note [1] re. @rev. Is it judicious to drop @rev just on the basis of potential confusion? In reality, we used @rev in DBpedia to completely demystify what's happening re. Linked Data i.e., the critical relation between a Descriptor Documents and its Unambiguously Named (via Generic HTTP URI) Subject. In one single URL-rewrite move we've been able to solve a complex and typically jargon ladened riddle. If you veer people away from @rev, we are taking steps backward. Links: 1. http://xml.coverpages.org/draft-nottingham-http-link-header-10.txt -- Web Linking Note 2. http://mediterraneanceramics.blogspot.com/2010/05/document-and-concept-this-and-how.html -- a post about Descriptor Documents and their Unambiguously Named Subjects . -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen -- Mark Nottingham http://www.mnot.net/ -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
VIVO Annual Conference, Aug 12-13, 2010, New York, USA
+++ Call for Papers The first annual VIVO National Conference will be held August 12 and 13 at the New York Hall of Science. We are pleased to invite you to participate in the conference with contributions to the meeting. We are requesting papers, panels, and poster presentations focusing on issues that VIVO is trying to address, including these listed in the Topics of Interest. Topics of interest: Collaboration Semantic WebLinked Open Data Role of VIVO in Science Adoption of VIVOImplementation of VIVO Social Networking Crowd Sourcing Mapping Networks Submission: Authors are invited to submit abstracts for poster, panel, and paper presentations related to the Topics of Interest and associated areas. All paper submissions will be handled electronically. Authors should sign up for an account and submit their abstract and the completed submission form at the conference submission site, http://www.easychair.org/conferences/?conf=vivo1. Proposals must be submitted as a one-page (8.5 x 11 inch) document [PDF or Microsoft Word format]. Each submission should not exceed one page typeset in 12-point font and must include: • The title of the submission and the names, academic degree(s), affiliations, and locations (city, state, and country) of all authors • An abstract which summarizes the submission and offers the reviewers a clear reflection of the contents and key points of the coming presentation, panel, or poster. Abstracts will undergo the peer-review process and the reviewing process is strictly confidential. Categories of submission: • Papers: Authors will be considered for either a full-length presentation of 45 minutes, with 10 minutes for questions or for inclusion into a collection of presentations to be delivered during a single session. These shorter presentations will be 10 minutes long with 5 minutes for questions. Please indicate your preference (short or long talk) on your submission. • Posters: Poster presentations offer an excellent opportunity to present preliminary research and projects and offer a platform for dialog on the subject. • Panels: Panels may be organized around a specific topic or may offer an innovative approach that cuts across multiple topic areas, technologies, experiences, or disciplines. There should be no more than four panelists in a given panel session. Important Dates: • Abstracts due: June 15, 2010 • Decision: July 15, 2010 Accepted papers will be presented by their author(s) and will be published in the conference proceedings. The proceedings are provided free of charge to conference attendees. For further details or inquiries, please contact Kristi Holmes at holme...@wustl.edu. _ Kristi L. Holmes, Ph.D. | Bioinformaticist | Becker Medical Library | Washington University School of Medicine 660 S. Euclid, Campus Box 8132, St. Louis, MO 63110 | 314-362-4737 | holme...@wusm.wustl.edu | Blog
Fine-grained LOD and managing network traffic?
Chimezie raised some interesting points about the possibility of network congestion given the LOD practice of HTTP URIs everywhere. http://copia.posterous.com/click-here-to-set-a-post-title-149 I know that this is in part why the hasher camp became dominant, as same-origin restriction reduces network load when you use hashes at fine grain. But I think figuring put that coarse-grained/fine-grained boundary is one of the main open architectural issues of LOD, so I found it useful to follow some analysis on the matter. I figured I'd mention it because I think the discussion of PURL infrastructure and federation that came up on this list recently is important for boosting the iron, but I think the issues Chimezie brings up are analogous to working out optimization of algorithmic complexity. -- Uche Ogbuji http://uche.ogbuji.net Weblog: http://copia.ogbuji.net Poetry ed @TNB: http://www.thenervousbreakdown.com/author/uogbuji/ Founding Partner, Zepheirahttp://zepheira.com Linked-in: http://www.linkedin.com/in/ucheogbuji Articles: http://uche.ogbuji.net/tech/publications/ Friendfeed: http://friendfeed.com/uche Twitter: http://twitter.com/uogbuji http://www.google.com/profiles/uche.ogbuji
