I always feel uneasy about limiting something like data types in a context
where we are defining a common specification for domains and use cases that
we haven't even defined yet.
Rather, I'd like to say that we can support any XML Schema defined data
type. in a RDF document.
For example in queries this would mean that we can optionally qualify
values with the type ( i.e.
oslc.where=dc:created>"2010-04-07T19:57:05.375Z"^^xsd:dateTime ).
BTW: I see the following in the current draft of the core:
oslc:valueType (URI, exactly-one) - may be any of the value types listed
above in OSLC Defined Resources, in URI form:
Literal value-types
String - http://www.w3.org/2001/XMLSchema#string
Integer - http://www.w3.org/2001/XMLSchema#int
Decimal - http://www.w3.org/2001/XMLSchema#decimal
Float - http://www.w3.org/2001/XMLSchema#float
Double - http://www.w3.org/2001/XMLSchema#double
Boolean - http://www.w3.org/2001/XMLSchema#boolean
DateTime - http://www.w3.org/2001/XMLSchema#dateTime
URI - http://open-service.net/xmlns/oslc-core/literal-types#URI
XMLLiteral -
http://open-service.net/xmlns/oslc-core/literal-types#XMLLiteral
Resource value-types
Resource -
http://open-service.net/xmlns/oslc-core/resource-types#Resource
In-Line -
http://open-service.net/xmlns/oslc-core/resource-types#InLine
Complex -
http://open-service.net/xmlns/oslc-core/resource-types#Complex
<jim/>
jim conallen
[email protected]
Rational Software, IBM Software Group
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Scott Bosworth/Raleigh/IBM@IBMUS
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[email protected]
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|04/08/2010 11:32 AM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[oslc-core] olsc properties - "integer" value-type?)
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[email protected]
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Dave, did we conclude yesterday that "integer" should be included in the
list of literal value-types in defining oslc properties? and in the
resource shape section as well?
Should I log an issue for this?
Thanks....Scott
Scott Bosworth | IBM Rational CTO Team | [email protected] | 919.486.2197
(w) | 919.244.3387(m) | 919.254.5271(f)
_______________________________________________
Oslc-Core mailing list
[email protected]
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
