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  January 2012

DC-ARCHITECTURE January 2012

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

2011-01-04 DCAM editors' call - report

From:

Thomas Baker <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Wed, 4 Jan 2012 12:20:17 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (138 lines)

2011-01-04 DCAM editors' call - 9:00 EST

Attended: Tom, George, Stuart, Richard, Kai, Michael, Jane
This report: http://wiki.dublincore.org/index.php/DCAM_Revision/TeleconReport-20120104

----------------------------------------------------------------------
Summary of actions

ACTION: Tom and Richard to put placeholder for introductory text into wiki document
at http://wiki.dublincore.org/index.php/DCAM_Revision_Draft.

ACTION: Kai and Tom to work on technical part in wiki, e.g.:
    http://wiki.dublincore.org/index.php/DCAM_Revision
    http://wiki.dublincore.org/index.php/DCAM_Revision_Scratchpad
    http://wiki.dublincore.org/index.php/DCAM_Revision_Graphics

----------------------------------------------------------------------
Discussion

Tom: Substantive discussion occurs on the DC-Architecture list unless there are
complaints about the traffic.  We can start writing at
http://wiki.dublincore.org/index.php/DCAM_Revision_Draft.  Need to start
builing a structure for the revised document(s).  Need to give something to
general readers, but technical documentation for more in-depth information.
General document provides examples, rationale, and uses of DCAM.  What are
DCAM's functional requirements?

Stuart: Premature to decide whether one or two documents? Nothing wrong with
the original goals, but it missed the mark with audiences.  Range of readers --
continuum from expert to beginners.  Onion layers. If we look at Website data,
people coming for metadata basics.  Could be documentation in layers. Every
term linked to glossary.

Jane: I want to be able to understand it at different levels, when struggling
to "get it".  People need to find their access points.

Stuart: Again, web statistics; bounce rate on those pages is high.

Jane: I like Stuart's onion metaphor - want to understand at different levels
in order to convey. Not just for teaching, but people in research looking.
Existing documentation is basically okay, but hard for people to read without
investing alot of time.

Stuart: People don't have time, so they give up.

Kai: Way we document DCAM. We want to base it on RDF, but maybe want to hide
details. I like the idea of more abstract docucmentation for the user. Still
not entirely sure what we want to do with DCAM.  When I approached this task,
may have seen it in overly simple terms. I thought we could just rewrite what
is there. But I see we need to address potential issues.

Tom: Introduction should describe function of DCAM; what are the requirements?
See http://wiki.dublincore.org/index.php/DCAM_Revision_Scratchpad: mapping of
concepts.  Pete Johnston's work on DC-Text makes some things that are implicit
in DCAM more explicit.  Also important to see what is happening in the RDF
Working Group.  Notion of "Description Sets" may be clearer for general readers
-- easier to explain -- than "Named Graphs".  What is DCAM good for? What is
its purpose? Needs to be part of an introduction. Current introduction is a
good part of the current specification, but some of the requirements that have
come up are not articulated there.

Stuart: Pedagogical functions will be layered on top of what DCAM is. First
task is to determine what's wrong with current DCAM, what needs to happen
(i.e., on technical level) -- then address the pedagogical piece, how
presentation is layered on top of this.  Pedagogical functions don't drive what
the DCAM is, how it is presented may be influenced by the pedagogic concerns.

Michael: Structure of specification and primer, like W3C, could work well.
Primer must be heavily edited, but would be built on specification.

Richard: Role for bridge to RDF. The "Is it based on RDF?" discussion reflects
this.

Stuart: Richard, you nail the pedagogical point. We use in teaching. What DCAM
did for me: provided a principled way for thinking that opened the door. This
is how it is used. Helps people go from where they are into a new space.

Tom: These are useful points that need to be written up. Put a placeholder in
the wiki with an introduction. Use the introduction as a place to collect text.

ACTION: Tom and Richard to put placeholder for introductory text into wiki document
at http://wiki.dublincore.org/index.php/DCAM_Revision_Draft.

Richard: Continue looking at other DCMI documentation (like the "using dublin
core" revisions) to make sure that everything aligns and can lead users through
concepts.

Stuart: DCMI Metadata Terms, Glossary, DCAM, User Guide - moving forward, these
documents need to be tightly coupled. Definitions linked to examples, etc.

Tom: Technical issues: Value Strings that are in different places in the Model
(literals used as the object a RDF statement as opposed literals used to
annotate the object of an RDF statement with a label).  I want to keep the core
model, but simplify the structure somewhat.  We need to address mappings to the
evolving RDF standards.  Important question: Should DCAM revisions be kept
backwards compatible with the earlier DCAM?  Or do we have an opportunity to
create a simpler model that preserves the essence of the old model?  As one of
the original authors, having someone take a critical look at it with fresh eyes
would be helpful.  If we do not have more owners of the technical part (besides
me), the result may not be scrutinized the way it should be.  I'd some
co-editors -- people who will take a close look at the details.

Kai: I volunteer to help with the technical issues.  Start DCAM from scratch,
based on RDF?

Tom: OK with me.

ACTION: Kai and Tom to work on technical part in wiki, e.g.:
   http://wiki.dublincore.org/index.php/DCAM_Revision
    http://wiki.dublincore.org/index.php/DCAM_Revision_Scratchpad
    http://wiki.dublincore.org/index.php/DCAM_Revision_Graphics

Kai: How would we define these concepts with RDF?

Tom: See also "Son of DC" by Allistair Miles
http://aliman.googlecode.com/svn/trunk/sodc/SoDC-0.2/index.html.  Don't want to
start with constraint language (DC-DSP), that will come later.

Richard: We are in a different place than where we were when DCAM started. RDF
is more palatable today. RDF semantics are the way they are because of their
goals. Would it be helpful to bring these out in documentation? Some of the
push-back was about "additional complexity" - people wanting simple records.
Levels of interoperability. People may say: "I'll just stick with my simple
structures" (on Level 1). If purpose is to translate...

Michael: We share most of the same premises of RDF - that metadata is
description-based, description of something, and not just a set of key-value
pairs packed into a record. This also bridges, opens door to formal
knowledge-representation languages.  But people do not necessarily want to
represent their bibliographic data in RDF, RDFS, and OWL.

Tom: We need to get the general introductory stuff, information about
audiences, etc. up on the mailing list.  We will have a larger DCAM discussion
in the next three weeks.  Meeting adjourned.

--
Tom Baker <[log in to unmask]>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

February 2020
January 2020
December 2019
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