[oslc-core] Proposal for Issue-25: Encoding of UI preview label

[Joe Ross]

I think we are saying that we are not changing the OSLC-core defined data 
type for the dcterms:identifier property. It would still have a value type 
of XMLLiteral when used in RDF which is based on OSLC core. Is that right?

Joe

================================================
Joe Ross/Austin/IBM, joeross at us.ibm.com
Tivoli Autonomic Computing & Component Technologies
512-286-8311, T/L 363-8311



From:   Steve K Speicher/Raleigh/IBM
To:     John Arwe/Poughkeepsie/IBM at IBMUS, 
Cc:     Joe Ross/Austin/IBM at IBMUS, oslc-core at open-services.net, 
oslc-core-bounces at open-services.net
Date:   07/27/2012 07:25 AM
Subject:        Re: [oslc-core] Proposal for Issue-25: Encoding of UI 
preview label



> Something I need to be clear on: is it the case that this issue applies 
only
> to UI preview because UI preview is the only case in OSLC where a 
resource 
> is defined to be XML and not RDF? 
> Since XMLLiteral is defined by RDF, an XML-based resource definition 
does 
> not "have access to" its definition (it's outside of XML, and going 
outside 
> of XML for its definition is not desireable)? 

This issue is really about that the content of these XML elements really 
should just be strings and not embedded XML content, regarding of how the 
value type is defined (i.e. XMLLiteral definition in RDF/XML or complex 
content in XML).  It just happens we were down a path "make our XML 
consumable by RDF/XML parsers as well" which added to some confusion.  The 
issue originated due to the complexities of the primary consumer of this 
content is HTML/JS, so having to parse the content and convert to HTML 
tags was onerous compared with just grabbing the content of the 
title/description and just jamming into a node.

Hope that adds some clarity.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20120727/7b8920be/attachment-0003.html>