Hi Holger Thank You for your quick response but I think the link to the blog post you included is not relevant to my question.
I am looking forward to your proposed solution to address this issue in the 3.o release as the current generation of qnames for imports is impractical. I think this issue is actually related to the treatment of URIs for the rdf:about property in TBC. Best, Marco On Thu, Oct 30, 2008 at 12:15 PM, Holger Knublauch <[EMAIL PROTECTED]> wrote: > > Hi Marco, > > currently TBC will add prefixes for new namespaces after you add a > file or URL to the Imports View. The main motivation for this policy > was to help with cases where the imported files only declare a default > namespace but no named prefixes. See also [1]. Fortunately fewer files > fall into this category so that I will disable this feature by default > in the next version. Thanks for the suggestion. > > Holger > > [1] > http://composing-the-semantic-web.blogspot.com/2007/05/default-namespaces-considered-harmful.html > > > On Oct 29, 2008, at 1:34 PM, Marco Neumann wrote: > >> >> Hi Don, >> >> TopBraid Composer actually asks you politely when you try to import an >> ontology to a project (a window is displayed that allows you to cancel >> the prefix fix). >> >> I want the same for the imports windows where you can drag your files >> into the imports reference list. TQ please provide such an option. >> >> Best, >> Marco >> >> >> On Wed, Oct 29, 2008 at 3:32 PM, donundeen <[EMAIL PROTECTED]> >> wrote: >>> >>> Hi Marco, >>> I have this same issue, of prefixes being created when I do Imports >>> >>> I'm wondering what you mean in the paragraph: >>> "When I import the documents into TopBraid and ignore the recommended >>> import statements ..." >>> >>> what do you mean by that? If there's a way to do my imports without >>> causing these namespaces to be created, that would be great. Usually, >>> as you do, I drag my imported files into the imports window of my >>> importing file. >>> >>> >>> I find that sometimes literally hundreds of prefixes are created, for >>> example when I import Calais result data. I'm not sure why that >>> happens either. Honestly, I can't think of a time I've ever WANTED >>> any >>> namespace prefixes to be created for me. Is this a necessary feature? >>> Perhaps there's a way I can turn it off, or does this feature overlap >>> with some other necessary functionality? >>> >>> >>> - don >>> >>> On Oct 29, 1:29 pm, "Marco Neumann" <[EMAIL PROTECTED]> wrote: >>>> Hi, >>>> >>>> I have discussed this with Dean today and was wondering if you have >>>> and idea what's going on. I have of number URL that produce RDF >>>> member >>>> information for Semantic Web Meetups around the world >>>> >>>> New Yorkhttp://www.swnyc.org/sparql/?id=274991 >>>> >>>> Palo Altohttp://www.swnyc.org/sparql/?id=455214 >>>> >>>> Washingtonhttp://www.swnyc.org/sparql/?id=987383 >>>> >>>> Chicagohttp://www.swnyc.org/sparql/?id=970635 >>>> >>>> Los Angeleshttp://www.swnyc.org/sparql/?id=1066567 >>>> >>>> When I import the documents into TopBraid and ignore the recommended >>>> import statements (recommended by Dean ) all is working well and the >>>> files are usable as planed. >>>> >>>> On the other hand if I import any of these URLs in the imports >>>> window >>>> of TopBraid it actually transforms some of my profile URIs into >>>> unwanted qname prefixes. >>>> >>>> Any ideas? >>>> >>>> Best, >>>> Marco >>>> >>> >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
