include pattern : including table data

Hello all.

I'm new to the mailinglist; I'm a student and freelance
designer/ 
developer.

I have a question about the include pattern:
anchor elements are not allowed in all elements: ie using an
anchor  
element to include extra table data (rows) will result in
invalid  
xhtml. ie. <table><a class="include"
href="#row_data"></a></table> is  
not valid.

I suppose we could work around this by using the title
attribute  
along with the class="include" on almost all
elements.
ie. <table><tr class="include"
title="#row_data"><td/></tr></ta
ble>  
is valid.

The title attribute set too "#an_id", however does
not indicate a  
reference to an other element, which is a problem. Any
thoughts/  
suggestions ?

Regards
-Alwin
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

From: "Alwin Blok" <alwinblokgmail.com>
> I have a question about the include pattern:
> anchor elements are not allowed in all elements: ie
using an anchor 
> element to include extra table data (rows) will result
in invalid  xhtml. 
> ie. <table><a class="include"
href="#row_data"></a></table> is 
not valid.
>
> I suppose we could work around this by using the title
attribute  along 
> with the class="include" on almost all
elements.
> ie. <table><tr class="include"
title="#row_data"><td/></tr></ta
ble>  is 
> valid.
>
> The title attribute set too "#an_id", however
does not indicate a 
> reference to an other element, which is a problem. Any
thoughts/ 
> suggestions ?

The include pattern is not going to change how information
is presented on 
the screen.
The purpose of the include pattern is to allow you to reuse
microformat 
information that's already on the page. The only effect that
the include 
pattern has is on parsers looking through the page for
microformat 
information.

For example, if you have information that an hcard could
use, then later on 
in the page you have address details for them, their first
hcard information 
can be reused (when microformat info is extracted) without
having to 
redisplay that info on the page again.

<div class="vcard"><span
class="fn" id="myname">Paul
Wilkins</span></div>
... other stuff ...
<div class"vcard">The place where <a
href="#myname"
class="include">I</a> 
live is <span class="adr"><span
class="street-address">123 Evergreen 
Terrace</span>.</div>

If you can provide an example of what you're wanting to
display on the page, 
we can then help with examples of how to effectively mark it
up as a 
microformat.

-- 
Paul Wilkins 

_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

On 3/15/07, Alwin Blok <alwinblokgmail.com> wrote:
> Hello all.
>
> I'm new to the mailinglist; I'm a student and freelance
designer/
> developer.

--- hello, welcome to the list

> I suppose we could work around this by using the title
attribute
> along with the class="include" on almost all
elements.
> ie. <table><tr class="include"
title="#row_data"><td/></tr></ta
ble>
> is valid.

--- there is a better, more semantic way. Tables have
several
accessibility 'hooks' they allow for axis, header, id, and
other
attributes to create relationships between two cells.

Unfortunately, i can't seem to find any examples about this
on the
wiki, and the example pages no longer seem to exist.

I know the new microformats book does cover all of this
indepth,
hopefully we can get an example on the wiki.

Do you have a URL you could post here so we can help you
mark-it-up?

-brian

-- 
brian suda
http://suda.co.uk
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

Brian,
>> Hello all.
>>
>> I'm new to the mailinglist; I'm a student and
freelance designer/
>> developer.
>
> --- hello, welcome to the list
>
>> I suppose we could work around this by using the
title attribute
>> along with the class="include" on almost
all elements.
>> ie. <table><tr class="include"
title="#row_data"><td/></tr></ta
ble>
>> is valid.
>
> --- there is a better, more semantic way. Tables have
several
> accessibility 'hooks' they allow for axis, header, id,
and other
> attributes to create relationships between two cells.
>
> Unfortunately, i can't seem to find any examples about
this on the
> wiki, and the example pages no longer seem to exist.
>
> I know the new microformats book does cover all of this
indepth,
> hopefully we can get an example on the wiki.

I'm starting a new column at digital web very soon
"code sharp" -  
this might be a great thing to kick off with.

(for those who don't know, I'm the guy who wrote the book
Brian is  
referring to - but much better, Brian Tech Edited it)

http://microformatiqu
e.com/book

There's also a great online tool for building table based
hCalendars,

http://dmitry
.baranovskiy.com/work/csc/

very cool

john

p.s.

(out march 26)

pps

sorry for the slightly advertisey post

j


>
> Do you have a URL you could post here so we can help
you mark-it-up?
>
> -brian
>
> -- 
> brian suda
> http://suda.co.uk
> _______________________________________________
> microformats-discuss mailing list
> microformats-discussmicroformats.org
> http://microformats.org/mailman/listinfo/microforma
ts-discuss
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

Op 15-mrt-2007, om 21:34 heeft Brian Suda het volgende
geschreven:

>> I suppose we could work around this by using the
title attribute
>> along with the class="include" on almost
all elements.
>> ie. <table><tr class="include"
title="#row_data"><td/></tr></ta
ble>
>> is valid.
>
> --- there is a better, more semantic way. Tables have
several
> accessibility 'hooks' they allow for axis, header, id,
and other
> attributes to create relationships between two cells.

> Do you have a URL you could post here so we can help
you mark-it-up?
>
> -brian

Hmm, I realise now, that this is indeed, not really a
problem with  
general use of the include pattern.

Sorry for going off-topic, but let me explain my question:
I am building a templating system for skinning, and editing
data  
structures.
For this, I am using elements containing optional includes
and choice  
includes (as templates), when I noticed a resemblance with
the markup  
of the include pattern.

A simple gui for a list of records could look like this:

<table style="display:none">
<tr id="#row_data"><td>First
Name</td><td>Last Name</td></tr>
<a class="optional rule"
title="#row_data">Add another
record..</a>
</table>
<table><a class="optional rule"
title="#row_data">Add record..</a></ 
table>

Clicking "Add record" clones the referred item,
binds it to backend  
data and replaces the anchor.

I think this is related to microformats, as it actually
describes a  
grammar of a (compound) microformat.
I need to specify these grammars, and I am trying to find a
format  
for the specifications.

Regards,
-Alwin
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss