Well... so it seems that the model is a bit more complex than I thought:-( Indeed, this 'shift' stuff comes into the picture, too. Sigh. Only one remarks below. Other than that, I guess back to square one: the group has to vote... (and implementers like me have to execute:-) Ivan > >> That means that, for example >> >> <div resource="#a" rel="a:b" href="#c"/> >> >> yields >> >> <#a> a:b <#c>. > > No. In this case, applying the grid above, you would get: > > _:a a:b <#a> . > > I.e., both @resource and @href shift to the right in the presence of > @rel, and then according to our list, @resource takes priority. > And here I am lost. Even in your model, isn't the right triple: <INHERITEDSUBJECT> a:b <#a>. where <INHERITEDSUBJECT> is either <> (provided @about="" is implicitly on <body> or <html>) or some inherited resource? Where does this sudden blank node come from? [snip] -- 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
Received on Tuesday, 22 January 2008 15:13:46 UTC