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  August 2007

DC-ARCHITECTURE August 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Draft of revised version of Expressing DC in X/HTML meta/link elements

From:

Pete Johnston <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Thu, 16 Aug 2007 11:32:35 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

Mikael said:

[snip]

> My gut feeling is that these are a bit too much at the moment. I'd
> prioritize updating the current DC-in-HTML spec to be DCAM-compatible.
> It seems to me that this also makes most existing DC-in-HTML metadata
> more or less compatible?

I think so. 

The main issue where there is an "incompatibility", I think, is the use
of the meta/@scheme attribute. The new draft specifies that meta
elements map to statements with literal value surrogates, and that
values of @scheme map to SES URIs, whereas in the past @scheme has been
used for both VES and SES URIs. 

So I think "naively" applying the "new" interpretation to documents
encoded using the "old" spec will result in some statements with
strangely typed literals as literal value surrogates.
   
> Later on, we can simply describe how to use RDFa together with DC-RDF,
> and slowly deprecate DC-in-HTML completely. 

Sounds good to me.

> The above assumes that the issue of knowing when to trigger DC-in-HTML
> parsing and when to trigger RDFa is solved.

Yes.

> But it seems to me that this is not a big issue, right?

I think it's a "moderately sized" issue ;-) But I think it's an issue
that RDFa has to address in the general case if it is to avoid the
generation of lots of unwanted triples e.g. I think the problem I
highlighted for the DCMI profile applies equally to all uses of Ian D's
Embedded RDF profile too. Also specs like OpenId make use of a "prefixed
name" convention in link/@rel attribute values without explicitlt
associating that convention with a mapping to property URIs. 

So it seems to me all this "legacy data" is something RDFa has to
handle, one way or another, and it is in the first instance an issue for
the RDFa group rather than for DCMI. (Though having said that, if we can
make any minor adjustments to smooth their path, then I'd like us to
take such suggestions under consideration.)

> So, to summarize, I propose to
> 
> 1. Keep DC-in-HTML, but update to be DCAM-compatible
> 2. Create DC-using-RDFa at a later stage, and make it 
> preferred over (1) over time.

I'm happy with that approach.
 
> > We may still want to consider changing the separator in 
> what I called
> > "DC-HTML Prefixed Names" from a period to a colon? I'm not 
> sure whether
> > that would be a good thing to do or not: given that they 
> aren't QNames
> > and the prefixes won't be mapped to XML Namespace Names, it may be
> > confusing to make that change.
> 
> Plus it would leave existing data in the dark.

Yes, agreed. Though note that the draft also proposes a new profile URI,
so I guess strictly speaking data with the current profile URI remains
in the dark, in the sense that the existng profile specifies no DCAM
interpretation.

> If we are to keep
> DC-in-HTML as a non-RDFa solution, I think it's better to 
> keep it close to the old specs.

Yes, that was very much the approach I had taken in creating the current
draft. I'm quite happy to keep the period-separated prefixed names (and
indeed would prefer to do so, not only for the backward compatibility
reasons, but also on the grounds that I fear that adopting names which
look rather like XML QNames but which aren't processed as XML QNames
will inevitably lead to some confusion).
 
Pete

---
Pete Johnston
Technical Researcher, Eduserv Foundation
Web: http://www.eduserv.org.uk/foundation/people/petejohnston/
Weblog: http://efoundations.typepad.com/efoundations/
Email: [log in to unmask] 
Tel: +44 (0)1225 474323

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

February 2024
January 2024
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
September 2022
August 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
November 2021
October 2021
September 2021
August 2021
July 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
April 2020
March 2020
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

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