You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by "Gregor J. Rothfuss" <gr...@apache.org> on 2005/04/26 14:25:56 UTC
Re: How the editor get's a schema
Torsten Schlabach wrote:
>>Is there a generic
>>description for document structure definitions? IIRC Gregor mentioned
>>something like that recently.
it's called JARV
http://issues.apache.org/bugzilla/show_bug.cgi?id=33587
a common API for document validation which we should use for all
situations where we validate.
> If that's the case please post it again.
>
> I am not happy at all with the current implementation for several reasons:
>
> - I was thinking of maybe converting between structure definitions on demand
> - I don't like files as well. I would envision more of an intelligent
> structure defintions registry.
> - etc.
>
> At this point in time I needed the method because I am still working on
> BXE 2.0 integration and I wanted to establish a clear contract how an
> editor fetches the schema definiton from the API. My idea was that the API
> could be changed (enhanced) at any time later on.
BXE calls that URL to get a stream of the schema, so maybe we might just
return the schema as a byte stream?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: How the editor get's a schema
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Torsten Schlabach wrote:
>>>it's called JARV
> But IIUC in the case of BXE it would be BXE that would have to be changed
> to use this, not Lenya. But it might come in handy in places where it is
> left to Lenya to validate a document.
>
> But in BXE (and probably also for other editors) the role of the schema is
> not only to validate but also to instruct the editor on possible moves,
> i.e. what elements are valid as children of a given element, for example.
right. which is why i think we need both JARV validation and a facility
to return a schema
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: How the editor get's a schema
Posted by Torsten Schlabach <ts...@apache.org>.
>> it's called JARV
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=33587
>> a common API for document validation which we should use for all
>> situations where we validate.
Thanks for the reference.
But IIUC in the case of BXE it would be BXE that would have to be changed
to use this, not Lenya. But it might come in handy in places where it is
left to Lenya to validate a document.
But in BXE (and probably also for other editors) the role of the schema is
not only to validate but also to instruct the editor on possible moves,
i.e. what elements are valid as children of a given element, for example.
Regards,
Torsten
> Torsten Schlabach wrote:
>
>>>Is there a generic
>>>description for document structure definitions? IIRC Gregor mentioned
>>>something like that recently.
>
> it's called JARV
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=33587
>
> a common API for document validation which we should use for all
> situations where we validate.
>
>> If that's the case please post it again.
>>
>> I am not happy at all with the current implementation for several
>> reasons:
>>
>> - I was thinking of maybe converting between structure definitions on
>> demand
>> - I don't like files as well. I would envision more of an intelligent
>> structure defintions registry.
>> - etc.
>>
>> At this point in time I needed the method because I am still working on
>> BXE 2.0 integration and I wanted to establish a clear contract how an
>> editor fetches the schema definiton from the API. My idea was that the
>> API
>> could be changed (enhanced) at any time later on.
>
> BXE calls that URL to get a stream of the schema, so maybe we might just
> return the schema as a byte stream?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org