W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > April to June 2002

XLiP

From: Masatomo Goto <mg@jp.fujitsu.com>
Date: Wed, 10 Apr 2002 13:55:41 -0400 (EDT)
Message-Id: <4.3.2-J.20020410104137.02b92850@smtp.fla.fujitsu.com>
To: www-xml-linking-comments@w3.org

This message is posted at Feb. 13th 2002, but there is not listed on 
Xml linking comment list. I will post again.


We (Fujitsu) are pleased to introduce updated XLiP which newly 
supports XPointer and XML base functions. Following is our new 
revised implementation report.

Newly supported feature is:

  - Almost all XPointer features
  - XML Base

All these feature can be tested with our demo application.

   URL is :

    [Japanese]
     http://www.labs.fujitsu.com/free/xlip/index.html
    [English]
     http://www.labs.fujitsu.com/free/xlip/en/index.html

Best regards.

   -Masatomo Goto



XML Linking Implementation Questionnaire


--------------------------------------------------------------------------------

General
What is the name of your organization?

      Fujitsu Limited.

How should we contact you on linking matters?

      E-mail to mg@jp.fujitsu.com or xlp@ml.fujitsu.co.jp


What is the name of the linking technology?

      XLiP (XML Linking Processor)

Please describe its functionality and development status briefly. Is it publicly available?

      XLiP is the processor works on DOM. It needs more improvement. 
      It is easy to append the XLiP to a system using DOM.
      XLiP recognizes all XLink features and keeps those information.
      By talking to the XLiP, system can handle Liking information in various way.

      To show XLiP functionality, tree browser has been implemented as the 
      demo application. This browser shows document as "tree" based on DOM.
      It can traverse from staring resource which is the XML information
      set to several types of ending resource (ex. XML information set,
      RTF, HTML, TEXT, Image). 
      This tree browser uses some API of XLiP but supports most of XLink 
      specification features.

If so, what is its current location?

      Publicly available. Only the demo application are available.
      In the future, Pocessor itself will be published and publish the API.
      [Web site]
         [Japanese]
           http://www.labs.fujitsu.com/free/xlip/index.html
         [English]
           http://www.labs.fujitsu.com/free/xlip/en/index.html


XLink
How does the technology use XLink?

      In the tree browser application, it uses XLink specification to achieve
      hyperjump among nodes and several kinds of resources.
      XLink is used to define links and traversal action.

Does (or will) the technology claim XLink conformance?

      nothing specal.

Please provide details about the parts of XLink implemented.

-Traversing simple outbound links 

      In the demo app, starting resource will be shown as the different icon 
      image. Traversal starts depending upon the "actuate" attribute value.
      If "onRequest", traversal starts when user clicks that starting resource
      and ending resource directly will be shown according to "show" attribute 
      value.
      But "onLoad" traversal does not supported. simply ignores it.

-Traversing extended outbound links 

      In the demo app, starting resource will be shown as the different icon 
      image. Traversal starts depending upon the "actuate" attribute value.
      If "onRequest", traversal starts when user clicks that starting resource.
      At that time dialog will be shown to specify which ending resouce to traverse.
      if the user selects one of the ending resources, it will be shown according to 
      "show" attribute value.
      But "onLoad" traversal does not supported. simply ignores it.

-Traversing extended inbound/third-party links 

      Same as traversing extended outbound links

      In the demo app, starting resource will be shown as the different icon 
      image. Traversal starts depending upon the "actuate" attribute value.
      If "onRequest", traversal starts when user clicks that starting resource.
      At that time dialog will be shown to specify which ending resouce to traverse.
      if the user selects one of the ending resources, it will be shown according to 
      "show" attribute value.
      But "onLoad" traversal does not supported. simply ignores it.

-show="new" 

      In the demo app, new window will be created and view the document 
      including those ending resources. Then set the focus to the ending 
      resource.

-show="replace" 

      In the demo app, document including ending resource will be 
      opened and closed currently viewed document which includes starting 
      resource. Then set the focus to the ending resource.

-show="embed" 

      In the demo app, ending resource is embedded as the child of
      staring resource.

-actuate="onLoad" 

      Traversal starts when XLink Processor resolve the XLink declarations and
      those starting resources.

-actuate="onRequest" 

      Traversal starts when user clicks the appropriate cell of the
      starting resources.

-XML Base support for relative URIs 

      supported.

-Linkbase role 

      supported.
      Linkbase can be loaded along with the value of "actuate" attribute. When running
      the demo application, those timings are as follows:

      onRequest ... user clicks that starting resource.
      onLoad    ... processor loads that starting resource.

Any other comments/details? 
What difficulties did you discover in using the XLink specification?

What difficulties did you discover in implementing XLink?

XPointer
How does the technology use XPointer?

Does (or will) the technology claim XPointer conformance?

      No.

Please provide details about the parts of XLink implemented.

     Please visit our web site.

      [Web site]
         [Japanese]
           http://www.labs.fujitsu.com/free/xlip/index.html
         [English]
           http://www.labs.fujitsu.com/free/xlip/en/index.html


Bare names 

      Supported.
      Currently, the processor recoginzes attribute which has "id" for its name 
      as ID attribute.

Child sequences 

      Supported.

id() function 

      Supported.
      But same condition with Bare names

Full XPath 
range-to 

      Supported.

string-range 

      Supported.
      But it is difficult to show the result.

Namespace support 

      Supported.

In programming API 

      Yes.

In user interface 

      Yes.
      XLinkTreeViewDemo application provides the function 
      to address the nodes which identified by the user
      specified XPointer string through a input dialog.

Selecting/showing multiple non-contiguous ranges 

      Yes. 

Any other comments/details? 

What difficulties did you discover in using the XPointer specification?

      Syntax makes xpointer string too long.

What difficulties did you discover in implementing XPointer?

      It doesn't simply implemented on top current XPath 
      implementation. Location set concept requires essential
      improvement of XPath implementation.


XML Base
How does the technology use XML Base?

Does (or will) the technology claim XML Base conformance?

      No.

Please provide details about the parts of XML Base implemented.

      In the XLiP, XML Base is used to resolve the relative URI in
      "href" attributes of XLink namespace.

What difficulties did you discover in using the XML Base specification?

      None.

What difficulties did you discover in implementing XML Base?

      Distinction between URL and system identifier.

Integration
How does the technology uses XLink, XPointer, and XML Base in conjunction?

     XLink resolution is processed at first. In that process, XPointer
     resolving processing and XML Base resolving processing be called.

Please provide details about the implementation.


Handling single nodes as participating resources 
Handling ranges of nodes as participating resources 
Handling participating resources made up of non-contiguous pieces 
Any other comments/details? 
What difficulties did you discover in using their specifications together?

     It doesn't have any difficulties. Easy to use.

What difficulties did you discover in implementing them together?

     It will not so difficult to implement together.

Conclusion
Do you have any other comments you would like to share with us? 
---
Masatomo Goto <mg@fla.fujitsu.com>
595 Lawrence Expressway, Sunnyvale, CA 94085, USA
Voice mail: (408)530-4620,  Fax: (408)530-4515
Received on Monday, 15 April 2002 06:57:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:39:43 GMT