Attached is a UML class diagram that illustrates a sensible mapping between FRSAD and SKOS/SKOS-XL. FRAD would look somewhat similar.
Since SKOS/SKOS-XL can be used to solve authority control use cases, it arguably should rather than trying to promote a library-centric alternative. I would also argue that SKOS is easier to use than FRSAD, particularly in the most common cases where the literals themselves don't need to be treated as objects.
Jeff
> -----Original Message-----
> From: DCMI Architecture Forum [mailto:[log in to unmask]]
> On Behalf Of Karen Coyle
> Sent: Sunday, May 27, 2012 3:52 PM
> To: [log in to unmask]
> Subject: Re: Fwd: [BIBFRAME] IFLA Functional Requirements namespaces
> published
>
> Jeff, perhaps they are, I haven't seen them coded in that way. What I
> find interesting is how different they are from each other, even though
> they are both, theoretically, describing authority data. (The "AD" is
> "authority data.")
>
> I put a copy of the FRAD entity diagram on my site:
>
> http://kcoyle.net/rda/frad_2009-fr_13.pdf
>
> This is the one from the French version, since the English version
> isn't
> available.
>
> kc
>
> On 5/27/12 11:53 AM, Young,Jeff (OR) wrote:
> > Karen,
> >
> > FRAD and FRSAD are basically variants of SKOS and SKOS-XL. Foaf:focus
> is a key factor for connecting these back to ontological models. The
> authority section of the lld-xg report addresses this but may not be
> clear enough.
> >
> > Jeff
> >
> > Karen Coyle<[log in to unmask]> wrote:
> >
> > I should mention that I am keeping a wiki page [1] relating to the
> > various versions of FRBR in RDF, with links to discussions around the
> > issues of modeling -- in particular the question of defining the FRBR
> > classes as disjoint.
> >
> > Also, FRAD [2] resembles FRBR in structure, but FRSAD [3] takes a
> very
> > different approach with only two classes, Thema and Nomen. An
> > interesting aspect of FRAD, which reflects standard library practice,
> is
> > that it retains the concept of a "controlled access point" and
> includes
> > a relationship to the rules under which the access point was
> developed
> > and the agency that created the access point by applying the rules.
> >
> > If I run into discussions of these latter FRs I will add them to the
> > wiki page.
> >
> > kc
> >
> > [1]
> >
> http://futurelib.pbworks.com/w/page/48221836/FRBR%20Models%20Discussion
> > (and linked from the home page http://futurelib.pbworks.com )
> >
> > [2]
> > http://www.ifla.org/publications/functional-requirements-for-
> authority-data
> > (This is the web page for the committee. The English language version
> of
> > FRAD is not available online, but there are other languages available
> on
> > that page.)
> >
> > [3]
> > http://www.ifla.org/files/classification-and-indexing/functional-
> requirements-for-subject-authority-data/frsad-final-report.pdf
> >
> > On 5/26/12 9:32 PM, Dan Brickley wrote:
> >> Fyi
> >>
> >>
> >>
> >> Begin forwarded message:
> >>
> >>> *From:* Riva Patricia<[log in to unmask]
> >>> <mailto:[log in to unmask]>>
> >>> *Date:* 27 May 2012 02:33:43 EEST
> >>> *To:* [log in to unmask]<mailto:[log in to unmask]>
> >>> *Subject:* *[BIBFRAME] IFLA Functional Requirements namespaces
> published*
> >>> *Reply-To:* Bibliographic Framework Transition Initiative Forum
> >>> <[log in to unmask]<mailto:[log in to unmask]>>
> >>>
> >>> *Functional Requirements namespaces published*
> >>>
> >>> Namespaces for the Functional Requirements (FR) family of
> >>> bibliographic metadata models have been published in Resource
> >>> Description Framework (RDF), the basis of the Semantic Web. The
> models
> >>> include Functional Requirements for Bibliographic Records (FRBR),
> >>> Functional Requirements for Authority Data (FRAD), and Functional
> >>> Requirements for Subject Authority Data (FRSAD). The namespaces can
> be
> >>> accessed at _http://iflastandards.info/ns/fr/_.
> >>>
> >>> The FR element set vocabularies include RDF classes and properties
> >>> corresponding to FR entities, attributes, and relationships. Each
> >>> class and property has a Uniform Resource Identifier (URI) for use
> in
> >>> Semantic Web data triples.
> >>>
> >>> A full de-referencing service is available for each URI. When used
> in
> >>> an ordinary Web browser, the URI displays HTML pages with
> >>> human-readable information about the element or concept. When used
> in
> >>> a semantic browser, the URI retrieves machine-readable information
> in
> >>> RDF/XML format. It is also possible to retrieve this format using
> an
> >>> ordinary Web browser.
> >>>
> >>> For example, the URI for the FRBR entity-relationship (FRBRer)
> model’s
> >>> Group 1 entity “Work” is
> >>> _http://iflastandards.info/ns/fr/frbr/frbrer/C1001_. To retrieve
> the
> >>> RDF/XML information in a normal Web browser, use
> >>> _http://iflastandards.info/ns/fr/frbr/frbrer/C1001.rdf_; that is,
> add
> >>> the file extension “.rdf” to the URI.
> >>>
> >>> Another example is the FRSAD attribute “has appellation”: the URI
> of
> >>> the corresponding RDF property is
> >>> _http://iflastandards.info/ns/fr/frsad/P2003_ and the RDF/XML file
> can
> >>> be retrieved in a normal browser using the URL
> >>> _http://iflastandards.info/ns/fr/frsad/P2003.rdf_.
> >>>
> >>> The element set for a specific FR model can be accessed as follows:
> >>>
> >>> *
> >>>
> >>> FRBRer: _http://iflastandards.info/ns/fr/frbr/frbrer/_
> >>>
> >>> *
> >>>
> >>> FRAD: _http://iflastandards.info/ns/fr/frad/_
> >>>
> >>> *
> >>>
> >>> FRSAD: _http://iflastandards.info/ns/fr/frsad/_
> >>>
> >>> The FR namespaces are maintained and accessed using the Open
> Metadata
> >>> Registry (_http://metadataregistry.org/_).
> >>>
> >>> These element sets reflect the current published models, however,
> as
> >>> the FR family is in the process of being consolidated, this may
> result
> >>> in the eventual deprecation of some URIs.
> >>>
> >>> Pat Riva
> >>> Coordonnatrice, section des monographies
> >>> Direction du traitement documentaire des collections patrimoniales
> >>> Bibliothèque et Archives nationales du Québec
> >>> 2275, rue Holt
> >>> Montréal (Québec) H2G 3H1
> >>> Téléphone : 514 873-1101 poste 3624
> >>> Télécopieur : 514 873-7296
> >>> [log in to unmask]<mailto:[log in to unmask]>
> >>> www.banq.qc.ca<http://www.banq.qc.ca/>
> >
>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
|