Re: ITS as a microformat (proposal)

2009/7/3 Jirka Kosek <jirka@kosek.cz>

> Felix Sasaki wrote:
> > Interesting approach ... esp. since validation is a kind of lax. What
> would
> > you or others think of the following approach: define a grammar (below in
> > ABNF form) to parse the ITS local data categories, e.g. like this:
> >
> > ITSMF = itsprefix [translate] [terminology] [localizationNote]
> > [directionality]
> > itsprefix = "its"
> > translate = "-translate-" ("yes" | "no")
> > terminology = "-term" ["-termInfoRef:" IRI] ; IRI production from RFC
> 3987
> > localizationNote = ...
> > terminology = ...
> >
> > That is, have the translate, terminology, localization note and
> > directionality data categories all "packed" in a class attribute.
>
> Seems little bit like a markup abuse, but microformats are all about
> abuse, after all ;-)


Exactly :)



>
>
> But I don't think that IRIs should encoded inside class name, e.g.
> content of termInfoRef. This way IRI is not exposed as some kind of link
> in HTML representation and user agents can't directly act on it.



Understand, but do we want user agents to act on ITS information, or to have
that information just for further processing by e.g. localization tools. Not
sure ...



> But for
> other categories your approach might work well.


Thanks, I will continue work on this.

Felix


>
>
>                                Jirka
>
> --
> ------------------------------------------------------------------
>  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
> ------------------------------------------------------------------
>       Professional XML consulting and training services
>  DocBook customization, custom XSLT/XSL-FO document processing
> ------------------------------------------------------------------
>  OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
> ------------------------------------------------------------------
>
>