[oslc-core] Proposed property table format

[Arthur Ryman]

Dave,

Thx for creating the table.

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

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 could use the term "Range" instead of Value Class.

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

Regards, 
___________________________________________________________________________ 

Arthur Ryman, PhD, DE


Chief Architect, Project and Portfolio Management

IBM Software, Rational

Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube







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