[chairs] Further assistance from Kavi - UDDI Spec TC

Title: Further assistance from Kavi - UDDI Spec TC

Karl

I have additions questions regarding content management that are hopefully simple to answer; unfortunately, the answers to these questions did not jump out at me.

1. Referencing document links in a version agnostic way. There are many situations, where you want to host a document in such a way that the link to it is version agnostic - as such, the link is always the same. Two situations come to mind:

A. On http://kavi.oasis-open.org/apps/org/workgroup/uddi-spec/ we've added a Quick Links section in the Group Notes/Public Description containing: 

Quick Links

Committee Specifications

UDDI Spec TC Committee Best Practices

UDDI Spec TC Committee Technical Notes

Specification Change Requests

UDDI Spec TC Committee Drafts

Minutes

Charter

Intellectual Property Rights

UDDI Mailing List

Membership at a glance

Press

Contributed Material

UDDI.org Member Section 

What I've found is that every time a document is updated, the links referencing it changes as a result of versioning. For example, if I were to update the "Committee Specifications" page (the first link), the link to "http://kavi.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/116/tcspecs.htm" would change from …/116/tcspecs.htm to ../somenewnumber/tcspecs.htm. This is problematic in that quick link to it (and all other links to this document) is (are) broken.

B. It is customary for specs to have both a "current" and a "version insensitive" link in the header. For example take a look at http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.htm. In this doc, two links are available:

Location:

http://uddi.org/pubs/ProgrammersAPI-V2.04-Published-20020719.htm

Latest version: 

http://uddi.org/pubs/ProgrammersAPI_v2.htm

In both cases the links need to be a) version invariant and b) need to be "hard-coded". We need to determine and control what a link to a document is going to be. As such, we need to be able to set a fixed link on a doc that is stored on a kavi system. Not having this capability will make it difficult to use kavi to host committee specs.

Does kavi support this? If so, how do we exploit this feature?

2. Referencing content from html pages stored on kavi.

Some of the content we'd like to host on kavi references local content. For example, http://kavi.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/105/bps.htm has the following reference: 

<img src=""top_of_page.gif"" width="43" height="25" border="0" alt="TOP OF PAGE"></a></font></p>

The source image "top_of_page.gif" is collocated with the document but does not render on the page (most likely due to version / document path issues). 

Could you please provide info explaining how to reference this content? The answer to this is likely dependent on the answer to the above.

Thanks in advance,

Luc Cl幦ent

Microsoft

UDDI Spec TC Co-chair