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
JohnMcClure said "... Personally I favor the solution that blank_line=paragraph_begin_OR_end... and I favor a distinct paragraph_start character pattern that allows the specification of an id for the generated <p> plus any other XHTML attribute(s)"
I like the idea of an optional distinct paragraph pattern also, mainly because it would ease implementation of XHTML attribute addition. The idea does clash somewhat with the current suggestion for indented paragraphs (see Creole Additions) which I think wouldn't be a great addition anyway.
I think, perhaps by accident, a nice pattern that has arisen in Creole is the use of single characters at the beginning of a line to signify block markup (lists and tables), and double characters anywhere to signify inline markup. These types of patterns are good for both implementers and users.
-- StephenDay 2008-Sept-19