This is the archive of the goodrelations dicussion list

Le 13 nov. 2012 à 14:02, Martin Hepp <martin.hepp at ebusiness-unibw.org> a écrit :

> For exposing less structured data, we will have a new class gr:PropertyValue in the next version of GoodRelations that allows you to encode exactly what you seem to want. Release to be expect shortly.

do you mean what is described at 
http://wiki.goodrelations-vocabulary.org/Documentation/Product_features
(but not in the specification page)?:

Hence, GoodRelations from release 2012-08-01 onwards supports a novel pattern based on
gr:ProductFeature and
gr:Feature
that allows publishing arbitrary property-value pairs for product features.

schema:feature [ a schema:ProductFeature ;
                       schema:propertyName "Power supply" ;
                       schema:propertyValue "110-220" ;
                       schema:unitText "Volts" ] ;

you can imagine that I like this kind of pattern. Will it be possible to write something like:

x:myScrew gr:feature  foo:Value3MM.

foo:Value3MM a gr:ProductFeature ;
	gr:featurePropertyId foo:threadDiameter ;      // or maybe instead: a foo:ThreadDiameter ?
	rdfs:label "3 mm" ;
	gr:hasUnitOfMeasurement "MMT"^^xsd:string ;
	gr:hasValue 3.

That would be very close to what we have in the configuration ontology! (with Specification == ProductFeature)
It allows for incremental refinement of the data. For instance, you can start with just
foo:Value3MM a gr:ProductFeature ;
	gr:featurePropertyId foo:threadDiameter ;      // or maybe instead: a foo:ThreadDiameter ?
	rdfs:label "3 mm" .


Best,

fps


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ebusiness-unibw.org/pipermail/goodrelations/attachments/20121113/6579728f/attachment.html>