RE: [wsrp-interop] MarkupType question

Title: RE: [wsrp-interop] MarkupType question

One could add parameters to the mime / content type 

e.g. "text/html; device=tiny" (http://www.zvon.org/tmRFC/RFC2045/Output/index.html section 5) then they would be unique and MIME processors SHOULD ignore parameters that they do not understand. But should W3C device profiles be a 2.0 proposed feature (http://www.w3.org/2001/di/)?

Regards,

Andre

-----Original Message-----

From: Michael Freedman [mailto:] 

Sent: 14 May 2004 00:49

To: wsrp-interop

Subject: [wsrp-interop] MarkupType question

Our mobile guys are looking to adding extensions to the MarkupType type 

that will allow Oracle to further qualify the markup type based on a 

notion of device type.  I.e. in the grand world of multi-device 

environments the mime-type isn't sufficient to qualify rendition 

support; it is useful to have a way to specify mime-type/device-type 

pairs as a way to qualify rendition support.  They asked me whether its 

legal for a producer to generate a portlet description with a markupType 

array which contains multiple entries with the same mime-type value. 

 [This occurs if the producer is using such an extension as it expresses 

the mime-type portion of the mime/device pair in the regular mime-tytpe 

field while the device type information in an extensions].  And if such 

a thing is legal if there are rules for how consumers deal/treat such a 

set of references?  Does it concatentate them?  Does it ignore all but 

one [the first?]? Does it ignore this portlet?  Any of the above as the 

consumer is free to do whatever it wants and we have no recommendation 

on what it should do?   In answering this question can you answer it 

both from the theoretical perspective [i.e. what you think the right 

answer is] and if you have a consumer implementation, from the practical 

perspective [what your current implementation does]?

   -Mike-

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php.