[oslc-core] Proposed property table format

[Dave]

On Thu, Jun 17, 2010 at 4:44 PM, Arthur Ryman <ryman at ca.ibm.com> wrote:

> There is no need to include the URI in the table since the Prefixed Name
> is an abbreviation for the URI. Given the Prefixed Name, we can determine
> the URI
>

Concur.


> We should also state that when we represent data in RDF/XML, that we use a
> QName whose whose local name part is equal to the portion of the Prefixed
> Name that comes after the prefix.
>

We do that in the representation rules already.


> We could use the term "Range" instead of Value Class.
>

Good idea.


>
> The Value-type column could be split into a Node Type column and a
> Representation column.
> For Node Type, the values are Literal, URI Ref, and Blank.
> For Representation, the values are Reference, Inline, and Either
>

I'll respond to this one in the value types thread.

Thanks,
Dave






From:
Dave <snoopdave at gmail.com>
To:
oslc-core <oslc-core at open-services.net>
Date:
06/17/2010 02:08 PM
Subject:
[oslc-core] Proposed property table format
Sent by:
oslc-core-bounces at open-services.net



I created a new property table format for use in OSLC Core. Scroll to the
end to see an example:
  http://open-services.net/bin/view/Main/OSLCCoreLinksDRAFT

The column names are:
  - Prefixed Name
  - Occurs
  - Extended
  - Value-type
  - Value Class
  - URI and Description

Spec leads, will this work for your spec? I am leaving things out, naming
things inappropriately?  That and other feedback is most welcome...

Thanks,
- Dave
_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100618/f0c8e7f9/attachment-0003.html>