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:John L. Clark (jl@po.cwru.edu)
Date:Aug 6, 2009 12:32:54 pm
List:org.xml.lists.xml-dev

On Thu, Aug 6, 2009 at 11:11 AM, Liam Quin <li@w3.org> wrote:

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. 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).

I think it would be useful, in other contexts as well, to have a list of elements from a particular vocabulary that the vocabulary's designer baptizes as making sense to embed within another vocabulary. (Specifically, such an element E in vocabulary N could be called a boundary element, and a document D would be boundary-valid iff for every element E', if the parent of E' is in a different vocabulary, then E' is a boundary element.) This provides a sort of light weight validation for compound documents. It also might be semantically interesting to see how elements fall into the two different coarse categories.

Of course, this assumes that elements have consistent local semantics wherever they're found in a vocabulary, but this is not necessarily the case. For example, you could have a 'warning' element that has different weight in different contexts. Perhaps such context-sensitive elements are always non-boundary elements, though.

Take care,

John L. Clark

_______________________________________________________________________

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