- From: Souripriya Das <souripriya.das@oracle.com>
- Date: Wed, 04 May 2011 09:45:59 -0400
- To: public-rdb2rdf-wg@w3.org
I changed the class name to rr:NamedRowSourceClass -- sounds simpler (and easier to spell :-)). -- Souri. Using this new naming in Alex's example: <TriplesMap1> a rr:TriplesMapClass; rr:rowSource <MyTable>; ... <TriplesMap2> a rr:TriplesMapClass; rr:rowSource <GetFailStudents>; ... <TriplesMap3> a rr:TriplesMapClass; rr: rowSource <GetFailStudents>; ... <MyTable> a rr:NamedRowSourceClass; rr:tableName "my_table"; rr:tableOwner "my_schema". <GetFailStudents> a rr:QueryResultRowSourceClass; rr:SQLQuery "SELECT id, name FROM my_schema.students WHERE grade< 50". Thanks, - Souri. On 5/4/2011 9:34 AM, Souripriya Das wrote: > I too like Alexander's proposal. Abstracting the details of, what we call a rowsource, away from TriplesMap seems nice. > > Maybe we need to change the names a bit. Specifically, while "relation" is a well-understood term in relational algebra, its use causes some confusion with relationship (or predicates) in RDF. > > So, instead of "relation", we could use "rowSource" as the theme term. For example, instead of rr:relation we could use rr:rowSource as the property name whose value identifies the source for the rows that a TriplesMap is trying to map to RDF triples. > > Using this new naming in Alex's example: > > <TriplesMap1> > a rr:TriplesMapClass; > rr:rowSource<MyTable>; > ... > > <TriplesMap2> > a rr:TriplesMapClass; > rr:rowSource<GetFailStudents>; > ... > > <TriplesMap3> > a rr:TriplesMapClass; > rr: rowSource<GetFailStudents>; > ... > > <MyTable> > a rr:ReferencableRowSourceClass; > rr:tableName "my_table"; > rr:tableOwner "my_schema". > > <GetFailStudents> > a rr:QueryResultRowSourceClass; > rr:SQLQuery "SELECT id, name FROM my_schema.students WHERE grade< 50". > > Thanks, > - Souri. > > >
Received on Wednesday, 4 May 2011 13:46:40 UTC