- From: Hammond, Tony <t.hammond@nature.com>
- Date: Fri, 02 Jul 2010 14:19:21 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>, "Hondros, Constantine" <Constantine.Hondros@wolterskluwer.com>
- CC: "public-lod@w3.org" <public-lod@w3.org>
Hi Kingsley: > Kill me with the PDF URL :-( I think we could have been a tad more gracious here. This kind of remark only serves to alienate the well intentioned. You know, it's not actually (yet) a crime to put out a PDF on the open Web. Yes, it may not be the most "webby" of document formats but it does have certain viabilities. Re your question: > Where can I see GET the RDF/XML resource? What on earth does this really mean? Which "resource" do you want to see? The link that was forwarded by the enquirer was to a specification document for generating resources with standalone RDF/XML descriptions as well as to embedded XMP (RDF/XML) packets. I'm not sure why that specification especially needs to be in RDF/XML. But there is an .rdfs [1] that I contributed to a somewhat older version of PRISM (1.2) if that helps you any. It needs to be updated and improved. As to the original query, there is already a large body of RDF/XML documents using PRISM available from academic publishers who have used it especially in their RSS feeds - and have been using it for > 5 years. See this RSS Best Practices document [2] from CrossRef - the organization promoting citation linking - which recommends that journals publishers use RSS 1.0 (i.e. the RDF flavour) and also that they use DC and PRISM for fuller descriptions. Also CrossRef are working on a similar document to encourage publishers to add XMP packets (with DC and PRISM) into their PDFs. Note that a couple of larger publishers are routinely adding XMP packets to their PDFs, and CrossRef is also devloping tools for smaller publishers [3]. (And I suppose if publishers must out PDFs then they are atoning to some degree in adding RDF/XML descriptions to these documents.;) So, at least on the scholarly publishing front there are ongoing efforts to make PRISM metadata terms available within RDF descriptions. Cheers, Tony [1] http://www.idealliance.org/filefolder/prism.rdfs [2] http://oxford.crossref.org/best_practice/rss/ [3] http://www.crossref.org/CrossTech/2009/12/add_crossref_metadata_to_pdfs.html On 1/7/10 22:37, "Kingsley Idehen" <kidehen@openlinksw.com> wrote: > Hondros, Constantine wrote: >> >> Has any PRISM content ever made it into the LOD cloud? >> >> >> >> PRISM (Publishing Requirements for Industry Standard Metadata) is a >> metadata standard that can be encoded as RDF/XML (as well as XML, and >> XMP), which has been developed by an impressive industry consortium >> [1], and which, as far as I can tell, is being actively used. >> >> >> >> In other words, just the sort of high quality metadata we would hope >> to have in the LOD cloud, right? End-points, anyone? >> >> >> >> [1] http://www.prismstandard.org/PRISMUsers.pdf >> >> > > Kill me with the PDF URL :-( > > Where can I see GET the RDF/XML resource? On 1/7/10 22:37, "Kingsley Idehen" <kidehen@openlinksw.com> wrote: > Hondros, Constantine wrote: >> >> Has any PRISM content ever made it into the LOD cloud? >> >> >> >> PRISM (Publishing Requirements for Industry Standard Metadata) is a >> metadata standard that can be encoded as RDF/XML (as well as XML, and >> XMP), which has been developed by an impressive industry consortium >> [1], and which, as far as I can tell, is being actively used. >> >> >> >> In other words, just the sort of high quality metadata we would hope >> to have in the LOD cloud, right? End-points, anyone? >> >> >> >> [1] http://www.prismstandard.org/PRISMUsers.pdf >> >> >> ------------------------------------------------------------------------ >> This email and any attachments may contain confidential or privileged >> information >> and is intended for the addressee only. If you are not the intended >> recipient, please >> immediately notify us by email or telephone and delete the original >> email and attachments >> without using, disseminating or reproducing its contents to anyone >> other than the intended >> recipient. Wolters Kluwer shall not be liable for the incorrect or >> incomplete transmission of >> of this email or any attachments, nor for unauthorized use by its >> employees. >> >> Wolters Kluwer nv has its registered address in Alphen aan den Rijn, >> The Netherlands, and is registered >> with the Trade Registry of the Dutch Chamber of Commerce under number >> 33202517. > > Kill me with the PDF URL :-( > > Where can I see GET the RDF/XML resource? ******************************************************************************** DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Neither Macmillan Publishers Limited nor any of its agents accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Macmillan Publishers Limited or one of its agents. Please note that neither Macmillan Publishers Limited nor any of its agents accept any responsibility for viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any). No contracts may be concluded on behalf of Macmillan Publishers Limited or its agents by means of e-mail communication. Macmillan Publishers Limited Registered in England and Wales with registered number 785998 Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS ********************************************************************************
Received on Friday, 2 July 2010 13:20:04 UTC