[tei-council] ITS at W3C

[Lou Burnard]

Well, this does seem to overlap quite a lot... and it would be nice if 
we could persuade W3C to adopt ODD oor something like it...  I met Felix 
at Extreme last year and formed a high opinion of him, so I think 
working with him might be well worthwhile.

If we were to set up with W3C something like the existing liaison with 
ISO, would we be able to say that the TEI runs the internet?

Seriously, tho. Yes, I agree that this would be worth pursuing, and I am 
willing to help pursue it, or persuade Sebastian to, assuming either of 
us can find the time.

Lou


Christian Wittern wrote:

>Council members,
>
>As it happens, I had a long conversation with Felix Sasaki yesterday,
>who joined the W3C host in Japan this April and works there on i18n
>issues.  He mentioned work going on at the W3C at the ITS
>(Internationalization Tag Set,
>cf. http://www.w3.org/International/its/) group, which seems to have
>some overlap with our problem here. The mission statement for the
>group is as follows:
><quote>
>Mission: Develop a set of elements and attributes that can be used
>with new DTDs/Schemas to support the internationalization and
>localization of documents; and provide best practice techniques for
>developers of DTDs/Schemas that show how to enable
>internationalization of their documents.
></quote>
>
>They are not ready and it might be overkill, but it seems to me that
>we should monitor this.
>
>He asked also if somebody from the TEI would be interested to join
>this group; we also discussed if the TEI could/should consider to
>enter into some formal relation with the W3C.  I would be interested
>in opinions from the Council members on the desirability of such a
>development.
>
>Sebastian Rahtz <sebastian.rahtz at computing-services.oxford.ac.uk> writes:
>
>  
>
>>Christian Wittern wrote:
>>
>>    
>>
>>>What would be the advantage of pulling this into the main P5 source?
>>>I see only added maintainance cost with no real benefit.  You could as
>>>easily pull them out and merge them into the tree on runtime.
>>> 
>>>
>>>      
>>>
>>perhaps its matter of semantics; if the main ODD processing
>>software expects to find the various language-specific <desc>s
>>in site in the main document, then it does not much matter whether
>>the merge is at runtime or at source. I just want to avoid a "normal"
>>ODD processor from having to know about the language modules.
>>
>>    
>>
>>>>dont forget attributes, and vallists, by the way
>>>>        
>>>>
>
>  
>
>>>But attributes should be covered within the elementSpec, shouldnt
>>>they.
>>>
>>>      
>>>
>>and the classSpecs.
>>    
>>
>
>  
>