Re: How to define <elements> in specifications

Hi Bjoern,

+1 to your proposal.


Le 18 juil. 2005, à 18:46, Bjoern Hoehrmann a écrit :
> Common information for an element would be which attributes it may 
> have,
> which attributes are required, the syntax for the attribute values,
> which elements may/must nest inside such an element and in which order,
> include schema fragments and if, which schema language(s), and so on.

That would help in many ways to have a common way of describing the 
things in the specification. It would help to extract information 
automatically, maybe to generate constraints for schemas, etc. or the 
opposite from schema to doc.

> an author trying to understand such a complex compound document format 
> is certainly not helped having to deal with a dozen of different ways 
> to describe conceptually very similar things.

Agreed :)

You mentionned Elements and attributes, do you limit your thoughts to 
XML languages?  It's a tricky thing. I'm trying to think about 
something which is a marker (not giving it the name of elements) in a 
language, etc.

* <Something> has <parameters> with <values>
* <Something> has <dependencies> with others <Something>
* <Something> has <semantic constraints>
* <Something> has <implementation constraints>


-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***

Received on Tuesday, 19 July 2005 15:24:57 UTC