[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: re: [chairs] Further assistance from Kavi - UDDI Spec TC
Luc, I'm guessing you'll have to point the link to an intermediary HTML page somewhere. That way you can change that page itself - and just leave Kavi to point to that static address. Not optimal I'd agree - as with everything software - there's always a sub-optimal clunky work around... would be nice if everything can just reside on the OASIS server... Karl - will we still have a separate project ftp upload area? If so - that could hold the sub-directories and content - and we could just point Kavi at the entry point to that workspace.... Cheers, DW. ================================================================ Message text written by Luc Clement > 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/t cspecs.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 <
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC