This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2558 - entry point for schemas
Summary: entry point for schemas
Status: CLOSED FIXED
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: WorkingDraft
Hardware: All Linux
: P2 normal
Target Milestone: PublicationFebruar20
Assignee: Felix Sasaki
QA Contact: ITS mailing-list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-29 23:47 UTC by Sebastian Rahtz
Modified: 2006-07-21 17:45 UTC (History)
0 users

See Also:

Attachments

Description Sebastian Rahtz 2005-11-29 23:47:36 UTC 
The ITS tagset should probably NOT have an entry point,
as the Relax NG currently does. This makes the thing impossible
to merge into an existing schema. It would be better to define,
a new meta schema which imports the ITS schema, for making
standalone rule sets.
Comment 1 Felix Sasaki 2005-11-30 05:07:26 UTC 
(In reply to comment #0)
> The ITS tagset should probably NOT have an entry point,
> as the Relax NG currently does. This makes the thing impossible
> to merge into an existing schema. It would be better to define,
> a new meta schema which imports the ITS schema, for making
> standalone rule sets.

I think that is a good idea. Any other thoughts? I am just wondering how to
write an ODD document without an entry point. Regards, Felix.
Comment 2 Sebastian Rahtz 2005-12-06 10:12:22 UTC 
(In reply to comment #0)
> The ITS tagset should probably NOT have an entry point,
> as the Relax NG currently does. This makes the thing impossible
> to merge into an existing schema. It would be better to define,
> a new meta schema which imports the ITS schema, for making
> standalone rule sets.

You add start='' as an attribute to <schemaSpec>
Comment 3 Sebastian Rahtz 2005-12-06 11:43:52 UTC 
This should solve the problem