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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

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


Subject: EDXL_DE Issue 3: choice in <contentObject> follow-up


> ISSUE 3: A <choice> between <uri>, <derefUri> and
> <namespacedXMLContent> should not be forced in a <contentObject>
> element.
>
> Originator: Michelle Raymond
>
> Reasons: The <uri> element may be desired in the same
> <contentObject> as one containing a <derefUri> element to direct to
> where the dereferenced document is held.
>
> Proposal: Several were mentioned  (see action.)
>
> Action: Michelle to write up the potential proposals discussed.



Here are options for tomorrow's discussion.


Option 1: choice removed and <uri>, <derefUri> and
<namespaceXMLContent> rolled up into the <contentObject>.

contentObject *
	mimeType (REQUIRED)
	contentDescription
	size
	digest
	contentKeyword *
	keyXMLContent
	originatorRole *
	consumerRole *
	confidentiality
	uri 
	derefUri
	namespacedXMLContent

where the mimeType guidelines state that it must be consistent in 1)
the type of content pointed to by the <uri>, 2) the type of content
encoded in the <derefUri> and 3) type = text/xml if
<namespacedXMLContent> is used.


Option 2: revise choice to combine <uri> and <derefUri> and place it
against <namespacedXMLContent> and place elements specific to the two
choices with them

contentObject *
	contentDescription
	size
	digest
	contentKeyword *
	originatorRole *
	consumerRole *
	confidentiality
	choice
		nonXMLContent
			mimeType (REQUIRED)
			uri
			derefUri
		xmlContent
			keyXMLContent
			namespacedXMLContent
		
where the mimeType guidelines state that it must be consistent in 1)
the type of content pointed to by the <uri>, 2) the type of content
encoded in the <derefUri> and 3) type = text/xml if
<namespacedXMLContent> is used.


Option 3: two structures at the contentObject level

contentObject *
	mimeType (REQUIRED)
	contentDescription
	size
	digest
	contentKeyword *
	originatorRole *
	consumerRole *
	confidentiality
	uri
	derefUri

where the mimeType guidelines state that it must be consistent in 1)
the type of content pointed to by the <uri>, 2) the type of content
encoded in the <derefUri>

and

xmlContentObject *
	contentDescription
	size
	digest
	contentKeyword *
	keyXMLContent
	originatorRole *
	consumerRole *
	confidentiality
	namespacedXMLContent


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