Some initial thoughts.
On 20/10/05, George Cristian Bina <[EMAIL PROTECTED]> wrote:
OK, major grouping helps. +1
> Elements
> Element: choice (name-class)
> Specifies a union of name-classes
> [name-class]+
An element - true
and a name-class.
Confusing? I don't know.
It's not a union though George - it's a choice,
one from n?
>
> Element: choice (pattern)
> List of valid pattern choices
> [pattern]+
'Stealing with glee' from Eric, how about
Element: choice (as a pattern)
> Element: define
> A named pattern, may specify combine as choice or interleave
> @name, @combine?, [pattern]+
I like the attribute notation... I wonder
if the XSLT notation is acceptable?
Especially when mixed with DTD notation! @combine? :-)
I guess that's just presentation though.
> Element: element (pattern)
> Matches elements
> (@name|[name-class]), [pattern]
That's messy.
Is that true?
Either @name OR name-class content model?
Mmm. Yep! Looks like it.
(I don't understand that one)
>
> Element: empty (pattern)
> Matches an empty node
> {empty}
>
> Element: except (name-class)
> Specifies a difference of name-classes
> [name-class]
Difference? I'd like to clarify that.. .or
perhaps simplify would be a better word.
>
> Element: except (pattern)
> Removes values(s) from a data pattern
> [pattern]
I like that description
> Element: grammar (pattern)
> Defines named patterns and the start pattern.
> (start | define | div | include)*
Much clearer definition.
> Element: include (pattern)
> Includes an external grammar and merges its definitions
> @href, (start | define | div)*
Syntax change?
I thought [ ] was the content model?
No... what semantics are you using [ ] for?
Mmm.
()
[]
{}
Need to resolve these, but that's a secondary.
> Element: name (name-class)
> Defines a name-class with a single name
> {QName}
This is an odd one. The only one with a QName content.
>
> Element: notAllowed (pattern)
> Always fails, provides abstract definitions that must be overwritten
> before use.
> {empty}
I don't like this description, but neither did I
like my own!
>
> Element: nsName (name-class)
> Any name in a namespace.
> except?
Syntax again? Should it be
{except?} or (except?)
> Element: optional (pattern)
> Contains optional patterns
> [pattern]+
>
> Element: param
> Specifies parameters constraining datatypes
> @name, #text
#text syntax?
>
> Content model definitions
> --------------------------------
> [[pattern]]
> (element | attribute | group | interleave | choice(as pattern) |
> optional | zeroOrMore | oneOrMore | list | mixed |
> ref | parentRef | empty | text | value | data |
> notAllowed | externalRef | grammar)
Yes, the 'choice(as pattern)' seems clear here.
> Global attributes - apply to all elements
> -------------------------------------------------
> Attribute: ns
> Defines the default namespace to be used for unqualified names.
>
> Attribute: datatypeLibrary
> A URI identifying the library of datatypes being used.
I like that.
> Hope that helps,
Getting there George. Getting there.
Thanks for that.
I'll do one along these lines
and post it to the list for comment
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
------------------------ Yahoo! Groups Sponsor --------------------~-->
Most low income households are not online. Help bridge the digital divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/2U_rlB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/rng-users/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
