OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] XML Data Modellling/Linking (was RE: [xml-dev] Afte r XQue

[ Lists Home | Date Index | Thread Index ]

I understand.  The popup example is given because 
it is clearly a semantic for a control, and in the grand 
tradition of genCoding, when GUIing, GUI.  I too 
think hyperlinking is a control type (how many 
times have we had this discussion now??) whereas, 
a relationship is just pointing by some reference 
type (and that is where the trouble starts, nameloc, 
relloc, treeloc anyone?).

Otherwise, this thread comes close to resurrecting 
archForms in RDF syntax.

As I said earlier to Liam, I don't think we take the 
leap because the benefits (among, device independence 
of content) are hard to sell without veryProminentRunningCode.


From: DuCharme, Bob (LNG-CHO) [mailto:bob.ducharme@lexisnexis.com]

Len Bullard wrote:
>So you want to go from this
><myElement oncontextmenu="doPopup(); return false;">Something</myelement>
> (snip)
> (some CSS)
><popup class="mylinktype" >
>  <item>MyItem</item>
>  <item>MyItem</item>
>or something similar?

I wouldn't even want to store it as a "popup" element. Pop-ups are device
specific; many devices can't do it. Here's a more semantic example inspired
by RFCs. Imagine that internally the IETF stores this:

   <rfc num="1111"/> <!-- or however they choose to reference another RFC
   <rfc num="2222"/>
   <rfc num="3333"/>

Then, they convert it to something like what you showed originally with one
stylesheet for web delivery, a sidebar with background shading for print
delivery with another stylesheet, etc. 


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS