[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] Multiple instances of an attribute Re: [xml-dev]Towards XML 2.0
- From: Stephen Green <stephengreenubl@gmail.com>
- To: Olivier Rossel <olivier.rossel@gmail.com>
- Date: Fri, 10 Dec 2010 10:17:17 +0000
I'm also thinking how the XML Namespaces spec used notation like xmlns:a=...
so I could imagine something like <price xml2ul:amount='["100 GBP',
'200 USD']'/>
for unordered lists where xml2ul is a WG-defined reserved prefix like xmlns
Likewise for sequences or ordered lists (ol) maybe
<text xml2ol:font-family='["Arial", "Verdana"]'/>
where the order is significant.
I guess someone can think of something better...
----
Stephen D Green
On 10 December 2010 09:53, Olivier Rossel <olivier.rossel@gmail.com> wrote:
> On Fri, Dec 10, 2010 at 10:15 AM, Stephen Green
> <stephengreenubl@gmail.com> wrote:
>>> A better solution is to use xsd:list datatype :
>>> <foo value="bar spam"/>
>>> but that is not known.
>>
>> reminds me - I was thinking the WG could add an xml:json datatype
>> which might solve this (but I would hope there would be a better
>> way to allow JSON-like functionality in an attribute).
>
> Attributes cannot describe structured content.
> So we modelize structured attributes with subelements.
> Unfortunately these "structured attributes as subelements" mix with
> the subelements that represent
> the relationships between the resources.
>
> Let's consider this idea of more powerful attributes:
>
> an element could now be really separated in two parts:
> - its XML attributes describing all the attributes of the resource
> - its sub-elements that REALLY correspond to the relationship it has
> with other resources
>
> I think it would REALLY make things clearer.
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]