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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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


Subject: Re: [dita] Issue: glossary.dtd does not conform to 1.2 specfilenaming rules


On 9/8/09 9:52 AM, "Ogden, Jeff" <jogden@ptc.com> wrote:

> Are the conventions all "SHOULD" rather than "MUST"?
> 
> Because there can be different doctype shells that use the same types
> and you should use different names for different shells, how can we have
> a convention that all the shells be named after the type?  We can choose
> to use the type name for one (perhaps the only one) that we include as
> an offici8al part of the specification, but we can't impose this as a
> requirement on others.

I don't understand your statement "you should use different names for
different shells".

How is that true? I *never* use different names for different shells--my
shells are organized into distinct plugins, so they can never occur in the
same directory.

I'm not saying it's *wrong* to give different shells different names, just
that it's not necessary as long as you are using PUBLIC identifiers to
resolve to specific shell files. In that case the system ID (filename) of
the shell is at best documentation and at worst noise.

That is, I make it a practice to ensure that system IDs for used in
documents shells *cannot* be resolved so that processors must correctly
resolve the public IDs or fail, because if the public IDs can't be resolved
it means there is a configuration problem somewhere that needs to be
resolved.

Cheers,

E.


----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email:  ekimber@reallysi.com <mailto:ekimber@reallysi.com>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
<http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com> 



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