You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we read the primitive attributes and assign values to the class properties. However, we ignore links to other classes. When a reference to another class is discovered, we need to:
find out if the relationship between the two classes is 1:1 or 1:n
ensure that both classes have been created in the map
populate the link and the reverse link with the object references
if it's 1:n, we will add the reference to the list if it's not already there
if it's 1:1, we will set the variable to the reference
@m-mirz This is a slight variation on the lazy-linking strategy we discussed. Instead of storing the rdfid and then later updating with a reference, we just create the linked class, which will later have the attributes filled in. A possible problem with this approach is that we could end up creating components that only exist in the file as links. However:
there's not a huge difference between a broken link and an empty component
that file is badly formed already
I'm not convinced that leaving a broken link is a better strategy
The text was updated successfully, but these errors were encountered:
Component attribute links
Currently we read the primitive attributes and assign values to the class properties. However, we ignore links to other classes. When a reference to another class is discovered, we need to:
@m-mirz This is a slight variation on the lazy-linking strategy we discussed. Instead of storing the rdfid and then later updating with a reference, we just create the linked class, which will later have the attributes filled in. A possible problem with this approach is that we could end up creating components that only exist in the file as links. However:
The text was updated successfully, but these errors were encountered: