This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9011 - There are discussions of alternate extensibility mechanisms, covered in [issue-41], which might allow other ways of integrating RDFa.
Summary: There are discussions of alternate extensibility mechanisms, covered in [issu...
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML+RDFa (editor: Manu Sporny) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Manu Sporny
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 05:08 UTC by Manu Sporny
Modified: 2011-08-04 05:06 UTC (History)
5 users (show)

See Also:

Attachments

Description Manu Sporny 2010-02-16 05:08:42 UTC 
There are currently discussions of alternate extensibility mechanisms, covered in [issue-41], which might allow other ways of integrating RDFa into HTML5 without having to specify an extension to HTML5, as the current document does. For example, if XML namespaces were supported in HTML5, it would allow one to specify RDFa without having to affect the main HTML5 specification.
Comment 1 Manu Sporny 2010-02-16 05:09:34 UTC 
RDFA-SPEC-SECTIONS [status-of-this-document]
Comment 2 Maciej Stachowiak 2010-02-16 09:30:41 UTC 
Isn't this just covered by ISSUE-41? Suggest resolving this and marking as TrackerIssue in favor of ISSUE-41.
Comment 3 Manu Sporny 2010-02-16 14:27:39 UTC 
This bug may be temporary. I had to add this in order for the specbugs script to annotate the status-of-this-document section with a mention of ISSUE-41. The correct fix would be to update specbugs to pull not only all of the W3C bugs associated with a component down, but all of the W3C issues down as well. The combination of bugs and issues should be used to annotate the specification.

This bug should remain active until that feature is implemented in specbugs.
Comment 4 Maciej Stachowiak 2010-02-16 23:05:47 UTC 
(In reply to comment #3)
> This bug may be temporary. I had to add this in order for the specbugs script
> to annotate the status-of-this-document section with a mention of ISSUE-41. The
> correct fix would be to update specbugs to pull not only all of the W3C bugs
> associated with a component down, but all of the W3C issues down as well. The
> combination of bugs and issues should be used to annotate the specification.
> 
> This bug should remain active until that feature is implemented in specbugs.
> 

There's gotta be some issue annotation code somewhere, since HTML5 itself is annotated with ISSUE-41.
Comment 5 Manu Sporny 2010-02-17 00:55:40 UTC 
(In reply to comment #4)
> There's gotta be some issue annotation code somewhere, since HTML5 itself is
> annotated with ISSUE-41.

There is... it's somewhere in Anolis, I need to talk with Geoffrey about it at some point to see if I can re-use it easily. The technical part is fairly trivial... it's finding the 1-2 hours in my day to integrate/write the code, that's the difficult part :)
Comment 6 Manu Sporny 2010-03-24 02:59:55 UTC 
This bug was temporary and is covered by ISSUE-41. There is no need for editor feedback.
Comment 7 Michael[tm] Smith 2011-08-04 05:06:23 UTC 
mass-move component to LC1