Now everything looks Ok to me (except views - question is below); I guess we have to vote on this before implementing? I can start working on these changes once we have a consensus...
> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > > Vadim Gritsenko wrote: > > > Where expansion syntax is allowed? Possible places are: <snip/> > What about 'all attributes' in the default namespace of elements in the > sitemap namespace? It's Ok with me... Of course, substituting for some of attributes do not make much sense, but again, "all attributes" rule is much simpler then quite long list of substitute-enabled attributes. > > > For example, a 'content view' of a resource could return the XML > > > content > > > before transformations, or a 'schema view' could return a schema that > > > can be used to validate the content returned in the 'default view'. > > > The > > > 'semantic view' might return a resource description document, the > > > 'hyperlink view' might return the list of hyperlinks that start from > > > that resource, etc... > > > > > > Views describe terminating pipeline fragments and must not contain a > > > generator since it's the original pipe that performs as generator. > > > > I have a question on this one. Suppose you have quite expensive (cpu, > > memory, and non cacheable to top this) generator, and want to invoke > > schema view. Does it mean that this generator will be invoked? Even if > > schema of the resource could be as simple as static schema file? > > Same for link generator: you might want different generators > > to handle default and links views. Example: > > + Default view: > > <map:generate src="xmldb:dbxml:///db/document"/> > > + Links view: > > <map:generate > > src="xmldb:dbxml:///db/document#//*[@xlink:type='simple']/@xlink:href"/> > > (to give an idea...) > > Again, very good point, but the real question should be: is the above a > resource view or is another resource entirely? Don't know... If you have domain knowledge and you could implement link/schema/etc view much more efficient then using original generator (if views must use original generator) - what to do? In conjunction with Lucene search this could be quite huge performance improvement. > Of course I forgot to say that pipelines without direct components are > illegal. BTW, this is possible to check with XSLT. Some of the rules are hard to implement in XSLT, but some are quite easy (that's in connection with your other email). Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
