atom feed90 messages in org.xml.lists.xml-devRe: [xml-dev] My proposal: Implicit n...
FromSent OnAttachments
Micah DubinkoJul 31, 2009 4:06 pm 
COUTHURES AlainAug 1, 2009 3:35 am 
Amelia A LewisAug 1, 2009 7:43 am 
Kurt CagleAug 2, 2009 11:54 am 
Kurt CagleAug 2, 2009 12:30 pm 
Amelia A LewisAug 2, 2009 6:44 pm 
rjel...@allette.com.auAug 2, 2009 9:06 pm 
Micah DubinkoAug 2, 2009 9:21 pm 
Micah DubinkoAug 2, 2009 9:39 pm 
Dave PawsonAug 2, 2009 11:20 pm 
Michael LudwigAug 3, 2009 8:30 am 
Kurt CagleAug 3, 2009 10:41 am 
Pete CordellAug 3, 2009 11:56 am 
Michael KayAug 3, 2009 1:46 pm 
Kurt CagleAug 3, 2009 4:42 pm 
rjel...@allette.com.auAug 3, 2009 8:39 pm 
Pete CordellAug 4, 2009 12:36 am 
Tim BrayAug 4, 2009 9:44 am 
Micah DubinkoAug 4, 2009 11:17 am 
Micah DubinkoAug 4, 2009 10:54 pm 
Liam QuinAug 4, 2009 11:28 pm 
Dave PawsonAug 5, 2009 12:45 am 
Pete CordellAug 5, 2009 3:17 am 
Tim BrayAug 5, 2009 12:53 pm 
Liam QuinAug 5, 2009 1:46 pm 
Michael KayAug 5, 2009 4:44 pm 
'Liam Quin'Aug 5, 2009 4:50 pm 
Pete CordellAug 6, 2009 12:23 am 
Pete CordellAug 6, 2009 12:35 am 
rjel...@allette.com.auAug 6, 2009 12:57 am 
Michael LudwigAug 6, 2009 1:37 am 
Kurt CagleAug 6, 2009 1:47 am 
rjel...@allette.com.auAug 6, 2009 1:50 am 
Michael KayAug 6, 2009 2:10 am 
Michael KayAug 6, 2009 2:21 am 
Michael KayAug 6, 2009 2:25 am 
Pete CordellAug 6, 2009 2:38 am 
Pete CordellAug 6, 2009 2:45 am 
rjel...@allette.com.auAug 6, 2009 3:08 am 
Pete CordellAug 6, 2009 3:30 am 
Michael KayAug 6, 2009 3:33 am 
Simon St.LaurentAug 6, 2009 5:57 am 
Dave PawsonAug 6, 2009 7:16 am 
Michael KayAug 6, 2009 7:32 am 
rjel...@allette.com.auAug 6, 2009 7:41 am 
Richard SalzAug 6, 2009 7:46 am 
Liam QuinAug 6, 2009 8:03 am 
Liam QuinAug 6, 2009 8:10 am 
Michael LudwigAug 6, 2009 8:10 am 
Pete CordellAug 6, 2009 9:37 am 
Dave PawsonAug 6, 2009 9:47 am 
Liam QuinAug 6, 2009 9:51 am 
Dave PawsonAug 6, 2009 9:53 am 
Dave PawsonAug 6, 2009 9:54 am 
Liam QuinAug 6, 2009 10:17 am 
Kurt CagleAug 6, 2009 10:19 am 
Richard SalzAug 6, 2009 10:25 am 
Michael LudwigAug 6, 2009 10:32 am 
Kurt CagleAug 6, 2009 10:38 am 
Richard SalzAug 6, 2009 10:41 am 
Pete CordellAug 6, 2009 10:42 am 
Dave PawsonAug 6, 2009 10:47 am 
Liam QuinAug 6, 2009 11:05 am 
Pete CordellAug 6, 2009 11:49 am 
John L. ClarkAug 6, 2009 12:32 pm 
Simon St.LaurentAug 6, 2009 1:06 pm 
Michael LudwigAug 6, 2009 1:13 pm 
Michael LudwigAug 6, 2009 1:16 pm 
Michael LudwigAug 6, 2009 1:39 pm 
Liam QuinAug 6, 2009 2:43 pm 
Michael LudwigAug 6, 2009 3:11 pm 
Michael KayAug 6, 2009 3:32 pm 
rjel...@allette.com.auAug 6, 2009 8:21 pm 
rjel...@allette.com.auAug 6, 2009 8:32 pm 
Michael KayAug 7, 2009 1:10 am 
michael odling-smeeAug 7, 2009 1:28 am 
Michael KayAug 7, 2009 1:33 am 
michael odling-smeeAug 7, 2009 2:24 am 
Michael LudwigAug 7, 2009 3:00 am 
Dave PawsonAug 7, 2009 8:50 am 
Liam QuinAug 7, 2009 9:08 am 
Micah DubinkoAug 7, 2009 5:03 pm 
Micah DubinkoAug 7, 2009 5:05 pm 
Robert KobergAug 7, 2009 5:08 pm 
Dave PawsonAug 12, 2009 12:34 am 
Dave PawsonAug 13, 2009 12:35 am 
Henri SivonenAug 13, 2009 11:47 am 
Micah DubinkoAug 23, 2009 3:05 pm 
David CarverAug 23, 2009 4:21 pm 
Henri SivonenAug 24, 2009 4:03 am 
Subject:Re: [xml-dev] My proposal: Implicit namespaces
From:Liam Quin (li@w3.org)
Date:Aug 6, 2009 2:43:10 pm
List:org.xml.lists.xml-dev

On Thu, Aug 06, 2009 at 10:39:38PM +0200, Michael Ludwig wrote:

Liam Quin schrieb am 06.08.2009 um 11:11:09 (-0400):

You only need to list those elements that can occur embedded in another vocabulary, plus the top-level element. For example, a list item might not make sense without a containing list.

But then again, it might:

<xsl:template match="Liste"> <list><xsl:apply-templates select="Artikel"/></list> </xsl:apply-templates>

Yes, XSLT is a really good example of richly mixed namespaces. The best nswer I have there is probably that I'm not proposing to remove the current namespace syntax!

This particular example doesn't matter much, but with XSLT used to generate XML, it is questionable to preclude any element from appearing embedded in another vocabulary.

I don't mean to preclude it.

So, a docbook list would automatically introduce the docbook namespace for all the elements it contained (until you got down to ones that implied some other namespace, such as "svg" perhaps).

Voil? the concept of scope reintroduced, isn't it? It's just that now the current namespace is not signalled by a prefix attached to a declaration, but by the last namespace-scope-setting element.

"last" here means nearest ancestor, like xml:lang and xml:base.

In streaming mode, you wouldn't know what namespace you're in unless you swim back up the river to find a namespace-scope-setting ancestor.

You have to keep track of your parents in any case. And the existing namespace mechanism works this way too.

Best,

Liam

-- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ * http://www.fromoldbooks.org/

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS to support XML implementation and development. To minimize spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ Or unsubscribe: xml-@lists.xml.org subscribe: xml-@lists.xml.org List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php