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

Help for DC-REGISTRY Archives


DC-REGISTRY Archives

DC-REGISTRY Archives


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

DC-REGISTRY Home

DC-REGISTRY  August 2001

DC-REGISTRY August 2001

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Multilingual RDF schemas for DC (Was Re: Internationalization )

From:

Pete Johnston <[log in to unmask]>

Reply-To:

A mailing list for the group discussing registration of qualifiers to the D <[log in to unmask]>

Date:

Thu, 16 Aug 2001 15:04:05 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (96 lines)

I said:

> >But then
> >this means multiple RDF schema files associated with the same namespace.
> >Maybe this is unavoidable?

Eric said:

> I'm not sure I understand this... Namespaces are a syntactic
simplification
> for providing uniquely identified terms.  Having instance data (Schemas,
> examples, profiles, etc.) that "describe" different characteristics of
> these identified terms allows for a very flexible and efficient means for
> managing decentralized description.
>
> This is a feature, no?

Oh yes, I agree, and I understand your point made in the previous message
that all the descriptions of a uniquely identified term, however they may be
distributed in physical files in different physical locations, are all tied
together by the URI for the term they are describing - and it's _that_
relationship rather than the physical distribution of the descriptions which
EOR is working with.

I was making the point that in various exchanges (which were off this list),
my understanding - and this may be where I'm going wrong as I'm still fairly
new to this stuff...;-)  - was that we were arriving at a position where
there was a one-to-one correspondence between a namespace and an RDF Schema
representation which declared/defined the terms in that namespace. One
consequence of that one-to-one correspondence was that the namespace URI
_might_ serve as a "locator" for an RDF Schema instance describing the terms
in the namespace.

If multilingual support means managing the different language descriptions
of the terms in the namespace as physically separate (distributed,
decentralised) instances of RDF Schema (which it surely must), then there
are multiple RDF Schema instances describing the same namespace. From the
point of view which regards these schemas as metadata instances, this is
fine, and a perfect example of the usefulness of RDF in supporting
distributed metadata instances describing the same resources (in this case,
terms in the namespace).

However, _if_ the namespace URI is also (potentially at least) to act as a
_locator_, then it can only locate _one_ RDF Schema instance i.e. there is a
"primary" (for want of a better word!) instance to which the namespace URI
might serve as a locator, but there are other RDF Schema instances (the
translations of that primary instance) - which are all good, valid
descriptions of the namespace - which are _not_ located by the namespace
URI.

That was why I was returning to the "typology of schemas". Rather in the way
that "application profiles" can be seen as containing "annotations" of the
term definitions in namespace schema (or additional metadata about the terms
in the namespace schema), providing information about real world use of
those terms, so "translated namespace schema" might also be seen as
"annotations" of those "primary" term definitions?

This suggests "privileging" one language representation of the namespace
over another, but it seems that:

if a namespace URI potentially acts as a locator for an RDF Schema instance
declaring the terms in that namespace,

and if that RDF Schema instance contains
declarations/definitions/descriptions for terms in one language only,

then the namespace URI as locator can locate only a single language version
of the RDF Schema description of the namespace.

So.... I think where I'm going wrong is in the first of these propositions
i.e. expecting a namespace URI to act as a locator for an (exactly one) RDF
Schema instance.... :-(

But isn't this what is meant by appendix C2 of the RDF M&S spec? Especially

> In addition, the namespace name serves as the identifier for the
corresponding RDF schema. The
> namespace name is resolved to absolute form as specified by the algorithm
in Section 5.2., Resolving
> Relative References to Absolute Form, in [URI]. An RDF processor can
expect to use the schema URI
> to access the schema content.

I'm afraid the longer I pursue this, the more confused I get..... Any
clarification would be much appreciated!

Thanks!
Pete
-------
Pete Johnston
Interoperability Research Officer
UKOLN, University of Bath, Bath BA2 7AY, UK
tel: +44 (0)1225 323619    fax: +44 (0)1225 826838
mailto:[log in to unmask]
http://www.ukoln.ac.uk/ukoln/staff/p.johnston/

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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


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

For help and support help@jisc.ac.uk

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