Bureaucrats, developer, Administrators
9,854
edits
m (relink) |
m (relink) |
||
Line 7: | Line 7: | ||
I've had tremendous trouble trying to figure out how to express [[Product group]]s in generic markup. The idea is that all [[product]]s belong to a [[product group]] and that [[product group]]s can belong to other [[product group]]s. [[tomatoe]]s are [[vegeatable]]s, which are [[food]] etc. | I've had tremendous trouble trying to figure out how to express [[Product group]]s in generic markup. The idea is that all [[product]]s belong to a [[product group]] and that [[product group]]s can belong to other [[product group]]s. [[tomatoe]]s are [[vegeatable]]s, which are [[food]] etc. | ||
The idea is to allow the defining of different relationships between [[product group]]s, for the uses of describing [[Product substitution]]s and [[ | The idea is to allow the defining of different relationships between [[product group]]s, for the uses of describing [[Product substitution]]s and [[sevice cycle]]s and other stuff we haven't even thought of yet. | ||
I was aiming at a generic [[product group]]-element to make the processing software ([[Instructional capital]]) simpler, but I can't get it to work. We could have an generic [[product group]]-element that encapsulates group specific data in a more specific element like: | I was aiming at a generic [[product group]]-element to make the processing software ([[Instructional capital]]) simpler, but I can't get it to work. We could have an generic [[product group]]-element that encapsulates group specific data in a more specific element like: |