Summary of @href/@resource completing triples issue (v2.0)

Sorry folks, Ben's right, there were several bugs in the last summary...
I'm repeating this because all three of these should turn into test
cases and we need to make sure that they're correct representations of
the issue:

This works for both models:

-----------------------------------------------------------------
<div href="#me">
   <span rel="foaf:knows" href="#ivan">
   <span rel="foaf:knows" href="#shane">
</div>
--------
<#me> foaf:knows <#ivan> .
<#me> foaf:knows <#shane> .
-----------------------------------------------------------------

and this is where the two models differ (note that @rel was moved up to
the containing element and the href is changed to @about):

-----------------------------------------------------------------
<div about="#me" rel="foaf:knows">
   <span href="#ivan">
   <span resource="#shane">
</div>
-------- Approach A triples (Mark)
<#me> foaf:knows <#ivan> .
<#me> foaf:knows <#shane> .
-------- Approach B triples (Ben)
NO TRIPLES GENERATED
-----------------------------------------------------------------

If you replace each @href/@resource with @about in the second example,
the two different approaches generate the same triples:

-----------------------------------------------------------------
<div about="#me" rel="foaf:knows">
   <span about="#ivan">
   <span about="#shane">
</div>
-------- Approach A triples (Mark)
<#me> foaf:knows <#ivan> .
<#me> foaf:knows <#shane> .
-------- Approach B triples (Ben)
<#me> foaf:knows <#ivan> .
<#me> foaf:knows <#shane> .
-----------------------------------------------------------------

-- manu

-- 
Manu Sporny
President/CEO - Digital Bazaar, Inc.
blog: Intro to the Semantic Web in 6 minutes (video)
http://blog.digitalbazaar.com/2007/12/26/semantic-web-intro

Received on Wednesday, 9 January 2008 19:42:11 UTC