Re: Why not XHTML+RDF? was Re: Links are links

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ Jeni Tennison <jeni@jenitennison.com> was heard to say:
| Hi Norm,
|
|> | Getting something that's easy for users to
|> | include -- in their schema, in their CSS or wherever -- will be the
|> | deciding factor.
|>
|> Maybe. A lot of folks have trouble with indirection, the
|> overwhelming majority will never write a schema,
|
| Do you think that the vast majority *will* write a DTD? This is one of

No. Fair point. Using schemas to add defaulted attributes is exactly
analogous to using DTDs for that purpose. But...I think it'll be a
long time before schema processing is as widely deployed (or commonly
performed) as DTD processing and much more centrally, I think the idea
of basing this on some sort of schema annotation stuff (rather than
defaulted attributes) is really unlikely to ever be widely deployed.

| the things that I don't understand about objections to HLink on the
| basis of too much indirection

For the record, my comment on indirection had nothing to do with
schema processing.

| Then maybe *simple* linking would be something to aim for? Like Paul
| Prescod said:
|
|> But XLink is pretty near pessimal along all axes. If links are so
|> important that they should be burned deep into the syntax then the
|> appropriate namespace is "xml" and the specification should be VERY
|> SHORT, VERY SIMPLE and VERY APPLICATION AGNOSTIC. Surely it isn't

Simpler than my earlier example that *already works in my browser*?

  <phrase xlink:href="http://www.example.com/" xlink:type="simple">...</phrase>

Yeah, the xlink:type attribute is a little unfortunate, but it could
probably be made unnecessary be specifying that its default was
'simple' and its presence was implied by xlink:href.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@Sun.COM    | If someone tells you he is going to make 'a
XML Standards Architect | realistic decision', you immediately
Sun Microsystems, Inc.  | understand that he has resolved to do
                        | something bad.--Mary McCarthy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE9nXskOyltUcwYWjsRAvijAKCBLMKRjaVMRj4EtFV9/aqw0JJI3wCfWist
FjczYgJ7I3YOcvJTDiD1a6M=
=enlJ
-----END PGP SIGNATURE-----

Received on Friday, 4 October 2002 07:28:09 UTC