logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

RE: Document/schema association proposal: msg#00065

Subject: RE: Document/schema association proposal
On Mon, 2003-10-20 at 15:23, david.pawson@xxxxxxxxxxx wrote:
> JC:
> > Here's what I'm planning to implement:
> > 
> > - locate.html is a draft of the documentation converted to HTML
> >Comments welcome.
> 
> "The variable rng-schema-locating-files specifies the list of schema
> locating files that nXML mode should use. It is not an error if some of the
> files do not exist. "
> 
> Could be confusing to the user James? If it picks up on a later schema 'in
> error'
> (as far as the user is concerned?)
>  How about a warning message, even if you do ignore it?

I guess it's only the relative file-name case where it's necessary to
allow the file not to exist.  Typically, this variable would contain
something like

 ("schemas.xml" "/home/jjc/schema/schemas.xml"
"/usr/share/schema/schemas.xml")

which means to use a "schemas.xml" file in the document's directory if
such a file exists, before the standard directories.  Lots of the time
the document's directory won't have such a file, so you really don't
want an error in that case.


> "The variable rng-schema-locating-files specifies the list of schema
> locating files that nXML mode should use."
> 
> Syntax please.

What's wrong with the syntax: "variable ... specifies the list"?

>  Assume this list is used sequentially? Any reporting if file
> n not found?
> (same logic as above).

It's talking about the same thing as the first paragraph.  I'll merge
the first two paragraphs.

> "You can use the command C-c C-s to manually select the schema for the
> document in current buffer. Emacs will read the file-name of the schema from
> the minibuffer. After reading the file-name, Emacs will ask whether you wish
> to add a rule to a schema locating file that persistently associates the
> document with the selected schema. "
> 
> If I have a list of 4 files, which one will be added to?

I think the first one on the list, or maybe the first existing one.

> "This says to use the schema xhtml.rnc for a document with namespace
> http://www.w3.org/1999/xhtml, and to use the schema docbook.rnc for a
> document whose local name is book. If the document element had both a
> namespace URI of http://www.w3.org/1999/xhtml and a local name of book, then
> the schema xhtml.rnc would be used. "
> 
> Is this due to ns taking precedence over documentElements, or the fact that
> the
> ns association was first in the file?

The latter.  I'll say so explicitly.

> 
> "A uri rule locates a schema based on the URI of the document. The resource
> attribute locates a schema for a particular resource. For example, 
> 
>      <uri resource="spec.xml" uri="docbook.rnc"/>
> "
> 
> Should that be 'the resource attribute specifies the xml document instance'?
> or 'the uri rule locates a schema'?

Yes.

> "If there is a pathAppend attribute, then the URI is transformed by
> appending the specified string to the URI's path component. "
>   No example provided James, as with all the others?

I'll add one.

> 
> 
> "  <documentElement prefix="xsl" localName="stylesheet" uri="xslt.rnc"/>"
> 
> Is this a case of first come first served? Ie first in the file takes
> precedence
> if the <namespace ns="" is also used in the same file?

Yes. Everything always first come, first served.  I'll emphasive that.

> 
> "Specifying a default schema"
> 
> I like that one!
> 
> 
> "declares three type identifiers XHTML "  
> (Only two listed)

1. XHTML
2. XHTML Strict
3. XHTML Transitional

> ? Do the typeId/@od element and typeId attribute have to be an exact string
> match?

Like xsd:token.  Strip leading and trailing whitespace; other strings of
whitespace normalized to a single character.

> "a document that started 
> 
>      <?my-doctype XHTML Transitional?>
> "
> 
> Isn't the pi target restricted to name? (production 5, xml) which could
> impact
> back on typeId?

The pi target is "my-doctype", which is a name.

> 
> "     <include rules="../rules.xml"/>"
> Any thought given to import class of use, so that an override would take
> place,
> or should we just use the first come first served idea to obtain precedence?

Hmm. I think it's enough to do applyFollowingRules for include, but
maybe an optional ruleType attribute on include would be useful. 
Something to think about.

James



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Rent DVDs from home.
Over 14,500 titles. Free Shipping
& No Late Fees. Try Netflix for FREE!
http://us.click.yahoo.com/mk9osC/hP.FAA/3jkFAA/2U_rlB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
emacs-nxml-mode-unsubscribe@xxxxxxxxxxxxxxx

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 





<Prev in Thread] Current Thread [Next in Thread>