Re: [oslc-core] JSON-LD of compact resources

[Samuel Padgett <spadgett@us.ibm.com>]

Hey, John. Steve and I had discussed this, and I agree. One problem is that we might need a need property or we'd be changing the meaning of an existing property. It's also used by the Publisher in the service description document. Would we want to change that too?

http://open-services.net/ns/core#

    <rdf:Property rdf:about="http://open-services.net/ns/core#icon">
        <rdfs:isDefinedBy rdf:resource="http://open-services.net/ns/core#" />
        <rdfs:label>icon</rdfs:label>
        <rdfs:comment>URL to an icon file that represents the provider. This icon should be a favicon format and 16x16 pixels in size.</rdfs:comment>
        <rdfs:seeAlso
rdf:resource="http://open-services.net/bin/view/Main/OslcCoreSpecification#Resource_Publisher" />
    </rdf:Property>

--
Samuel Padgett | IBM Rational | spadgett@us.ibm.com
Eclipse Lyo: Enabling tool integration with OSLC


John Arwe---05/01/2014 10:54:20 AM---in  http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/specs/resource-preview.html

From:	John Arwe/Poughkeepsie/IBM@IBMUS
To:	oslc-core@lists.oasis-open.org
Date:	05/01/2014 10:54 AM
Subject:	Re: [oslc-core] JSON-LD of compact resources
Sent by:	<oslc-core@lists.oasis-open.org>

---

in http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/specs/resource-preview.html section 4 Compact, I think icon should also be a separate resource ala the previews. 
The icon has its own properties, like title, and its own URI (the icon property shows this), so this seems pretty obvious.

Implementations that want to populate the OSLC 2.0 properties as well would still be free to do so, in order to interop with 2.0 clients. 

Best Regards, John

Voice US 845-435-9470  BluePages 
Tivoli OSLC Lead - Show me the Scenario