W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2006

RE: using <ns> to specify namespaces

From: Yves Savourel <yves@opentag.com>
Date: Thu, 2 Feb 2006 06:08:18 -0700
To: "'Felix Sasaki'" <fsasaki@w3.org>, "'Sebastian Rahtz'" <Sebastian.Rahtz@oucs.ox.ac.uk>
Cc: <public-i18n-its@w3.org>
Message-ID: <001601c627f9$bca1fb30$0300a8c0@Breizh>

OK, I'm convinced <ns> is the way to go then :)

-----Original Message-----
From: Felix Sasaki [mailto:fsasaki@w3.org] 
Sent: Thursday, February 02, 2006 5:40 AM
To: Sebastian Rahtz
Cc: Yves Savourel; public-i18n-its@w3.org
Subject: Re: using <ns> to specify namespaces

On Thu, 02 Feb 2006 18:27:20 +0900, Sebastian Rahtz <Sebastian.Rahtz@oucs.ox.ac.uk> wrote:

> Felix Sasaki wrote:
>>  Talking from the XSLT / XQuery perspective: Both Sebastians and my  
>> implementations need to copy the string values of the selector  
>> attributes into generated XSLT stylesheet / XQuery files. So we need an  
>> extra step anyway to generate zero or more xmlns elements in these  
>> files, so that the XSLT / XQuery processor understands these values as  
>> "namespace using" XPath expressions.
>>  This task seems to me easier to do with the <its:ns> element, rather  
>> than analyzing xmlns attributes at "its:documentRules". Although the  
>> task would be not impossible for XQuery, I think. Sebastian, what do  
>> you think about XSLT?
> as it stands in XSLT 1.0, I don't see any way to get the necessary
> information across from the (otherwise reasonable) notation Yves
> proposes. Can you see a way, Felix?
Ah, sorry, I just thought of XSLT 2.0 ... With XSLT 1.0, you are really  
lost, I think.

Received on Thursday, 2 February 2006 13:08:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC