[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fw: ISSUE BP-25: Title: WS-HumanTask Attachment Info Data Type elementcontentType is ambiguous
Revised proposal for BP-25 based on the discussion in the TC call on July
23.
The following changes are made to Gerhard's original proposal:
(a) for the new contentCategory field, replace the xsd:string type by an
xsd:anyURI type
(b) for the new contentCategory field, replace the predefined xsd:string
values by xsd:anyURI values
(c) add a sentence that support for the predefined values is mandated
(d) the definition of the predefined constants in WS-HT XML Schema
artifacts is not considered here - it will be addressed in issue BP-20
1. Extend type tAttachmentInfo with the element contentCategory (WS-HT spec
section 3.4.3.1. and ws-humantask-types.xsd):
<xsd:element name="attachmentInfo" type="tAttachmentInfo" />
<xsd:complexType name="tAttachmentInfo">
<xsd:sequence>
<xsd:element name="name" type="xsd:string" />
<xsd:element name="accessType" type="xsd:string" />
<xsd:element name="contentType" type="xsd:string" />
<xsd:element name="contentCategory" type="xsd:anyURI" />
<xsd:element name="attachedAt" type="xsd:dateTime" />
<xsd:element name="attachedBy" type="htd:tUser" />
<xsd:any minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
2. Add the following spec text to WS-HT spec section 3.4.3.1. (marked blue)
[...]
The contentType of an attachment can be any valid XML schema type,
including xsd:any, or any MIME type. The attachment data is assumed to
be of that specified content type.
The contentCategory of an attachment is a URI used to qualify the
contentType. While contentType contains the type of the attachment, the
contentCategory specifies the type system used when defining the
contentType. Predefined values for contentCategory are
-- "http://www.w3.org/2001/XMLSchema"; if XML Schema types are used for
the contentType
-- "http://www.iana.org/assignments/media-types/"; if MIME types are used
for the contentType
The set of values is extensible. A WS-HumanTask compliant implementation
MUST support the use of XML Schema types and MIME types as content
categories, indicated by the predefined URI values shown above.
The accessType element indicates if the attachment is specified inline
or by reference.
[...]
Kind Regards
DK
(Embedded image moved to file:
pic22066.jpg)IBM
Dieter König IBM Deutschland Research &
Development GmbH
Senior Technical Staff Schönaicher Str. 220 Vorsitzender des Aufsichtsrats:
Member Martin Jetter
WebSphere Process D-71032 Böblingen Geschäftsführung: Herbert
Server Architect Kircher
(Embedded image moved (Embedded image moved to file: Sitz der Gesellschaft:
to file: pic14980.gif) pic03420.gif)Phone (office): Böblingen
Mail: (+49) 7031-16-3426
dieterkoenig@de.ibm.com
(Embedded image moved (Embedded image moved to file: Registergericht: Amtsgericht
to file: pic30991.gif) pic10312.gif)Phone (home Stuttgart, HRB 243294
WebSphere Software office): (+49) 7032-201464
----- Forwarded by Dieter Koenig1/Germany/IBM on 25.07.2008 18:20 -----
From: Gerhard Pfau/Germany/IBM
To: bpel4people@lists.oasis-open.org
Cc: Dieter Koenig1/Germany/IBM@IBMDE, Matthias Kloppmann/Germany/IBM@IBMDE@IBMDE, Frank Leymann
<frank.leymann@iaas.uni-stuttgart.de>
Date: 21.07.2008 14:38
Subject: ISSUE BP-25: Title: WS-HumanTask Attachment Info Data Type element contentType is ambiguous
Dear all,
pls. find below a proposal for resolving ISSUE BP-25 (
http://www.osoa.org/jira/browse/BP-25):
1. Extend type tAttachmentInfo with the element contentCategory:
<xsd:element name="attachmentInfo" type="tAttachmentInfo" />
<xsd:complexType name="tAttachmentInfo">
<xsd:sequence>
<xsd:element name="name" type="xsd:string" />
<xsd:element name="accessType" type="xsd:string" />
<xsd:element name="contentType" type="xsd:string" />
<xsd:element name="contentCategory" type="xsd:string" />
<xsd:element name="attachedAt" type="xsd:dateTime" />
<xsd:element name="attachedBy" type="htd:tUser" />
<xsd:any minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
2. Add the following spec text (blue)
[...]
The contentType of an attachment can be any valid XML schema type,
including xsd:any, or any MIME type. The attachment data is assumed to
be of that type.
The contentCategory of an attachment is a string used to qualify the
contentType. While contentType contains the type of the attachment, the
contentCategory specifies the type system used when defining the
contentType. Possible values for contentCategory are "MIME" and
"XSD-Schema". The set of values is extensible.
The accessType element indicates if the attachment is specified inline
or by reference. [...]
3. Define string constants to be used as values for contentCategory:
Add spec text to define the following constants for contentCategory:
"MIME"
"XML-Schema"
Here is the text again as PDF, in case the colors and fonts don't make it:
[attachment "WS-HT - Proposed Resolution for BP-25.pdf" deleted by Dieter
Koenig1/Germany/IBM]
As Wednesday this week is the first day of my summer vacation Dieter is
going to cover BP-25 during the TC meeting.
Best regards,
Gerhard
Gerhard
Pfau
IBM Senior
Technical
Staff
Member
Lead
Architect,
Human Task
Manager
Member, (Embedded
IBM image moved
Academy of to file:
Technology pic30126.gif)
Member,
Technical
Expert
Council CR
phone: +49-(0)7031-16-4899
fax: +49-(0)7031-16-4890
mobile: +49-(0)160-533-6578
"Make everything as simple as possible, but not simpler." -
Albert Einstein
Legal Information:
IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Martin Jetter;
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
