sigh... rel="grddl" is squatting; it's not URI-based at all.
The worst that can happen to the head/@profile attribute in HTML5 is that it gets ignored.
rel=transformation is squatting too. ;)
As for HTML 5 (and XHTML 2), I hope you are right about the profile attribute. I wouldn't put it past people to get rid of it though. I have a funny feeling that "oh! We need it for the Semantic Web!" will be completely ignored as an argument.
I hope you are right, but we desperately need a contingency plan.
2007-06-26EDT01:56:10+00:00
#
As for HTML 5 (and XHTML 2), I hope you are right about the profile attribute. I wouldn't put it past people to get rid of it though. I have a funny feeling that "oh! We need it for the Semantic Web!" will be completely ignored as an argument.
I hope you are right, but we desperately need a contingency plan.
No, the HTML spec specifically says that values of the rel attribute can be grounded in URI space using profile URIs. So The rel="transformation" in the GRDDL spec is grounded in URI space at http://www.w3.org/2003/g/data-
vi...#transformation . So we're not specifying what _all_ uses of rel="transformation" means; only uses of rel="transformation" in documents where the author has explicitly called out GRDDL. That's not squatting; that's URI-based extensibility.
2007-06-26EDT18:41:59+00:00
#
Dan, you say: The worst that can happen to the head/@profile attribute in HTML5 is that it gets ignored.
Do you mean that, at worst, browsers will ignore it? But won't it invalidate the HTML5? My concern would be that some developers will be prevented from using GRDDL because their clients/employers require that the HTML be valid.
I would also expect W3C specifications to be consistent with each other.
Perhaps you could use @rel=grddl as a threat - if they take out @profile, they need to predefine another @rel value ;)
2007-06-27EDT10:54:23+00:00
#
Do you mean that, at worst, browsers will ignore it? But won't it invalidate the HTML5? My concern would be that some developers will be prevented from using GRDDL because their clients/employers require that the HTML be valid.
I would also expect W3C specifications to be consistent with each other.
Perhaps you could use @rel=grddl as a threat - if they take out @profile, they need to predefine another @rel value ;)
