We discourage the use of large RDF/XML dump files in the context of 
GoodRelations, since they are a perfect entry for Denial-of-Service attacks. 
Also, properly deploying RDF/XML resources on production systems is often 
difficult in an enterprise context. Even supporting the rdf/xml media type can 
pose a challenge when there is fine-grained access control on production 
systems.



On Jun 13, 2012, at 3:14 PM, Sebastian Hellmann wrote:

> Dear Martynas,
> the parallel way has some disadvantages in a dynamic context, so I was asking 
> what the latest best practice was to embed RDF in HTML.
> Having a companion or separate RDF file is definitely suitable for most of 
> the use cases, but not always (e.g. in the case of an annotation web service 
> chain).
> Let's say you send around the document to different annotators and each one 
> wants to add annotations in RDF, then you would have to implement CRUD access 
> to the companion RDF file.
> Returning the same document with the annotations embedded is much simpler.
> All the best,
> Sebastian
> 
> 
> On 06/13/2012 02:09 PM, Martynas Jusevičius wrote:
>> Hey Sebastian,
>> 
>> can't you simply use<link rel="alternate" type="application/rdf+xml"
>> href="recshop.rdf">  ?
>> It's not embedding per se, but it's one of the patterns. More info here:
>> http://linkeddatabook.com/editions/1.0/#htoc66 (section "Making RDF
>> Discoverable from HTML")
>> 
>> Martynas
>> graphity.org
>> 
>> On Tue, Jun 12, 2012 at 7:22 PM, Sebastian Hellmann
>> <[email protected]>  wrote:
>>> Dear Mark,
>>> my main concerns are:
>>> 1. What are the best practices to include invisible RDFa in an HTML
>>> document. I think Keith answered that. Maybe at the end of the body would be
>>> the most unobtrusive way.  The same question was raised here:
>>> http://answers.semanticweb.com/questions/10161/is-visually-hidden-rdfa-an-anti-pattern
>>> I just wanted to reassure that hidden RDFa is not contradicting the
>>> intention of RDFa.
>>> Are there any practical disadvantages (besides the obvious increase in byte
>>> size)?
>>> 
>>> 2. Are there any alternatives to RDFa to include RDF in HTML ?
>>> 
>>> All the best,
>>> Sebastian
>>> 
>>> 
>>> 
>>> On 06/12/2012 05:52 PM, Mark Birbeck wrote:
>>>> Hi Sebastian,
>>>> 
>>>> It's not clear to me whether you are saying that you don't want to use
>>>> RDFa because:
>>>> 
>>>> * you don't like it, or;
>>>> 
>>>> * you think that it needs to have some user-oriented manifestation.
>>>> 
>>>> There is no requirement that the RDFa in a document is displayed to
>>>> the user in any way, or that the triples somehow 'double-up'. This
>>>> means that your example could also be marked up like this:
>>>> 
>>>>   <div
>>>>     xmlns:cd="http://www.recshop.fake/cd#";
>>>>     about="http://www.recshop.fake/cd/Empire_Burlesque";
>>>>   >
>>>>      <span property="cd:artist" content="Bob Dylan"></span>
>>>>     <span property="cd:dbpedia"
>>>> resource="http://dbpedia.org/resource/Empire_Burlesque";></span>
>>>>   </div>
>>>> 
>>>> Regards,
>>>> 
>>>> Mark
>>>> 
>>>> 
>>>> On Tue, Jun 12, 2012 at 3:02 PM, Sebastian Hellmann
>>>> <[email protected]>    wrote:
>>>>> Dear list,
>>>>> What are the best practice to include a set of RDF triples in HTML.
>>>>> *Please note*: I am not looking for the RDFa way to include triples. I
>>>>> just
>>>>> want to add a set of triples somewhere in an HTML document. They are not
>>>>> supposed to show up like "Wikinomics", "Don Tapscott" in  the following
>>>>> example:
>>>>> 
>>>>> <div  xmlns:dc="http://purl.org/dc/elements/1.1/";
>>>>>  about="http://www.example.com/books/wikinomics";>
>>>>>  <span  property="dc:title">Wikinomics</span>
>>>>>  <span  property="dc:creator">Don Tapscott</span>
>>>>>  <span  property="dc:date">2006-10-01</span>
>>>>> </div>
>>>>> 
>>>>> I don't want to use the strings in the HTML document as objects in the
>>>>> triples. My use case is that I just have a large set of triples, e.g.
>>>>> 1000
>>>>> that I want to include as a bulk somewhere and ship along with the html.
>>>>> Which way is the best? Do the examples below work?
>>>>> All the best,
>>>>> Sebastian
>>>>> 
>>>>> *******************************************
>>>>> Include in head
>>>>> ******************************************
>>>>> <html>
>>>>> <head>
>>>>> <script type="application/rdf+xml">
>>>>> <rdf:RDF
>>>>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
>>>>> xmlns:cd="http://www.recshop.fake/cd#";>
>>>>> 
>>>>> <rdf:Description
>>>>> rdf:about="http://www.recshop.fake/cd/Empire Burlesque">
>>>>> <cd:artist>Bob Dylan</cd:artist>
>>>>> <cd:dbpedia rdf:resource="http://dbpedia.org/resource/Empire_Burlesque";>
>>>>> </rdf:Description>
>>>>> </rdf:RDF>
>>>>> </script>
>>>>> </head>
>>>>> <body>
>>>>> </body>
>>>>> </html>
>>>>> ******************************
>>>>> attach after html
>>>>> *****************************
>>>>> <html>
>>>>> <head>
>>>>> </head>
>>>>> <body>
>>>>> </body>
>>>>> </html>
>>>>> <rdf:RDF
>>>>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
>>>>> xmlns:cd="http://www.recshop.fake/cd#";>
>>>>> 
>>>>> <rdf:Description
>>>>> rdf:about="http://www.recshop.fake/cd/Empire Burlesque">
>>>>> <cd:artist>Bob Dylan</cd:artist>
>>>>> <cd:dbpedia rdf:resource="http://dbpedia.org/resource/Empire_Burlesque";>
>>>>> </rdf:Description>
>>>>> </rdf:RDF>
>>>>> 
>>>>> 
>>>>> --
>>>>> Dipl. Inf. Sebastian Hellmann
>>>>> Department of Computer Science, University of Leipzig
>>>>> Projects: http://nlp2rdf.org , http://dbpedia.org
>>>>> Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann
>>>>> Research Group: http://aksw.org
>>>>> 
>>>>> 
>>> 
>>> --
>>> Dipl. Inf. Sebastian Hellmann
>>> Department of Computer Science, University of Leipzig
>>> Projects: http://nlp2rdf.org , http://dbpedia.org
>>> Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann
>>> Research Group: http://aksw.org
>>> 
>>> 
> 
> 
> -- 
> Dipl. Inf. Sebastian Hellmann
> Department of Computer Science, University of Leipzig
> Projects: http://nlp2rdf.org , http://dbpedia.org
> Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann
> Research Group: http://aksw.org
> 
> 


Reply via email to