Re: [CODE4LIB] Embedding XHTML into RDF
We're doing this in VIVO (www.vivoweb.org). I developed service layer that integrates with VIVO that exposes the RDF as XML (or JSON) and it handles properties which include HTML (some of it is pretty ugly) that is used to render faculty profile pages like this: http://chemistry.cornell.edu/faculty/detail.cfm?netid=hda1 All of the content under the navigation bar has been pulled out of VIVO as RDF. The content under the Research area includes HTML markup in the RDF. The link above is on a site using Coldfusion and there are other sites using Drupal calling my service layer to bring in content from VIVO. -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ethan Gruber Sent: Wednesday, January 11, 2012 2:37 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Embedding XHTML into RDF Hi all, Suppose I have RDF describing an object, and I would like some fairly free-form human generating description about the object (let's say within dcterms:description). Is it semantically acceptable to have XHTML nested directly in this element or would this be considered uncouth for LOD? Thanks, Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
+1 Rob On Thu, Jan 12, 2012 at 9:26 AM, aj...@virginia.edu aj...@virginia.edu wrote: My inclination would be to keep the descriptive snippets in some kind of content store with a good RESTful Web exposure and just use those URLs as the values of description triples in your RDF. Then your RDF is genteel Linked Data and your XHTML can be easily available to integrating services. --- A. Soroka Online Library Environment the University of Virginia Library On Jan 11, 2012, at 11:00 PM, CODE4LIB automatic digest system wrote: From: Ethan Gruber ewg4x...@gmail.com Date: January 11, 2012 3:07:16 PM EST Subject: Re: Embedding XHTML into RDF People are going to use the YUI rich text editor and the output is run through tidy, so that should ensure the well-formedness of the HTML. Right now we have a system where thousands of small XHTML fragments exist as text files in a filesystem (edited manually, practically), which are rendered through wiki software. The fragments have RDFa attributes so that an RDFa python script can interpret wiki pages as RDF on the fly. We need to redesign the system from the ground up, and I'd like to use RDF as the source object. Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
My inclination would be to keep the descriptive snippets in some kind of content store with a good RESTful Web exposure and just use those URLs as the values of description triples in your RDF. Then your RDF is genteel Linked Data and your XHTML can be easily available to integrating services. --- A. Soroka Online Library Environment the University of Virginia Library On Jan 11, 2012, at 11:00 PM, CODE4LIB automatic digest system wrote: From: Ethan Gruber ewg4x...@gmail.com Date: January 11, 2012 3:07:16 PM EST Subject: Re: Embedding XHTML into RDF People are going to use the YUI rich text editor and the output is run through tidy, so that should ensure the well-formedness of the HTML. Right now we have a system where thousands of small XHTML fragments exist as text files in a filesystem (edited manually, practically), which are rendered through wiki software. The fragments have RDFa attributes so that an RDFa python script can interpret wiki pages as RDF on the fly. We need to redesign the system from the ground up, and I'd like to use RDF as the source object. Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
Not sure I would like running across dcterms:description with a URI as its object. Not that dcterms:description has a defined range, but I don't think most agents would expect anything other than some kind of text. Linked data is based at least as much on convention as schema - doing something that disrupts the assumptions of the majority of your consumers seems counterproductive. It'd be like having a URI for dcterms:title (also technically legal): how abstract do you need it? I personally prefer rdf:XMLLiteral (and an untyped, unmarked up version would make sense, too). -Ross. On Thu, Jan 12, 2012 at 11:26 AM, aj...@virginia.edu aj...@virginia.edu wrote: My inclination would be to keep the descriptive snippets in some kind of content store with a good RESTful Web exposure and just use those URLs as the values of description triples in your RDF. Then your RDF is genteel Linked Data and your XHTML can be easily available to integrating services. --- A. Soroka Online Library Environment the University of Virginia Library On Jan 11, 2012, at 11:00 PM, CODE4LIB automatic digest system wrote: From: Ethan Gruber ewg4x...@gmail.com Date: January 11, 2012 3:07:16 PM EST Subject: Re: Embedding XHTML into RDF People are going to use the YUI rich text editor and the output is run through tidy, so that should ensure the well-formedness of the HTML. Right now we have a system where thousands of small XHTML fragments exist as text files in a filesystem (edited manually, practically), which are rendered through wiki software. The fragments have RDFa attributes so that an RDFa python script can interpret wiki pages as RDF on the fly. We need to redesign the system from the ground up, and I'd like to use RDF as the source object. Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
On Thu, Jan 12, 2012 at 11:41 AM, Ross Singer rossfsin...@gmail.com wrote: Oops, dcterms:title, does have a range -- nevermind. Well, nevermind on that example, I still don't like URIs for dcterms:description. -Ross. -Ross. On Thu, Jan 12, 2012 at 11:37 AM, Ross Singer rossfsin...@gmail.com wrote: Not sure I would like running across dcterms:description with a URI as its object. Not that dcterms:description has a defined range, but I don't think most agents would expect anything other than some kind of text. Linked data is based at least as much on convention as schema - doing something that disrupts the assumptions of the majority of your consumers seems counterproductive. It'd be like having a URI for dcterms:title (also technically legal): how abstract do you need it? I personally prefer rdf:XMLLiteral (and an untyped, unmarked up version would make sense, too). -Ross. On Thu, Jan 12, 2012 at 11:26 AM, aj...@virginia.edu aj...@virginia.edu wrote: My inclination would be to keep the descriptive snippets in some kind of content store with a good RESTful Web exposure and just use those URLs as the values of description triples in your RDF. Then your RDF is genteel Linked Data and your XHTML can be easily available to integrating services. --- A. Soroka Online Library Environment the University of Virginia Library On Jan 11, 2012, at 11:00 PM, CODE4LIB automatic digest system wrote: From: Ethan Gruber ewg4x...@gmail.com Date: January 11, 2012 3:07:16 PM EST Subject: Re: Embedding XHTML into RDF People are going to use the YUI rich text editor and the output is run through tidy, so that should ensure the well-formedness of the HTML. Right now we have a system where thousands of small XHTML fragments exist as text files in a filesystem (edited manually, practically), which are rendered through wiki software. The fragments have RDFa attributes so that an RDFa python script can interpret wiki pages as RDF on the fly. We need to redesign the system from the ground up, and I'd like to use RDF as the source object. Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
Oops, dcterms:title, does have a range -- nevermind. -Ross. On Thu, Jan 12, 2012 at 11:37 AM, Ross Singer rossfsin...@gmail.com wrote: Not sure I would like running across dcterms:description with a URI as its object. Not that dcterms:description has a defined range, but I don't think most agents would expect anything other than some kind of text. Linked data is based at least as much on convention as schema - doing something that disrupts the assumptions of the majority of your consumers seems counterproductive. It'd be like having a URI for dcterms:title (also technically legal): how abstract do you need it? I personally prefer rdf:XMLLiteral (and an untyped, unmarked up version would make sense, too). -Ross. On Thu, Jan 12, 2012 at 11:26 AM, aj...@virginia.edu aj...@virginia.edu wrote: My inclination would be to keep the descriptive snippets in some kind of content store with a good RESTful Web exposure and just use those URLs as the values of description triples in your RDF. Then your RDF is genteel Linked Data and your XHTML can be easily available to integrating services. --- A. Soroka Online Library Environment the University of Virginia Library On Jan 11, 2012, at 11:00 PM, CODE4LIB automatic digest system wrote: From: Ethan Gruber ewg4x...@gmail.com Date: January 11, 2012 3:07:16 PM EST Subject: Re: Embedding XHTML into RDF People are going to use the YUI rich text editor and the output is run through tidy, so that should ensure the well-formedness of the HTML. Right now we have a system where thousands of small XHTML fragments exist as text files in a filesystem (edited manually, practically), which are rendered through wiki software. The fragments have RDFa attributes so that an RDFa python script can interpret wiki pages as RDF on the fly. We need to redesign the system from the ground up, and I'd like to use RDF as the source object. Ethan
[CODE4LIB] Embedding XHTML into RDF
Hi all, Suppose I have RDF describing an object, and I would like some fairly free-form human generating description about the object (let's say within dcterms:description). Is it semantically acceptable to have XHTML nested directly in this element or would this be considered uncouth for LOD? Thanks, Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
You might consider the Content in RDF specification: http://www.w3.org/TR/Content-in-RDF10/ which describes how to do this in a generic fashion, as opposed to stuffing it directly into a string literal. HTH Rob On Wed, Jan 11, 2012 at 12:36 PM, Ethan Gruber ewg4x...@gmail.com wrote: Hi all, Suppose I have RDF describing an object, and I would like some fairly free-form human generating description about the object (let's say within dcterms:description). Is it semantically acceptable to have XHTML nested directly in this element or would this be considered uncouth for LOD? Thanks, Ethan
Re: [CODE4LIB] Embedding XHTML into RDF
On Wed, Jan 11, 2012 at 2:36 PM, Ethan Gruber ewg4x...@gmail.com wrote: Hi all, Suppose I have RDF describing an object, and I would like some fairly free-form human generating description about the object (let's say within dcterms:description). Is it semantically acceptable to have XHTML nested directly in this element or would this be considered uncouth for LOD? Free-form human generating is considered uncouth except behind closed doors, but XML literals are explictly provided for - see http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#dfn-rdf-XMLLiteral Simon
