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
The index (core) properties defines a set of properties for each concept. The given set of properties doesn't contain properties in which the name of the property is set during the product upload. Examples are e.g.:
The user can set the label "width" and a value for the property dimension of a product.
Custom properties have a label and a value which can be set
The catalogue-search calls this kind of properties "virtual proeprties", because the property in the first example would be not dimension but width and would have a specific value.
These kinds of properties and the properties of eclass are not contained yet. For a semantic (hierachical search) the are needed.
The text was updated successfully, but these errors were encountered:
I think , this is a good starting point. With respect to your last ontology, there are more than just custom properties which have to be considered. I mentioned in my issue description also dimension. ( urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2#Dimension). Are going to add it also?
The index (core) properties defines a set of properties for each concept. The given set of properties doesn't contain properties in which the name of the property is set during the product upload. Examples are e.g.:
The catalogue-search calls this kind of properties "virtual proeprties", because the property in the first example would be not dimension but width and would have a specific value.
These kinds of properties and the properties of eclass are not contained yet. For a semantic (hierachical search) the are needed.
The text was updated successfully, but these errors were encountered: