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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ciq message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ciq] Re: CIQ Specifications & XLink


Ram,
 
I concur with Michael on this one.
 
The only folks using Xlink that I know are the XBRL - and its almost a deliberate choice there - since then you have to use a XBRL tool that has Xlink support in it - creates a closed marketplace.
 
I suggest that we look for other means here.
 
The issue with general Xlink support for regular parsers - eg Xerxes - is quite literally - how long is a piece of string?  With an XML document - its finite - and hence has a local memory model.  When you do Xlinks - you do not know what you are Xlinking (in the general case).  Obviously in the case of XBRL its a finite closed world - so that works OK.
 
Perhaps we can use includes or imports - or use simple http URL links inside comments - to provide the logical linkage you are after?  Also - we now have the static area:
 
 docs.oasis-open.org/ciq
 
available to us - so we can reference to content there too - if you need to associate?
 
DW


-------- Original Message --------
Subject: [ciq] Re: CIQ Specifications & XLink
From: "Ram Kumar" <kumar.sydney@gmail.com>
Date: Thu, August 10, 2006 10:22 am
To: michael.blaim@kremsresearch.at
Cc: ciq@lists.oasis-open.org, "Max Voskob" <max.voskob@paradise.net.nz>

Dear Michael,

The reason we want to use XLink is that it simplifies providing
links between multiple resources (e.g parties) and relationships
between the resources that might exist in multiple documents.

Regards,

Ram

On 8/11/06, michael.blaim@kremsresearch.at
<michael.blaim@kremsresearch.at> wrote:
>
> Dear Mr Kumar,
>
> We are currently working on an XML specification for customer (party)
> information for travel and tourism with special focus on data protection and
> security. We use xNL, xAL (v3.0) and xCRL (v2.0, but we are looking forward
> to v3.0). These specifications really meet our requirements (flexibility,
> scalability, granularity etc) so far. The one thing we are not sure of is
> the XLink references. Although XLink is ideal for XML references in theory
> we can't find a way to put it into practice (with processors, parsers etc).
> So what is the reason for CIQ TC to use XLink?
>
> Best regards
> Michael Blaim
>
> Research Fellow
> Tourisms Research Center Krems
> Hofrat Erben Str 4
> 3500 Krems
> Austria
> phone: +43 2732 72177 25
> fax: +43 2732 72177 21
> mail: michael.blaim@kremsresearch.at
> web: http://www.kremsresearch.at
>
> anet - austrian network for e-tourism
> http://www.anet-network.at
>
>
>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]