sitemap-v06.rng

["Carmona Perez, David" <DP...@fcc.es>]

Hi all,

I propose to change the RelaxNG validation file sitemap-v06.rng in this way:
Component declaration like <map:generator>, <map:transformer>, <map:serializer>, and similars would need to be:

	<define name="map.generator">
		<element name="map:generator">
			<ref name="map.generator.attlist"/>
			<ref name="component.config"/>
		</element>
	</define>

where component.config is defined as

	<define name="component.config">
		<zeroOrMore>
			<element>
				<anyName>
					<except>
						<nsName ns="http://apache.org/cocoon/sitemap/1.0"/>
					</except>
				</anyName>
				<zeroOrMore>
					<attribute>
						<anyName>
							<except>
								<nsName ns="http://apache.org/cocoon/sitemap/1.0"/>
							</except>
						</anyName>
					</attribute>
				</zeroOrMore>
				<choice>
					<ref name="config"/>
					<text/>
				</choice>
			</element>
		</zeroOrMore>
	</define>

That is, to allow any configuration content.  If we make it too restrictive, what about custom components setup?.

What do you think about this?

David

*************************************************************
Este correo ha sido procesado por el Antivirus del Grupo FCC.
*************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: sitemap-v06.rng

[David Crossley <cr...@apache.org>]

Martin Holz wrote:
> I use sitemap-v06.rng for editing the sitemap with oxygen and I like
> it to be very restrictive. So I do not always have to look into the docu
> to see how a configuration looks exactly. I do change the sitemap
> quite often but do not write new components very often, especially
> compontents which need additional configuration elements. 
> Adapting sitemap-v06.rng once in a while is a low price for good
> sitemap editing support.

Perhaps we could have two schema:
 sitemap-strict.rng
 sitemap-lax.rng

With the "lax" one, we could implement David's idea to be not so strict.

With the "strict" one we could keep adding to it so that it defines
everything that is allowable. This helps with automated editor prompts
and so is a type of sitemap documentation.

I recently re-added the build target "validate-sitemaps". Running it
against today's CVS still shows many things missing (you may need to
edit tools/targets/validate-build.xml to include more sitemaps).

The trouble with the "strict" one is the maintenance. We don't see
many people helping out with improving it and keeping it up-to-date.
It would be an excellent resource if we did.

It is great to hear that the various xml editors are providing support
for RELAX NG.

--David



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: sitemap-v06.rng

[Martin Holz <ho...@fiz-chemie.de>]

Hi,

"Carmona Perez, David" <DP...@fcc.es> writes:

> I propose to change the RelaxNG validation file sitemap-v06.rng in this way:
> Component declaration like <map:generator>, <map:transformer>, <map:serializer>, and similars would need to be:
[Snipped concrete implementation]
> That is, to allow any configuration content.  If we make it too restrictive, what about custom components setup?.

I use sitemap-v06.rng for editing the sitemap with oxygen and I like
it to be very restrictive. So I do not always have to look into the docu
to see how a configuration looks exactly. I do change the sitemap
quite often but do not write new components very often, especially
compontents which need additional configuration elements. 
Adapting sitemap-v06.rng once in a while is a low price for good
sitemap editing support.


Martin


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org