I still disagree if we are developing both a human readable and machine
readable form. Don't make the human learn n forms - machines are more able
to switch delimiters on the fly than humans.
In this thought exercise ... I need to free myself from my day to day life
of making Xml do real work for end users - that act having some fundamental
problems in itself.
In the new core "ML" perhaps we could:
- go for even less features
- remove the idea of DTDs and DocType all together.
- reflect on XML Schema, RelaxNg and why DITA went with the class attribute
for its typing.
- make the namespaces part of core.
Of course, all these things could and are being done within the existing
Xml. I think we need to acknowledge that Xml as concieved is kick ass. But
core Xml may perhaps still be "bigger" than it needs to be.
-----Original Message-----
From: Peter Hunsberger [mailto:]
Sent: Thursday, July 09, 2009 3:04 PM
To: Jim Tivy
Cc: Pete Cordell; XML Developers List
Subject: Re: [xml-dev] XHTML 2 Working Group won't be renewed?
On Thu, Jul 9, 2009 at 4:25 PM, Jim Tivy<> wrote:
> Not a good idea for an open interoperatable data format.
If part of the spec is a way to figure out what delimiters are being
used in any given instance, then I'd argue the exact opposite. I
believe this was the case for SGML (anyone?)
>
> -----Original Message-----
> From: Peter Hunsberger [mailto:]
> Sent: Thursday, July 09, 2009 7:31 AM
> To: Pete Cordell
> Cc: XML Developers List
> Subject: Re: [xml-dev] XHTML 2 Working Group won't be renewed?
>
>> From: "Michael Kay"
>>>
>>> One problem is that the more universal you want to make it, the more
>>> contexts it has to be unambiguous in: for example XQuery has problems
> with
>>> {uri}local because it already uses "{" extensively.
>>
>> If you get really desperate you could do something Perl-esque where you
>> choose your delimiters.
>
> Didn't SGML allow you to choose your own delimiters (in general)?
>
> --
> Peter Hunsberger
>
--
Peter Hunsberger
