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


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

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

Subject: [OASIS Issue Tracker] Commented: (CMIS-130) XML and HTMLproperties underspecified

    [ http://tools.oasis-open.org/issues/browse/CMIS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10239#action_10239 ] 

Julian Reschke commented on CMIS-130:

The XSD should follow from the design, not the other way around.

So, two questions:

For an XML property is:


a legal value? Is


If both are, are they to be handled differently?

For HTML, is



What I'm trying to say is that the requirements for HTML and XML are totally different, and that we need to be careful with terminology.

See http://greenbytes.de/tech/webdav/rfc4287.html#rfc.section.3.1.1 for an example what needs to be done.

>  XML and HTML properties underspecified
> ---------------------------------------
>                 Key: CMIS-130
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-130
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.50, Draft 0.6
>            Reporter: Julian Reschke
>            Assignee: Ethan Gur-esh
> (note this basically repeats CMIS-34, as far as I can tell, none of these issues have indeed been addressed by the recorded proposal)
> "An XML property holds a valid fragment of Extensible Markup Language (XML) content."
> Valid or well-formed? Escaped? When valid, how is this decided (XML validity implies that the content references a DTD which is used for validation)
> "An HTML property holds a valid fragment of Hypertext Markup Language (HTML) content."
> Valid? According to which DTD? HTML4? XHTML? Escaped? (same as for XML)
> Examples please...
> "For XML Types:
> - URI SchemaURI This attribute is for properties of type "XML" only. It provides the URI location of an XML schema to which the property value MUST conform."
> I'm not sure how exactly this is supposed to work if the property takes an XML *fragment*, such as "foo <i>bar</i>". I guess a minimal example would be extremely helpful.
> Also, having a normative requirement on XML Schema well be a *significant* burden for implementations, so I'd like the TC to discuss whether this is really desirable.
> "- String Encoding This attribute is for properties of type "XML" only. It specifies the encoding used for the property value (e.g. UTF-8, etc.)."
> If the property is marshalled as XML or String everywhere, what exactly is this good for? Why do we need it for XML, but not for Strings?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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