FRPR

From n² wiki

Jump to: navigation, search

Contents

[edit] Functional Requirements for Product Records

editing help

Repurposing FRBR vocab to use with (manufactured) products.

Spawned from SemWeb Music Store, which will be a domain-specific spike

Should be suitable for use in these scenarios :

  • arbitrary product catalogue
  • repair department records (e.g. have you fixed my keyboard yet - the one that got peed on by a cat?).

Hopefully possible to reuse most of the FRBR terms directly (especially Group 1 entities). Some terms may need to be added, e.g. in the car example, a hatchback is a kindOf car, it might not be desirable to make this a rigid, exclusive category. (I see SKOS on the horizon :-)

It would be nice to incorporate PartWhole modelling, like "our car has platinum Porsche hub caps..." - maybe later..?

[5:04pm] mmmmmRob: looking at page 15 (of this: http://www.ifla.org/VII/s13/frbr/frbr.pdf ), work-subject relationships, thinking that maybe you need a product-purpose relationship

See also: http://www.loc.gov/cds/FRBR.html

Other product modelling: SWOP project ( car)


[edit] Example

Our car is a Fiat Punto 3-door hatchback, it has registration PI314.

(abbreviated URIs below, some constructs may be nodes rdfs:label'led with the given string)

first pass...

[edit] Driving 

Driving a frbr:concept .

[edit] Fiat 

http://www.fiat.com a frbr:corporate-body ;
     name "Fiat" ;
     rating "economical" .

[edit] Fiat Punto 

FiatPunto a frbr:Work ;
     frbr:is-created-by http://www.fiat.com ;
     frbr:has-as-subject Driving .


frbr:Work - An abstract notion of an artistic or intellectual creation.

[edit] Fiat Punto 3-Door Hatchback 

FiatPuntoHatchback3Door a frbr:Expression ;
     frbr:is-realised-by http://www.fiat.com ;
     someschema:has-doors "3" ;
     frbr:realizes FiatPunto ;
     frbr:has-a-complement FiatPuntoHatchbackBootLiner ;
     frbr:has-a-transformation FiatPuntoHatchback5Door .


frbr:Expression - A realization of a single work usually in a physical form.

(the long names around here like FiatPuntoHatchback3Door are arbitrary URIs of individuals?)

[edit] Fiat Punto 3 Door Hatchback 1997-2000 

FiatPuntoHatchback3DoorLeftHandDriveUK1997-2000 a frbr:Manifestation ;
     frbr:is-produced-by http://www.fiat.com ;
     frbr:embodies FiatPuntoHatchback3Door ;
     frbr:is-a-successor-to FiatPuntoHatchnack3DoorLeftHandDriveUK1972-1997 ;
     frbr:has-a-successor FiatPuntoHatchback3DoorLeftHandDriveUK2000-2007 .


frbr:Manifestation - The physical embodiment of one or more expressions.

[edit] PI314 

<PI314> a frbr:Item ;
     frbr:exemplifies FiatPuntoHatchback3DoorLeftHandDriveUK1997-2000 ;
     frbr:is-owned-by http://www.danja.com/wateva ;
     foaf:nick "danja's speed machine" .

frbr:Item - An exemplar of a single manifestation.

[edit] Possible Near-Synonyms

Personal danja note - I find the terms/concepts in FRBR really hard to think about, like juggling jelly. For product stuff I think it might be justifiable to use different terms (probably subclassed one way of the other) to make it easier to work with - but have no idea yet of suitable terms.

  • Work - product
  • Expression - model
  • Manifestation - version, edition
  • Item - ...item

Haynes has manufacturer, model, shape, edition and engine breakdown

[edit] How it's done with PMO

Mail from Michel Bohms of SWOP project 

 Our PMO (of SWOP) would say:

 Class Car
 With property license plate nr

 Class FiatPuncto
 Subclass of Car (a "variant class")
 Some class variables fixed.
 With some free parameters like amount of doors etc.

 Then your car with license plate PI314 would be an individual of
 FiatPuncto etc.


 So in the dimension of generic-specific-occurrrence, generics and
 specifics are covered both by classes.
 Local occurrences are nicely handled by treating decomposition relation
 the same as the class variables.

 This way we can have global instances or local instances dependning on
 the needed flexability.
Retrieved from "http://n2.talis.com/wiki/FRPR"
Personal tools