Summary of @href/@resource completing triples issue

This is repeating what everybody else has more or less agreed upon, but
it helps to have a succinct definition of what we're talking about... it
seems that the @href/@resource triple completion issue boils down to this:

This works for both approaches:

-----------------------------------------------------------------
<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):

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

If you replace @href with @resource above, you get the same triples as
listed above.

If you replace the @href's with @abouts 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> .
-----------------------------------------------------------------

Is that a succinct definition of the @href/@resource completing triples
issue?

-- 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 17:21:23 UTC