W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > July 2007

Re: [RDFa] Telecon Agenda, Thursday 12 July, 1500 UTC, 1100 Boston

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Thu, 12 Jul 2007 15:02:02 +0100
Message-ID: <640dd5060707120702x2433b423w4b21579e5f66b6a9@mail.gmail.com>
To: "Ben Adida" <ben@adida.net>
Cc: RDFa <public-rdf-in-xhtml-tf@w3.org>, "SWD WG" <public-swd-wg@w3.org>

Hi Ben,

Many apologies, but I will definitely be late for the call, and might
not be able to make it all. I have to attend something that is
supposed to go from 3pm to 4pm my time, so if it finishes bang on
time, I should be able to get back home for about 4.10-4.15pm, and so
only miss the first part of the call. But the nature of the event is
such that it could drag on, so if I don't make it, please accept my
apologies.

I don't want to hold up any discussions, so I thought I'd throw a few
comments on the agenda items here.


> 2) @href/@resource everywhere
> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0059

I might as well say what would be the ideal solution from my point of
view; I would like to see:

  * @href restricted to its HTML/XHTML positions;
  * @resource allowed everywhere;
  * the UA is not obliged to make @resource navigable in any way, although it
    certainly could, based on knowledge gleaned from triples;
  * no difference in terms of triples between the two attributes;
  * @href does NOT set the subject for nested statements.

In the main I'm arguing for a way of referring to an object that is a
resource and is non-navigable. For example:

  <div attribute-that-dare-not-speak-its-name="am:wishlist">
    <span rel="am:wish resource="urn:isbn:1234567">A book</span>
  </div>


> 3) @class/@role/@new_attribute
> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0035

As you know I'm rooting for @new_attribute.

If it gets accepted, and you get to the point where you discuss the
name of it, then my vote is for Niklas's 'instanceof'. I did like @isa
but I think it's too short, and wouldn't be noticed when making a
quick read through a document; @instanceof stands out quite nicely.


> 4) @rel everywhere
> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0057


This is tricky.

I've not gone into detail on this, but I don't like @rel everywhere,
because it's an HTML/XHTML attribute, and not an RDFa one. If we don't
have @href everywhere then I think we don't need this, and I would
suggest that we just use @property for @resource as well as for
@content. This keeps the amount of work required to implement DTDs and
schemas for RDFa really small.

However...I don't regard this as a show-stopper, so if most votes are
for @rel/@rev everywhere then that's fine be me, too.


> 5) @src
> http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jul/0041

I think this should be the subject of an 'instanceof' (or whatever
attribute is used). However, if a @rel is present then @src should
also be the object of a triple.

I think the confusion that has arisen is only to do with the
explanations, and I think if we can explain this odd 'striped' feature
we we should be ok.

Regards,

Mark

-- 
  Mark Birbeck, formsPlayer

  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Thursday, 12 July 2007 14:02:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:08 GMT