Hi Phil, Answers below:
> Hi Gokhan > > I have only just tried this out, so sorry for the delay. > I was a little confused as your example gave the same result as my two > attempts i.e. nothing out. THEN I used my brain and connected an > ImportRDF fromWorkspace to the ConvertSpreadsheet with an actual > connection. Then it (and mine) worked. Doh! > I see the properties with the correct datatypes etc. Sorry I wasted a > bit of your time here. > No problem. I am happy that it works. > I've experimented with a couple of things and may have found a bug/issue > or two. > 1. In your example you use %1 as the instance pattern. > I would like to use %6-%7 however when the property > sml:importToInputGraph is defined it will only ever create %1 instance > patterns and ignores anything else that has been stated. For my import > to work correctly I need to define the pattern. This works fine as long > as sml:importToInputGraph is not used. > This is by design. But of course, we would need to say that instance patterns are not possible at the moment while sml:importToInputGraph is set as true. When importing to the input graph, the importer assumes that each cell is already a resource or a literal. The key reason behind this is that the imported resources or statements may already exist in the input graph. When not importing to the input graph, i.e. creating a new graph/model, the importer has more freedom to create instances. However, we can consider your issue as an enhancement request to make the true and false states of sml:importToInputGraph more similar to each other. > I've also seen the instance pattern not work as requested in normal use. > (trivial I know) > product%6-%7 actually gives product-<value>-<value> and a pattern of > product-%6-%7 gives product--<value>-<value>. > Thanks, I reproduced this as well. It will be fixed in the next release. > 2. When I import a spreadsheet without the use of sml:importToInputGraph > with an instance pattern of %6-%7 (which are both paddednumbers e.g. > 001-10) I see the creation of "unique" resources based on the rows of > data. i.e. if %6 for three rows is 101 and %7 is "10", then I see three > instances with the identifiers 101-10, 101-100, 101-101. In some > situations I really like this behavior and in other cases it's not what > I'm looking for and is really annoying. Could we have a Boolean on this > module for the creation of unique resources? > We wouldn't want the importer to become too complicated. But we will also consider this as enhancement request for a more advanced spreadsheet importer flavor. > I've also noticed that in the case where I was using the property > sml:importToInputGraph all the %1 identifiers were string values but the > resources created were not unique. E.g. if three rows had the value of > %1 as "TBC" I would have expected three resources created with the id's > TBC, TBC0, TBC1. But it didn't. It just created one instance of TBC. > This is a real problem for me, where I need differentiate. > So if I could get the above request could I also have the unique > resource created whether it is fact numeric or alpha numeric and whether > or not the importToInputGraph is used? > > In this situation, in addition of losing the possibility to create one "TBC" resource, also the possibility to re-use an already existing "TBC" resource from the input graph would also be lost. However, we will also consider this as enhancement request for a more advanced spreadsheet importer flavor. Thanks, Gokhan -- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to topbraid-composer-us...@googlegroups.com. To unsubscribe from this group, send email to topbraid-composer-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en.
