W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > April 2011

RDFa Core last call comments - "have not yet caught up"

From: Jonathan Rees <jar@creativecommons.org>
Date: Thu, 21 Apr 2011 12:39:26 -0400
Message-ID: <BANLkTiknnx+N4s908hGJEk=6qHc+EvWZSw@mail.gmail.com>
To: public-rdfa-wg@w3.org

The Note in section 2 says:

  However, the media type registrations that govern the meaning of
  fragment identifiers (see section 3.5 of the URI specification
  [RFC3986], [RFC3023], and [RFC2854]) have not yet caught up with this

You added this note in response to the TAG's request that you explain
that there is an issue, even if no solution is offered.  Thanks for
doing this.

However, "not yet caught up" sounds too much like a promise.  It
implies that you believe the specs *will* catch up with RDFa.  You
would need some justification for this, such as someone having
volunteered to changing the registrations or RFC 3986. I don't think
you have such justification.

You might just stick with a more factual statement such as

  Unfortunately, this practice is not at present covered by
  the media type registrations that govern the meaning of
  fragment identifiers (see section 3.5 of the URI specification
  [RFC3986], [RFC3023], and [RFC2854]).

This may be sufficient.  "At present" is a bit of a weasel hinting at
possible change but not predicting it.  This wording may leave the
reader wondering what to make of the contradiction - does it mean they
shouldn't use fragids after all because they're out of spec?  I've
been trying to come up with a followon sentence that is reassuring,
without success so far.  You could say for example that you believe
that there is no serious incompatibility and that you *hope* that the
specs will be made consistent in the future.  Or you might say that
you think the specs are wrong and should be ignored, but that
would encourage an anti-specification attitude that could be used
against RDFa itself (and much of what W3C does).

I'm sorry I can't be more helpful right now.  Perhaps the reference to
webarch in the next sentence will be adequate (in some
nonspecific way) and we don't need an additional
sentence saying that these fragids are OK.

We've been talking about media type registrations and fragids a
fair amount in the TAG. This particular topic was taken up at
the 24 March 2011 TAG meeting:
See also

It's a rather painful part of the architecture, and no one likes it,
but it's not obvious how to fix it.

This message has not been vetted with the TAG, so should be taken
as individual communication, but I've done my best to represent what
others in the TAG have said on the subject.

Received on Thursday, 21 April 2011 16:39:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:51 UTC