Are there any projects that are already using RDF or Microdata to
express TEI semantics in HTML, or is this something else that many
people are talking about but no one has done anything with yet?
Dot
On Sat, Jun 11, 2011 at 12:30 PM, Brett Zamir <[log in to unmask]> wrote:
> On 6/11/2011 10:35 PM, Sebastian Rahtz wrote:
>>
>> On 10 Jun 2011, at 05:41, Brett Zamir wrote:
>>>
>>> In summary, there is really no information that will be lost in a
>>> TEI-in-HTML5 serialization.
>>
>> Sorry to come late into this very interesting subject; I for one fully
>> intend to
>> experiment with the microdata route when I have a minute (alongside a
>> related
>> TEI to RDF conversion).
>
> Great... Let us know if you would like any collaboration. It would seem to
> me that it may productive for our group interested in this to perhaps do a
> comprehensive gradual review of the stylesheets (at a level understandable
> to non-technical users) as well as the relevant portions of the TEI and HTML
> specifications to come up with a semantic algorithm for reliably converting
> TEI to and from HTML, without interfering with a project's stylistic freedom
> in styling such documents.
>
> It would seem to me that CSS and JavaScript might be project-specific, but
> formalizing the means of converting to HTML, using the stylesheets as a base
> would be very worthwhile, as well as informative in itself for documenting
> and collectively reviewing the significance of the choices made in the
> stylesheets, distinguishing potentially normative transformations from any
> optional non-normative ones, and offering any suggestions for improvement.
>
> Are you open to this, and do others think this would be a suitable endeavor
> for us?
>
>> But I have to remind you that my HTML stylesheets at least
>> (and I imagine other peoples too) destroy a fair amount of TEI info along
>> the way,
>> and its not obvious how the microdata can get it back.
>>
>> A simple example is<note>, which one typically puts in a different
>> construct
>> in HTML from what is in the TEI.<app> isn another.
>
> Applying CSS display:none seems a logical choice to me when the application
> does not provide its own means of display (such as adding mouseovers on the
> parent to reveal the text)...
>
> To take the first example of <note/> (at
> http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-note.html ) , I
> think it could be transformed into this.
>
> Assuming no attribute is available or can be made available in TEI itself to
> make the important assertion about whether the note was in the original text
> or not (I wouldn't think even @resp indicates this) and thus likely to be
> displayable by default, variables might be used to determine whether to hide
> such notes by default or not. My preference, however, would be to ensure
> there would be no need of such variables, allowing attributes and default
> behaviors to be relied upon to control rendering.
>
> <!-- One might also use a 'div' instead of an aside -->
> <aside hidden="hidden" itemprop="note"> <!-- HTML5 would make this hidden,
> but it would need CSS display:none for older browsers -->
> <meta itemprop="place" content="bottom"/>
> <meta itemprop="type" content="gloss"/>
> <link itemprop="resp" href="#MDMH"/>
> <dfn xml:lang="de" lang="de" itemprop="term">Malerisch</dfn>. This word has,
> in the German, two
> distinct meanings, one objective, a quality residing in the object,
> the other subjective, a mode of apprehension and creation. To avoid
> confusion, they have been distinguished in English as
> <span itemprop="mentioned">picturesque</span> and
> <span itemprop="mentioned">painterly</span> respectively.
> </aside>
>
> TEI may not be committal about whether certain such elements are understood
> to be rendering or not, whether such as the above ought to programmatically
> display the contents of the <respStmt/> referrred to by "#MDMH" (with the
> respStmt perhaps also represented as an initially hidden HTML element), etc.
> But an individual website could use CSS to style according to their tastes,
> even using CSS with the :hover pseudo-class to turn it into an interactively
> exposable footnote, or using JavaScript to add some other behavior.
>
> My impression is that it should be possible to find a logical and canonical
> transformation in most cases which was both universally agreeable
> structurally and flexible enough to be styleable according to different
> project's needs, though no doubt many could be challenging to settle upon.
>
> Best wishes,
> Brett
>
--
*~*~*~*~*~*~*~*~*~*~*
Dot Porter (MA, MSLS)
Digital Medievalist, Digital Librarian
Email: [log in to unmask]
*~*~*~*~*~*~*~*~*~*~*