Re: [dss] ProcessingDetails

[Juan Carlos Cruellas Ibarz <cruellas@ac.upc.es>]

Yes, Andreas, 

but the xs:any  allows you to proceed further in the machine-readable
details, so that  for instance, 
if a revoked certificate is encountered, you can define a structure
identifying such a certificate, or if 
a certain property in a signature is needed and the verifier does not find
it, one can define a way of
identifying such a property...
And this can be used by a human being of by the application.... would also
these aspects 
be out of the initial scope and leave them unspecified until somebody
interested decides to
do the effort?

Regards


Juan Carlos


At 14:43 16/01/2004 +0100, Andreas Kuehne wrote:
>Hi Juan Carlos,
>
>my view is : standardize the machine readable aspects, leave the human
readable part as an <any> !
>
>This way both sides of requirements can be solved without overspecifying
the readable text !
>
>
>Greetings
>
>Andreas
>
>> >But I think it would be an overspecification if we try to define what
>> should be included in the information section. I would leave it to the
>> implementor to decide whats the content of their informative section and
>> what not. On one side we could demand, on the other side we could limitate
>> too much. 
>> >Maybe someone wants to include different localizations, maybe someone
>> wants to add a pretty HTML version ...
>> >
>> >Greetings
>> 
>> I see your point...would then your conclusion be that this is a matter of
>> every profile that wants to include details even
>> if with time some of these details contain the same information within
>> different structures?... what I think is that
>> if somebody defines a profile with certain structues that somebody else can
>> use in other one, then these structures
>> would be reused...
>
>___________________________________________________________________________
___
>Nachrichten, Musik und Spiele schnell und einfach per Quickstart im 
>WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110
>