Re: [RDFa] non-binding resolutions

Great. Thanks to you guys for moving forward.

Two additions to get the rules well defined:

- the subject of @property remains unchanged and looks for the closes
RDF identity up the XML tree

- one small thing that you seem to forget: the @data attribute on the
<object>. Do we remain silent on that, or do we include them on the same
level and functionality as @src? I would propose to equate it with @src

I believe that the rules I outlined for containers and collections in:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0174.html

remain valid, too, ie, that long term issue may be considered as solved
as well.

The only open issue I still see is my proposal on "_:". As I say in

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0174.html

I do not see any other way to create something like

[ a rdf:Seq;
  rdf:_1 [ p:q "bla2". ];
  rdf:_2 [ p:q "bla2". ].
].


I think it would be *very* important to start with the RDFa syntax doc
that would then hopefully lead to new implementations. All the
implementations out there (like the trplr one that I testes a few days
ago) rely on the old version.

The coming two weeks are quite slow for me (I will then travel again).
If you need help on editing, you know where to find me...:-)

Ivan

Ben Adida wrote:
> 
> Hi all,
> 
> Mark, Ralph and I had a very productive chat today where we agreed on
> some non-binding resolutions. Our next steps are to
> 
> A) update the test cases
> B) update the implementations
> C) update the RDFa syntax doc (yes, we can start on this!)
> 
> 
> Why non-binding? Because we were only 3 on the call and the resolutions
> will be best achieved by *trying* them out in actual implementations,
> rather than theorizing on them endlessly.
> 
> So, here they are, your non-binding resolutions.
> 
> 1) @instanceof is the attribute name for rdf:type
> 
> 2) @id does *not* play a role in RDFa triple generation.
> 
> 3) @rel, @rev, and @instanceof cause chaining (aka striping), whether or
> not there is @href/@resource on the element.
> 
> 
> (2) and (3) cause changes to the rules I laid out a few days ago, so I
> will restate the rules completely now.
> 
> 
> - @rel (conversely @rev) creates triples with the given predicate. The
> object of @rel (conversely the subject of @rev) is the "RDF identity" of
> the current element, and the subject of contained elements is implicitly
> set to that same "RDF identity."
> 
> - @instanceof applies to the "RDF identity" of the current element, and
> sets of the subject of contained elements to this same "RDF identity."
> 
> - the RDF identity of an HTML element is, in order of precedence
>  - @resource
>  - @href
>  - @src if it's an IMG
>  - @about
>  - a new bnode
> 
> (NOTE how @id is not present in this list anymore.)
> 
> Thus, here are some examples:
> 
> 
> 
> <div about="#me" rel="foaf:knows" instanceof="foaf:Person">
>   <span property="foaf:name">Mark</span>
> </div>
> 
> <#me> foaf:knows [ rdf:type foaf:Person ; foaf:name "Mark" ] .
> 
> 
> 
> 
> <div about="#me" rel="foaf:knows" instanceof="foaf:Person"
>      href="http://example.org/~mark">
>   <span property="foaf:name">Mark</span>
> </div>
> 
> <#me> foaf:knows <http://example.org/~mark> .
> <http://example.org/~mark>
>   rdf:type foaf:Person ;
>   foaf:name "Mark" .
> 
> 
> 
> 
> <div about="#me" instanceof="foaf:Person">
>   <span property="foaf:name">Ben</span>
> </div>
> 
> <#me> rdf:type foaf:Person .
>       foaf:name "Ben" .
> 
> 
> 
> 
> <div instanceof="foaf:Person">
>   <span property="foaf:name">Ben</span>
> </div>
> 
> _:div0 rdf:type foaf:Person ;
>        foaf:name "Ben" .
> 
> 
> 
> <img about="#me" rel="foaf:image" src="ben.jpg" />
> 
> <#me> foaf:image <ben.jpg> .
> 
> 
> 
> 
> And in any of these cases, adding @id doesn't change a thing about the
> RDFa triples generated.
> 
> -Ben
> 

-- 

Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf