If DC elements disallow mixed content, then one can't include, eg,
the directionality markup often needed for BiDi languages. The
same, of course, applies to other important markup such as an
indication of a change of (human) language within an element.
The Web I18N community has had an ongoing tussle over this with
the XML Schema community and with the RDF community.
Misha Wolf
Standards Manager
Product and Platform Architecture Group
Reuters Ltd.
-----Original Message-----
From: General DCMI discussion list [mailto:[log in to unmask]] On
Behalf Of Liddy Nevile
Sent: 04 June 2004 01:36
To: [log in to unmask]
Subject: Re: How to contain semantic formatting in DC title
My understanding is that it is OK to use different languages, that is
what DC 'likes' but that the problem at hand is to do with using
non-spoken languages. I guess it is XML language? or MathML language?
Maybe that is not a problem but I'd like to know.
If the original idea, with a superscript 2 is followed, the result will
be something that only those with the right browser and capacity to see
it will be able to use. MathML is critical to accessibility for many
people, contexts and purposes.
Maybe all we need to do is have a way of saying that the language is
XML/MathML and pointing to it???
Liddy
On Friday, June 4, 2004, at 10:13 AM, Howard Batchelor wrote:
> I have been happily using Arabic, Persian, and Turkish as values in DC
> Title, Creator, etc. with no sense that this might be a problem
> provided these are stored in a 32-bit table. I would be glad to know
> if anyone thinks otherwise.
>
-----------------------------------------------------------------
Visit our Internet site at http://www.reuters.com
Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.
|