W3C home > Mailing lists > Public > public-html@w3.org > November 2007

RE: ISSUE-4 (html-versioning): HTML Versioning and DOCTYPEs [HTML Principles/Requirements]

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Tue, 6 Nov 2007 19:04:38 +0100
Message-ID: <78BEBE845AB46D4789206C4DBB3A969C93002E@obeex01.obe.access-company.com>
To: "Karl Dubost" <karl@w3.org>
Cc: "Dan Connolly" <connolly@w3.org>, "HTML Issue Tracking WG" <public-html@w3.org>
Version seems to be important for backward compatibility, profiling for feature management and definition of products. Profiling is one of the steps to define the intention of the particular content that is based on large feature-set of the "full" profile/content.



From: Karl Dubost [mailto:karl@w3.org] 
Sent: Tuesday, November 06, 2007 6:30 PM
To: Marcin Hanclik
Cc: Dan Connolly; HTML Issue Tracking WG
Subject: Re: ISSUE-4 (html-versioning): HTML Versioning and DOCTYPEs [HTML Principles/Requirements]



Le 6 nov. 2007 à 12:17, Marcin Hanclik a écrit :

	Versioning and profiling seems to be the common issue throughout WGs.
	Would it be possible to have one mechanism for all those specs?


The issue is more around what each class of products do with a version number.

* Do they need it?

* if yes, how do they use it?

* when not using it what are the challenges?


For Class of products, I'm talking about


* authoring tools (standalone applications)


* converters

* custom search engines

* web search services 

* document analyzers

* browsers

* validators

* other markup languages using the language (example atom see below)




<title type="xhtml">

  <div xmlns="http://www.w3.org/1999/xhtml">

    HTML and its <strong>versioning</strong>!








Karl Dubost - W3C


Be Strict To Be Cool


Received on Tuesday, 6 November 2007 18:05:34 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:28 UTC