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  June 2003

DC-ARCHITECTURE June 2003

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: URI fragment IDs, MIME types and DCMI PURL redirects

From:

Roland Schwaenzl <[log in to unmask]>

Reply-To:

DCMI Architecture Group <[log in to unmask]>

Date:

Tue, 3 Jun 2003 15:39:04 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (120 lines)

> From [log in to unmask] Mon Jun  2 21:33 MET 2003
> X-RAL-MFrom: <[log in to unmask]>
> X-RAL-Connect: <pat.bath.ac.uk [138.38.32.2]>
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> Importance: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
> Date:         Mon, 2 Jun 2003 20:37:43 +0100
> From: Pete Johnston <[log in to unmask]>
> Subject: URI fragment IDs, MIME types and DCMI PURL redirects
> To: [log in to unmask]
>
> This question came up in an off list discussion, and I admit I find the
> area pretty confusing, so I'm not quite sure whether (a) my
> understanding is correct or (b) there's a problem here or not...
>
> DCMI uses PURLs for the URIs for all the DCMI terms, and issuing an HTTP
> GET of such a PURL generates a redirect by the OCLC resolver to a
> http://dublincore.org/... URI. Those dublincore.org URIs include
> fragment identifiers. So e.g.
>
> http://purl.org/dc/elements/1.1/title redirects to
> http://dublincore.org/2003/03/24/dces#title
>
> According to section 4.1 of http://www.ietf.org/rfc/rfc2396.txt
>
>    the optional fragment identifier, separated from
>    the URI by a crosshatch ("#") character, consists of additional
>    reference information to be interpreted by the user agent after the
>    retrieval action has been successfully completed.
>
> and
>
>    The semantics of a fragment identifier is a property of the data
>    resulting from a retrieval action, regardless of the type of URI used
>    in the reference.  Therefore, the format and interpretation of
>    fragment identifiers is dependent on the media type [RFC2046] of the
>    retrieval result.
>
> So, for example, RFC2854 http://www.ietf.org/rfc/rfc2854.txt
> specifies that for a document with MIME type text/html:
>
>    the fragment identifier
>    designates the correspondingly named element; any element may be
>    named with the "id" attribute, and A, APPLET, FRAME, IFRAME, IMG and
>    MAP elements may be named with a "name" attribute.
>
> For text/xml, RFC3023 http://www.ietf.org/rfc/rfc3023.txt says
>
>    As of today, no established specifications define identifiers for XML
>    media types.  However, a working draft published by W3C, namely "XML
>    Pointer Language (XPointer)", attempts to define fragment identifiers
>    for text/xml and application/xml.  The current specification for
>    XPointer is available at http://www.w3.org/TR/xptr

Some change happened here: XPTR in March 2003 was made W3C Recommendation.

>
> However, at present the document http://dublincore.org/2003/03/24/dces
> appears to be served with MIME type text/plain. I'm not clear whether
> fragment identifiers are defined at all for text/plain, but it doesn't
> seem like it?
>
> So is that a problem for using the redirect of
> http://dublincore.org/2003/03/24/dces#title ?

DCMI doesn't use fragments for it's vocabulary.

>
> The recent W3C RDF draft specs suggest the use of a MIME type
> application/rdf+xml



Fragments in RDF have to be interpreted in a way presuming (!) one had done a
retrieval on a gadget of MIME type application/rdf+xml.


>
> http://www.aaronsw.com/2002/rdf-mediatype.html
>
> This spec explicitly says rdf:ID and rdf:about attributes

can be used to define.

In the case at hand rdf:about isn't used that way.


> define
> fragments. The served document does have an attribute
> rdf:about="http://purl.org/dc/elements/1.1/title".
>
> But even if the document was served as application/rdf+xml, this doesn't
> quite seem to address the problem of what is designated by
> http://dublincore.org/2003/03/24/dces#title
>
> Does it actually matter?! I'm really not sure! If someone tells me
> authoritatively it doesn't, then I'll go away happy(ish)...(maybe!)

authoritively...who could...

>
> It just seems there _may_ be a problem somewhere there at the moment in
> that the use of the URIref http://dublincore.org/2003/03/24/dces#title
> doesn't seem to "fit" very well, either with a MIME type of text/plain
> (as at present) or of application/rdf+xml (as the recent specs suggest).


The document you get when de-referencing the RDF namespace URIreference is
also MIME typed text/plain.

rs


>
> Pete
>
>

Top of Message | Previous Page | Permalink

JISCMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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


WWW.JISCMAIL.AC.UK

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