[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: linking, 80/20

• To: Paul Prescod <paul@p...>
• Subject: Re: linking, 80/20
• From: Erik Wilde <net.dret@d...>
• Date: Mon, 19 Aug 2002 20:41:10 +0200
• Cc: xml-dev@l..., Ann Navarro <ann@w...>, "Simon St.Laurent" <simonstl@s...>
• References: <3D5EB23A.F74BA6F7@p...> <4.3.2.7.2.20020818100859.00bb5c90@m...> <3D61247A.1050306@d...> <3D6137CC.65EA915F@p...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721

Paul Prescod wrote:
> Erik Wilde wrote:
>>so what about defining an xlink data model in terms of infoset
>>extensions, referencing it in xhtml and defining an xhtml-happy syntax
>>for it, and then going ahead and defining a css3 module for link
>>formatting? 
> So what you're saying is that XHTML and XLink will be hard-coded to
> integrate with each other at the prose specification level (rather than
> through any syntax) and other vocabularies will have to integrate with
> XLink through the intrusive XLink-namespaced attributes? I don't see
> that as progress.

it's not the prose level, but i don't have any complete solutions yet i 
could pull out of my pocket. i think that the xlink data model would be 
defined in terms of infoset contributions, and that this spec would 
define a namespace uri. this namespace uri would then be used in the 
xhtml spec to refer to the semantics and infoset contributions defined 
in the xlink data model spec.

>>css3 would require some work, because the selectors would need to be
>>extended to cover infoset extensions, and a new module for properly
>>handling link formatting would be required. however, i think it would be
>>worth it, since this could be used for *any* vocabulary being built on
>>the xlink data model.
> When a browser sees a new vocabulary how will it know how to map from
> the syntax into the XLink data model?

there would be a css or xslt style sheet associated with the new 
vocabulary to define the processing of xlink infoset contributions. the 
xlink infoset contributions would be defined in the way how the new 
vocabulary defines markup for xlink data model items and properties. i 
am not sure how this could be made in the best way, either prose (sorry! 
then it needs to be hard-coded in the browser), or some formalized 
mapping mechanism (xslt? xpath? or something simpler? i have to think 
about that...).

this probably will not sound all that appealing on first sight. however, 
i think that having a universal hypermedia model for the web would be a 
very good thing. there once was a time when the web was considered a 
hypermedia system, and not only an infrastructure for having stuff sent 
to browsers.

cheers,

erik wilde  -  tel:+41-1-6325132  -  fax:+41-1-6321035
           mailto:net.dret@d... -  http://dret.net/
           computer engineering and networks laboratory
           swiss federal institute of technology  (eth)
           * try not. do, or do not. there is no try. *

• Follow-Ups:
  • Re: linking, 80/20
    • From: "Thomas B. Passin" <tpassin@c...>
  • RE: linking, 80/20
    • From: "Didier PH Martin" <martind@n...>

• References:
  • Re: linking, 80/20
    • From: Paul Prescod <paul@p...>
  • Re: linking, 80/20
    • From: Ann Navarro <ann@w...>
  • Re: linking, 80/20
    • From: Erik Wilde <net.dret@d...>
  • Re: linking, 80/20
    • From: Paul Prescod <paul@p...>

• Prev by Date: Re: CDATA section
• Next by Date: RE: linking, 80/20
• Previous by thread: Re: linking, 80/20
• Next by thread: RE: linking, 80/20
• Index(es):
  • Date
  • Thread