JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-ARCHITECTURE Archives


DC-ARCHITECTURE Archives

DC-ARCHITECTURE Archives


DC-ARCHITECTURE@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-ARCHITECTURE Home

DC-ARCHITECTURE Home

DC-ARCHITECTURE  February 2012

DC-ARCHITECTURE February 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: DCAM: Karen Coyle on application profile design patterns (2008)

From:

"[log in to unmask]" <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Wed, 22 Feb 2012 14:31:45 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (126 lines)

 All

I think these patterns are a good starter set, and suggest we add the more
complex patterns I suggested earlier [1].

These range from overlaps with Karen's set through tests of additional
specifics in SoDC-CL such as cardinality, to the mega-patterns of concrete
schema interoperability.

I'm happy to try and translate these into the formats used in Karen's
patterns (including examples).

btw, I wish I'd know about Alisatair's stuff on the architecture wiki
before now - it's a great articulation of issues we've been discussing in
the ISBD/XML Study Group, FRBR Review Group, and Joint Steering Committee
for Development of RDA. But the language/terminology mis-match between
abstract modellers and librarians certainly prevented me from finding it
via Google.

Cheers

Gordon

[1]
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1202&L=DC-ARCHITECTURE&P=6405





On 22 February 2012 at 02:46 Thomas Baker <[log in to unmask]> wrote:

> In 2008, Karen started to enumerate some common design patterns.  We have
> provisionally concluded that a revised DCAM would need to be be based on,
and
> illustrated with, examples.  Here -- minus the DSP angle-bracket examples
-- is
> the starter set of patterns.  They are similar in nature to the examples
that
> Alistair penciled into his draft.
>
> Can we take this as a start, or does anyone want to propose a different
type of
> examples (or patterns)?  As Antoine has suggested, the effort of just
trying it
> might be less than the effort of discussing it in the abstract...
>
> Tom
>
> ----------------------------------------------------------------------
> http://dublincore.org/dcmirdataskgroup/apDesigns
>
>     Some Application Profile Design Patterns
>         These design patterns are based on the Dublin Core Description
Set
>         Profile (DSP). The DSP structure is a single description set that
>         contains one or more descriptions, each of which contains one or
more
>         metadata statements. Both the description and the metadata
statements
>         can define constraints on usage.
>
>         Statement: A Simple String
>             The simplest metadata statement describes a property that
takes a
>             simple string value ("literal"), with no constraints.
>             [... example ...]
>
>         Mandatory and Repeatable
>             Both description templates and statement templates can be
coded as
>             mandatory/optional and repeatable/not repeatable. This is
done
>             using the values "minimum" and "maximum". The most commonly
used
>             values are:
>             [... example values ...]
>
>             The following code defines a property ("title") that is
required
>             and not repeatable:
>             [... example ...]
>
>         Using Controlled Lists
>             One way to assure consistency of metadata use is to require
that
>             values be taken from a controlled list. Controlled lists can
be
>             short ("yes" "no" "maybe") or they can be long (such as the
Library
>             of Congress Subject Headings, which number about 250,000).
>
>             To define a property as taking a member of a controlled list
as its
>             value using the terms of the DC Application Profile, the
controlled
>             list is called a "Vocabulary Encoding Scheme" and the list
itself
>             is represented with its identifier, a URI. Use of a list can
be
>             mandatory or optional.
>
>             This code illustrates a "subject" property that optionally
can use
>             terms from the LC Subject Heading list.
>             [... example ...]
>
>             This code shows a subject property that requires the use of a
term
>             from the LCSH list:
>             [... example ...]
>
>             If you have a short list that you wish to embed in the DSP
you can
>             do that using the "LiteralOption". Each term is listed, and
values
>             must be taken from the list:
>             [... example ...]
>
>             You can support multiple languages with the LiteralOption by
>             including the XML "lang" attribute:
>             [... example ...]
>
> --
> Tom Baker <[log in to unmask]>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

November 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
September 2005
August 2005
July 2005
June 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
December 2000
November 2000
October 2000


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager