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


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

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

Subject: RE: [dss] SignResponse::Profile attribute.

Sorry about the previous post (which was signed). Re-posting in case you
couldn't read it.



   I think from the threads surrounding the issue, the assertion was that an
implementation must implement a particular interface under that particular
schema assumption. That may be core, or that may be a profile. There is
provision for additional profiles which sheds light on this question raised
by JC. Excerpt from 2.8.4 of core reads as follows.

quote ...

The <AdditionalProfile> element can appear multiple times in a request. It
indicates additional profiles which modify the "main" (Ed's emphasis)
profile specified by the Profile attribute (thus the Profile attribute MUST
be present; see sections 3.1 and 4.1 for details of this attribute). The
interpretation of additional profiles is determined by the main profile.

... end quote

Note the use of "main profile" and "MUST".

I think a service must be true and unambiguous wrt the interface contract
and policy of its "main profile" and therefore this attribute is correctly
specified as use="required" on response elements (i.e. section 3.2 and 4.2)
but can be left optional on request elements (i.e. section 3.1 and 4.1).

I think the schema and the schema snippets in the doc are correct and the
text below them are wrong.


-----Original Message-----
From: Juan Carlos Cruellas [mailto:cruellas@ac.upc.edu] 
Sent: April 25, 2005 9:41 AM
To: DSS TC List
Subject: [dss] SignResponse::Profile attribute.

Dear all,

In section 3.2 of the core, third paragraph says:

"Profile [Optional]
This attribute indicates the particular DSS profile used by the server. 
It may be used by the
client for logging purposes or to make sure the server implements a profile
the client expects."

It seems from this text that this attribute is optional. Nevertheless, in
the XML schema (in both, the core document and the .xsd file) it appears as

<xs:attribute name="Profile" type="xs:anyURI" use="required"/>

Should it not be use="optional"?

Juan Carlos

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS

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