On Mar 1, 2009, at 8:36 PM, Jeremy Carroll wrote:
> > > I'll let Scott or Holger answer about how best to use this URI in > TBC, but I'll comment on the URI itself: Thanks Jeremy for the technical background. I just noticed that TBC did not allow entering URIs without a matching prefix in the create class/property/instance dialogs. I have generalized this for the new beta, so that arbitrary URIs can be directly entered between <...> brackets. This just as an aside. My understanding is that the URIs suggested by TK will not be used for property names, and as such should be OK for tools like TopBraid's RDF/ XML exporter (which indeed uses Jena's split algorithm). So as long as you are happy with reading URIs like <cpe:/a%3Aapache%3Ahttp_server %3A1.3.30> on your screen, it's technically possible. The next beta will (finally) have a feature that allows you to switch the whole display between qnames/URIs and human-readable labels (rdfs:label and sub-properties thereof). Then, a good practice will be to have the URIs in whatever (ugly?) form you want, but at least have human-readable strings such as "Apache HTTP Server version 1.3.30" as rdfs:labels of these URI resources. Beta 2 is scheduled for early next week; we are planning to freeze code for testing tomorrow. Regards, Holger --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
