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

Help for DC-INTERNATIONAL Archives


DC-INTERNATIONAL Archives

DC-INTERNATIONAL Archives


DC-INTERNATIONAL@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-INTERNATIONAL Home

DC-INTERNATIONAL Home

DC-INTERNATIONAL  June 2002

DC-INTERNATIONAL June 2002

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Provenance

From:

Thomas Baker <[log in to unmask]>

Reply-To:

Thomas Baker <[log in to unmask]>

Date:

Thu, 6 Jun 2002 07:22:52 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (187 lines)

Dear all,

Harry made an important posting about the RDF modelling of
translations of element labels and definitions in German and
other languages. He made the posting in three different groups,
so I was uncertain where to reply; I ended up posting in
dc-architecture because it has alot to do with encoding issues,
but obviously the issues also relate to the Registry and to
Internationalization/Localization (see attached posting).

Readers of dc-international will be especially interested in
the issues described below.

Rather than continue to cross-post (which is strongly
discouraged), I suggest we continue the discussion in
dc-architecture.

Tom

On Thu, Jun 06, 2002 at 07:14:25AM +0200, Thomas Baker wrote:
> Date:         Thu, 6 Jun 2002 07:14:25 +0200
> From: Thomas Baker <[log in to unmask]>
> Subject:      Re: Provenance
> To: [log in to unmask]
>
> > I can see how, given this model, I can (programmatically) get from dc:title
> > to the resources described in "#deDE_1" and "#deDE_2" (by looking for an
> > rdf:Statement with an rdf:Subject of dc:title), but how would a program get
> > from dc:title to the resource described in "#deDE_0"?
>
> Harry, Roland, (attn: Shigeo and Eric),
>
> This discussion touches on a crucial feature of RDF --
> the ability to overlay annotations, in this case translated
> labels and definitions.  It moves us further towards goals
> that were recognized and discussed at a series of meetings
> of the Working Group for DC in Multiple Languages in 1997
> and 1998 (see [1] and [2]).  In this somewhat long posting,
> I lay out two requirements that may not be addressed by the
> current approach, but could be.  These are summarized as two
> questions at the end.
>
> The position paper of mid-1998 [1] recognized that "versions"
> (preferred over "translations" at the time) of Dublin Core
> elements in various languages should share a single namespace
> (Point 4) and proposed a now-outdated RDF encoding of the
> Title element in French (Point 6).  Importantly, the paper
> also suggested that: "Versions of the Dublin Core in other
> languages should cite the specific English version on which
> they are based (eg, 1.0, 1.1, 2.0...), as that canonical
> version will evolve over time".  Shigeo, his colleagues at
> ULIS, and I explored the implications of versioning in a
> paper early last year [3].
>
> In that paper, we proposed some general requirements with
> regard to versioning translations (Section 4):
>
> -- that for long-term access to legacy metadata as well as
>    for the needs of software developers it should be possible
>    to reconstruct the exact labels and definitions in use at
>    a particular point in time (Points 1 and 3);
>
> -- that the set of terms should grow incrementally, not by
>    infrequent, numbered releases such as "Dublin Core 2.0"
>    (Point 5) -- the paper summarizes discussion of this issue
>    in DC-AC in 1999 (Section 5);
>
> -- that namespace URIs remain stable through successive
>    versions (Points 2 and 4), which is now addressed by
>    the DCMI Namespace Policy;
>
> -- and, importantly, that the translation of a term into
>    Japanese needs to reference a unique identifier for the
>    specific historical version translated (Points 6 and 7).
>    This requirement emerged from our sense that inevitably,
>    translations would lag somewhat behind the "canonical"
>    English version, even if the resulting differences of
>    wording were to have no significant impact on applications
>    (see the DCMI Namespace Policy).
>
> This need to uniquely identify a historical version of a term
> is roughly "prototyped" in the new Usage Board document -- for
> example, consider the two historical versions of "dc:title":
>
>     VMS-ID:        title-002
>     URI:           http://purl.org/dc/elements/1.1/title
>                    [-- Label, Definition, etc of dc:title, DCMES 1.1 --]
>     Replaces:      http://dublincore.org/usage/terms/dc/#title-001
>
>     VMS-ID:        title-001
>     URI:           http://purl.org/dc/elements/1.1/title
>                    [-- Label, Definition, etc of dc:title, DCMES 1.0 --]
>     isReplacedBy:  http://dublincore.org/usage/terms/dc/#title-002
>
> .. where the state of the Title term in DCES 1.0 is
> (prototypically, at least) "uniquely identified" as "title-001"
> -- for example, try clicking on the mirrored document at
> http://www.gmd.de/People/Thomas.Baker/usage/terms/dc/#title-001.
>
> With these issues in mind, I have two questions about the
> proposed RDF syntax below:
>
> 1) Could "translation annotations" of this form in principle
>    be distributed over -- and harvested from -- multiple
>    Web sites?  The whole thrust of the 1997-1999 discussion
>    was that German translations would be maintained by
>    German-speaking organizations.  The alternative -- that
>    DCMI would hold and maintain all translations centrally --
>    seemed then and still seem both impractical and politically
>    undesirable.
>
> 2) Could an RDF statement be added to point to the uniquely
>    identified historical version of an element?  For example,
>    could a translation of "dc:language" point to the DCES 1.0
>    version at http://dublincore.org/usage/terms/dc/#language-001
>    (or an equivalent).
>
> Tom
>
> [1] http://dublincore.org/groups/languages/mr-19980525.shtml
> [2] http://dublincore.org/groups/languages/
> [3] http://avalon.ulis.ac.jp/~sugimoto/RPs/saint.pdf
>
> On Wed, Jun 05, 2002 at 04:25:35PM -0400, Harry Wagner wrote:
> > > > <!-- Begin: Title Declaration -->
> > > > <rdf:Property rdf:about = "&dcns;title"/>
> > > >
> > > > <rdf:Description rdf:about = "&dcns;title" bagID="deDe_0">
> > > >   <rdfs:label rdf:ID="deDE_1" xml:lang="de-DE">Titel</rdfs:label>
> > > >   <rdfs:comment rdf:ID="deDE_2" xml:lang="de-DE">Titel der
> > > > Quelle; der vom Verfasser, Urheber oder Verleger vergebene
> > > >   Namen der Ressource</rdfs:comment>
> > > > </rdf:Description>
> > > >
> > > > <rdf:Description rdf:about="#deDe_0">
> > > >         <dc:description xml:lang="de-DE">
> > > >           Sprachabhaengiger Teil der Deklaration eines
> > > >           DC-Terms in Deutsch.
> > > >         </dc:description>
> > > >         <dc:description xml:lang="en-US">
> > > >           Language dependent part of the deklaration of a DC
> > > >           Term in German.
> > > >         </dc:description>
> > > >         <dc:publisher>DCMI</dc:publisher>
> > > >         <dc:source rdf:resource="http://www.dublincore.org/documents/dces"/>
> > > > </rdf:Description>
> > > >
> > > > <rdf:Description rdf:about="#deDE_1">
> > > >         <dc:creator>Diann</dc:creator>
> > > >         <dc:description xml:lang="de-DE">Zuordnung eines
> > > >          deutschen Labels zu einem DC Term</dc:description>
> > > >         <dc:description xml:lang="en-US">Association of a
> > > >           German label to a DC term</dc:description>
> > > >         <dc:publisher>DCMI</dc:publisher>
> > > >         <dc:rights xml:lang="de-DE">
> > > >           Die publizierende Organisation uebernimmt keine
> > > > Gewaehr fuer die Richtigkeit der Zuordnung des deutschen Ausdrucks.
> > > >         </dc:rights>
> > > >         <dc:rights xml:lang="en-US">The publisher disclaims
> > > >          any responsibility for the correctnes of the association
> > > >          of the German expression.
> > > >         </dc:rights>
> > > > </rdf:Description>
> > > >
> > > > <rdf:Description rdf:about="#deDE_2">
> > > >         <dc:creator>Walter</dc:creator>
> > > >         <dc:description xml:lang="de-DE">Zuordnung eines deutschen
> > > >          RDFS Kommentars zu einem DC Term</dc:description>
> > > >         <dc:description xml:lang="en-US">Association of a
> > > >           German RDFS comment to a DC term</dc:description>
> > > >         <dc:publisher>DCMI</dc:publisher>
> > > >         <dc:rights xml:lang="de-DE">
> > > >           Die publizierende Organisation uebernimmt keine
> > > >           Gewaehr fuer die Richtigkeit der Zuordnung des deutschen Ausdrucks.
> > > >         </dc:rights>
> > > >         <dc:rights xml:lang="en-US">The publisher disclaims
> > > >           any responsibility for the correctnes of the association
> > > >           of the German expression.
> > > >         </dc:rights>
> > > > </rdf:Description>

--
Dr. Thomas Baker                                [log in to unmask]
Institutszentrum Schloss Birlinghoven          mobile +49-171-408-5784
Fraunhofer-Gesellschaft                          work +49-30-8109-9027
53754 Sankt Augustin, Germany                     fax +49-2241-14-2619

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2012
March 2012
February 2012
November 2011
September 2011
May 2011
December 2010
October 2010
September 2010
February 2010
January 2010
October 2009
September 2009
August 2009
July 2009
February 2009
August 2008
October 2007
August 2007
July 2007
May 2007
February 2007
October 2006
August 2006
June 2006
April 2006
September 2005
August 2005
July 2005
June 2005
May 2005
January 2005
December 2004
November 2004
October 2004
September 2004
July 2004
June 2004
November 2003
October 2003
September 2003
June 2003
May 2003
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
October 2001
January 2001
December 2000
November 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
January 2000
November 1999
October 1999
September 1999
July 1999
June 1999
May 1999
February 1999
January 1999
November 1998
October 1998
September 1998
July 1998
June 1998
January 1998


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