[
Lists Home |
Date Index |
Thread Index
]
- From: "Bullard, Claude L (Len)" <clbullar@ingr.com>
- To: Paul Fishwick <fishwick@cise.ufl.edu>, Jean-Marc Vanel <jmvanel@free.fr>, xml-dev@xml.org, x3d-contributors@web3d.org, Frederic ABIVEN <Frederic.ABIVEN@teaser.fr>, Patrick Laug <Patrick.Laug@inria.fr>, Amine Hassim <Amine.Hassim@inria.fr>, Jean Marc VANEL <jean-marc_vanel@effix.fr>
- Date: Thu, 2 Mar 2000 09:33:13 -0600
Another piece is XLinks and XPointers. These are derived from the
work on HyTime and TEI:
o XLink - expresses the relationship among resources where the resources
are are content in a location. Extended XLinks can contain multiple
resources.
It is important to note the these can be grouped and can exist separately
from the content addressed.
o XPointer - multiple ways to resolve a location (that is, what to do when
IDs
and names aren't used. A flaw at the heart of the Sony DTD is it's over
reliance
on names). For example, span(child(4, myElement), child(5,myElement)).
IOW,
you don't always have control over content, so you need read-only linking.
XLinks and XPointers can be used to create virtual documents made of others
pieces. IOW, they are used to pull together documents similar to the way a
recordset can be a view of joined tables. There are even tools to map from
SQL to XLink and back. These were the ideas surfaced in the nineties from
work in the IETM and TEI communities who understood the problems of
aggregation of hypermedia content types in depth. So the problems you note
with
IGES, STEP, etc. have been thought through in some detail.
Using these tools requires a shared XML object model; not XML-like.
Len Bullard
Intergraph Public Safety
clbullar@ingr.com
http://fly.hiwaay.net/~cbullard/lensongs.ram
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
> -----Original Message-----
> From: Paul Fishwick [SMTP:fishwick@cise.ufl.edu]
>
> I still am hoping that there exist evolutionary methods that will allow
> X3D and all of
> the other XML implementations to co-exist and co-operate. This hope may
> not be
> justified, but I am ever the optimist (for some unknown reason).
> Namespaces are
> proposed as something we should consider to aid in bridging gaps.
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/threads.html
***************************************************************************
|
