Re: Request for Dependency Resolution or Review

At 16:07 1999 09 17 -0400, Joseph M. Reagle Jr. wrote:
>[1] http://www.w3.org/Signature/Group/dependencies.html

>   We are soliciting a commitment to resolve a dependency (by having it
>   addressed it in a spec or RD) and/or a commitment to review the XML

>   XML Package (forthcoming)

Since this was addressed to me (I assume in my capacity as proposed 
co-chair of the forthcoming XML Packaging WG), I feel compelled to 
respond, but it is unclear what I should say.

You are soliciting a commitment, but you don't suggest a timeframe for
response.  Specifically, I don't know how to make any commitment in
the name of a WG that doesn't yet exist and doesn't expect to exist
for perhaps many months.  Is is acceptable that you wait for any
response to your request for commitment until the WG exists, or do 
you have a different suggestion?

Also, after a quick read of your message and the referenced requirements
document, I don't (personally--but of course I can't speak for whoever
turns out to be a future member of the forthcoming XML Packaging WG)
understand most of what you've written.  Maybe this indicates that I
shouldn't be co-chair of the XML Packaging WG!  But whenever it becomes
time to consider the dependencies you list, someone will have to explain
to me what they mean.  But I guess there is no need to do that now if
the plan is to wait for the WG to exist before going any further.

paul

>   Dependency: logical/assertion semantics of
>   package must be explicit.
>   
>   Dependency: expectations regarding the processing (e.g., white space)
>   of content within a package must not violate signature or XML content
>   semantics.
>   
>   Dependency: signed content in/over packages. How to combine element
>   IDs?
>   
>   Dependency: how to show the relative relationships of package parts.
>   For example, how to include XML content with stylesheets and related
>   resources used for rendering.

Received on Friday, 17 September 1999 16:48:40 UTC