On Tue, Apr 5, 2011 at 2:36 PM, Galen Charlton <gmcha...@gmail.com> wrote: > Hi, > > On Tue, Apr 5, 2011 at 2:26 PM, Mike Rylander <mrylan...@gmail.com> wrote: >> Evergreen (http://evergreen-ils.org/) uses unAPI extensively, so we >> wouldn't want to see the abbr-title pattern removed, but I don't see >> any reason to avoid aligning the spec with the value-class pattern a >> bit in terms of supported implementation. >> >> Note, though, that the value for unAPI is a tag: URI, not human-usable >> data, so it may be less applicable to unAPI than, say, hCard. My >> $0.02 ... > > It looks like that the value-title variant [1] of the value-class > pattern would give us a way to avoid the accessibility problem while > not inflicting opaque strings meant for machine processing on humans. > > [1] > http://microformats.org/wiki/value-class-pattern#Parsing_value_from_a_title_attribute >
But, isn't that exactly what unAPI specifies today in an <abbr>? -- Mike Rylander | VP, Research and Design | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@esilibrary.com | web: http://www.esilibrary.com -- You received this message because you are subscribed to the Google Groups "gcs-pcs-list" group. To post to this group, send email to gcs-pcs-list@googlegroups.com. To unsubscribe from this group, send email to gcs-pcs-list+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/gcs-pcs-list?hl=en.
