Browse files

Added profile doc

  • Loading branch information...
1 parent 60388f6 commit 0fa92d67f8a835b9659d9aa27117f69c6a706a7d @iand committed Jul 29, 2012
Showing with 33 additions and 18 deletions.
  1. +1 −18
  2. +32 −0 profile.html
@@ -428,31 +428,14 @@ This section lists some common schemas in a format suitable for including in an
The following implementations of the embedding scheme described in this document are available:
-* [An XSLT stylesheet implementing the rules described in this document](
+* [An XSLT stylesheet implementing the rules described in this document]( (**Editorial Note:** now at
* [A transformation service using the above stylesheet](
* [Embeddable RDF parser]( in [ARC](, see [webservice](
# Further Reading
**Editorial Note:** These links have been moved to the github [repository wiki](
-* Limitations of Embedding RDF in HTML
-* Summary of Triple Production Rules
-* RSS in HTML
-* RDF Schemas in HTML
-* Embedded RDF Profile Document
-**Editorial Note:** Ian Davis wrote several blog posts about erdf:
-* [Naked Metadata Using Embedded RDF](
-* [Enhancing Embedded RDF](
-* [Embedded Trackbacks](
-* [Classes In Embedded RDF](
-* [Towards Copy and Paste eRDF](
# References
This document has drawn on several long-standing conventions:
32 profile.html
@@ -0,0 +1,32 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">
+<html xmlns="" xml:lang="en" lang="en"><head profile="">
+ <meta content="HTML Tidy for Windows (vers 1st February 2003), see" name="generator">
+ <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <title>
+ Embedded RDF HTML Profile
+ </title>
+ <link rel="transformation" href="">
+ </head>
+ <body>
+ <div id="content">
+ <h1>
+ Embedded RDF HTML Profile
+ </h1>
+ <p>A GRDDL-capable client tool, when visiting a page which contains the profile reference <code></code>
+ will first visit this profile document and apply the
+transformation declared here. The results of that transformation will
+contain a statement identifying the transformation that should be
+applied to
+convert the originating document into RDF/XML. The GRDDL client has
+everything it
+needs to get RDF/XML from the original XHTML document, while the author
+the originating document need not concern themselves with the details of
+ the
+profile, merely including the reference to its URI is enough. </p>
+ <p>This following link provides the statement : <a rel="profileTransformation" href="">extract-rdf.xsl</a>, <a rel="profile" href="">profile</a></p>
+ </div>

0 comments on commit 0fa92d6

Please sign in to comment.