==Some ideas for global attributes (id and class).

Here is an example usage with link markup:

[[{.someclass}http://google.com|This is a link with a class attribute "someclass"]]

[[{#someid}http://google.com|This is a link with an id]]

[[{#someid.someclass}http://google.com|This is a link with a class and id!]]

The above could be applied to any inline creole (links, bold, italics, etc.). Block markup becomes more complicated: 


|{.someclass} Does this class apply to the table, row, or cell | There doesn't seem to be an easy way |

Paragraphs, on the other hand, are pretty straight forward:

{.indent}Here is my paragraph with class="indent"! 


These ideas come from http://textism.com/tools/textile (although not verbatim)

-- [[StephenDay]], 2008-Sept-15

For links, I have proposed at [Talk.Link Extensibility Proposal] to reserve the first positional for specification of an xml:id.
[[.xml_id: rel_path | rev_path | title_path :: 
   URL | label +style=s1:v1;s2:v2 (comment)]]
Multiple classes for an element must be specifiable of course, suggesting we aim for a general mechanism in the process. Thus I propose to precede the names of XHTML attributes with the plus sign. The four positionals being proposed for a link (id, rel_path, rev_path, and title_path) map to XHTML attributes and could also/instead be spec'd using +id, +rel, +rev & +title. However given my intent to minimize author use of this attributes mechanism I think it's better for annotation to have a consistent model that's been based substantially on the double-colon. 

-- [[JohnMcClure]]