OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [relax-ng] Agenda for RELAX NG telcon 20 June 2002


> -----Original Message-----
> From: James Clark [mailto:jjc@jclark.com]
> Sent: Tuesday, June 18, 2002 7:07 PM
> To: relax-ng@lists.oasis-open.org
> Subject: [relax-ng] Agenda for RELAX NG telcon 20 June 2002
>
> Compact syntax
>
> 1. Should "externalRef" keyword be renamed to "external"?

Yes, fine.

> 2. Should "notAllowed" keyword be changed so as to avoid mixed case
> keywords?

Why not use ! as Mr. Cowan suggests.

> 3. Does anybody prefer "()" as used by XQuery instead of  the "empty"
> keyword?

Again, I like empty.

> 4. Should we allow
>
>   attribute foo { }
>
> as a shorthand for
>
>   attribute foo { text }
>
> ?

I like this because it provides a direct analogue to <attribute
name="foo"/>.

> 5. Should we make quotes on parameter values optional when the
> value is an NMTOKEN
>
> xs:string { minLength = 1 }
>
> ?

Hmmm. Hmmmmmmm.

> 6. Should we introduce an alternative string literal syntax that
> works well
> for strings that may contain multiple " and ' characters?  The leading
> contender is Python-style triple-quoted strings.

Sure.

> 7. Should we provide an alternative syntax for an annotation element that
> occurs as the first child of a RELAX NG element but is not
> semantically an
> annotation on that parent element?  Kawaguchi-san gave as an example:
>
> <element name="foo">
>   <cc:java>code();</cc:java>
>   <empty/>
> </element>

This seems like a good idea. By convention or by specification? If by spec,
where will this be specified? Should there be a (brief/modular) spec
describing RelaxNGCC support?

Since we use

## The foo element is empty.

in compact syntax for <a:documentation>, could we use

// code();

for RelaxNGCC annotations in the compact syntax as well?

> 8. What should the conformance clause say?

I agree that we shouldn't mandate too many cosmetics for annotations. John's
statement seems to be a good start. See
http://lists.oasis-open.org/archives/relax-ng/200206/msg00025.html

> James
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC