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  February 2010

DC-ARCHITECTURE February 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: DC-HTML and HTML5 - a clarification and position - *DRAFT*

From:

Thomas Baker <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Sun, 28 Feb 2010 11:55:36 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (187 lines)

Forwarding from Larry Masinter...

On Sat, Feb 27, 2010 at 09:35:35PM -0800, Larry Masinter wrote:
> Sender: Larry Masinter <[log in to unmask]>
> From: "Larry Masinter" <[log in to unmask]>
> To: "'Thomas Baker'" <[log in to unmask]>
> Cc: <[log in to unmask]>,
> 	<[log in to unmask]>,
> 	<[log in to unmask]>,
> 	"DCMI Architecture" <[log in to unmask]>
> Subject: RE: DC-HTML and HTML5 - a clarification and position - *DRAFT*
> Date: Sat, 27 Feb 2010 21:35:35 -0800
> Content-Type: text/plain;
> 	charset="us-ascii"
> X-Mailer: Microsoft Office Outlook 12.0
> 
> I know I initiated this request, but I'd like to see
> if I can make the request more specific:
> 
> If you're sending a comment to the HTML working group,
> I think it would be most productive to comment on the
> actual documents now being moved forward, including
> both Microdata and HTML+RDFa: 
> 
> http://www.w3.org/html/wg/
> 
> If you like them fine as they are, that's great,
> but probably also doesn't need a lot of discussion.
> 
> If there are some specific changes or technical issues
> you have with the document, then submitting that in
> terms of "what you think is wrong"  also be
> useful. 
> 
> A general kind of architectural review might be useful
> for the DCMI community, but the kind of general 
> statements below are going to get lost in the noise.
> 
> Thanks,
> 
> Larry
> --
> http://larry.masinter.net
> 
> 
> 
> -----Original Message-----
> From: Thomas Baker [mailto:[log in to unmask]] On Behalf Of
> Thomas Baker
> Sent: Friday, February 26, 2010 8:58 AM
> To: DCMI Architecture
> Cc: [log in to unmask]; Larry Masinter; [log in to unmask];
> [log in to unmask]
> Subject: DC-HTML and HTML5 - a clarification and position - *DRAFT*
> 
> Dear all,
> 
> The W3C HTML Working Group is developing a new version of HTML,
> and proposals are on the table with implications for whether
> DCMI would be able to apply solutions it has promoted for use
> with HTML4 and XHTML in a new HTML5 environment [1].
> 
> The following statement, which puts DCMI's HTML-related work
> into an historical context and articulates a position on the
> issues as we currently understand them, is signed by the authors
> of DCMI's current HTML-related specifications and by the
> co-moderators of the DCMI Architecture Forum.
> 
> I am posting this message now to dc-architecture in order to
> invite a close reading by interested members of this forum and
> would particularly appreciate quick feedback if anyone spots
> errors of fact.
> 
> Discussion of this issue has recently come thick and fast, with
> new developments and contributions not only on the mailing list
> of the W3C HTML working group [2,3], but also the mailing lists
> of the W3C Linking Open Data project [4,5,6,7] many of which
> have been Cc'd to the mailing list of the W3C Semantic Web
> Interest Group [e.g., 8].
> 
> Unless anyone raises red flags, I plan to submit this post early
> next week to all of the relevant mailing lists.  Recipients Cc'd
> to this message are invited to join the dc-architecture list [9]
> if they wish to respond to the dc-architecture group as a whole.
> 
> Many thanks,
> Tom Baker
> 
> [1] http://lists.w3.org/Archives/Public/public-html/2010Jan/0573.html 
> [2] http://lists.w3.org/Archives/Public/public-html/2010Feb/0683.html
> [3] http://lists.w3.org/Archives/Public/public-html/2010Feb/0794.html
> [4] http://lists.w3.org/Archives/Public/public-lod/2010Feb/0207.html
> [5] http://lists.w3.org/Archives/Public/public-lod/2010Feb/0215.html
> [6] http://lists.w3.org/Archives/Public/public-lod/2010Feb/0218.html
> [7] http://lists.w3.org/Archives/Public/public-lod/2010Feb/0220.html
> [8] http://lists.w3.org/Archives/Public/semantic-web/2010Feb/0214.html
> [9] http://www.jiscmail.ac.uk/lists/dc-architecture.html
> 
> --------------------
> [Text to be posted:]
> 
> Over the years, DCMI has developed several specifications
> of relevance to the discussions around HTML5:
> --  RFC 2731 of 1999 ("Encoding Dublin Core Metadata in HTML") [1],
>     now obsoleted by RFC 5791 ("RFC 2731 Is Obsolete") of 2010 [2].
> --  "Expressing Dublin Core in HTML/XHTML meta and link elements" of
> 2003 [3],
>     currently a "superseded recommended" as explained in [4].
> --  "Expressing Dublin Core metadata using HTML/XHTML meta and link
>     elements" (a.k.a. DC-HTML) of 2008 [5], currently a DCMI
> Recommendation.
> 
> The 2008 DC-HTML Recommendation makes use of the XHTML meta data
> profile, which is associated with a Profile Transformation as
> defined by GRDDL.
> 
> DCMI acknowledges that all technology is transitional, and that,
> in particular, syntax for embedding metadata in HTML is likely
> to evolve significantly over the next few years.
> 
> The intention of DCMI is to help metadata implementers use
> metadata effectively in the Web environment.  While
> DCMI-specific solutions have been developed over the years to
> meet pressing needs, DCMI's intention is not to promote
> syntactic solutions that are specific to "Dublin Core", but
> rather to enable the use of Dublin Core terms in metadata that
> draws on other compatible namespaces, such as FOAF, in the
> context of application profiles.
> 
> Increasingly, such syntax solutions are being developed outside
> of DCMI. Since the finalization of RDFa as a W3C Recommendation
> in 2008, DCMI also promotes RDFa for use in "Dublin Core"
> metadata as an alternative to DC-HTML/2008.
> 
> In this spirit, DCMI does not consider itself to be committed
> to the profile attribute in a way that would preclude migration
> to alternative mechanisms in HTML5.  DCMI is open to any forms of
> markup that will meet the needs of the Dublin Core community.
> 
> In our understanding, the need of the Dublin Core community is
> for a mechanism to encode RDF triples using <meta> and <link>
> elements which:
> 
> -- supports both literal and URI objects 
> -- includes an abbreviation mechanism for property URIs, not
>    just for property URIs owned by DCMI, but for property URIs
>    generally.
> 
> The 2008 DC-HTML specification provides such a mechanism.  RDFa
> provides such a mechanism through CURIEs.  If RDFa were
> available in HTML5, DCMI would therefore be happy to promote its
> use with HTML5.
> 
> If the new microdata proposal were to provide a mechanism for
> achieving the same effect, then DCMI would be happy to promote
> its use as well.  Based on an imperfect understanding of the
> proposal on the table, DCMI does have some concern that
> requiring the use of full URIs for qualifying the provenance of
> properties sets a high bar for implementers, who could resort to
> pragmatic solutions that would depend on out-of-band information
> or other forms of "context" to relate the properties used
> specifically to DCMI metadata terms and could therefore, in
> practice, introduce ambiguity about the precise terms referenced.
> 
> DCMI is interested in promoting any generic, standards-based
> solutions which ensure that its properties are precisely
> identified and can be referenced and used without ambiguity.
> 
> Best regards,
> 
> Tom Baker (CIO of DCMI), Pete Johnston, Mikael Nilsson, Andy Powell
> on behalf of DCMI
> 
> [1] http://tools.ietf.org/html/rfc2731
> [2] http://tools.ietf.org/html/rfc5791
> [3] http://dublincore.org/documents/dcq-html/
> [4] http://dublincore.org/documents/dc-html-notes/
> [5] http://dublincore.org/documents/dc-html/
> [6] http://dublincore.org/documents/dc-ds-xml/
> 
> -- 
> Thomas Baker <[log in to unmask]>
> 

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

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