JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-ARCHITECTURE Archives


DC-ARCHITECTURE Archives

DC-ARCHITECTURE Archives


DC-ARCHITECTURE@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-ARCHITECTURE Home

DC-ARCHITECTURE Home

DC-ARCHITECTURE  January 2018

DC-ARCHITECTURE January 2018

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: [RDF AP] First draft Tabular Metadata Profiles

From:

Karen Coyle <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Mon, 22 Jan 2018 07:52:56 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (172 lines)

Hi, Mariana - thanks for giving it a read. Comments below.

On 1/22/18 2:14 AM, Mariana Curado Malta wrote:
> Hi Karen,
> 
> 
> This is interesting.
> 
> 
> I have the following considerations:
> 
> 
> 1. The "proposed ontology" - why do you call it an ontology ?

I'm not particular on what it is called. Vocabulary is fine, too.

> 
> I can see that it is a descriptive metadata application profile (MAP) -
> or upper MAP, that is, it describes a MAP for a specific context (as far
> as I can see a MAP is a data model with declaration of RDF
> vocabulary terms and its constraints). So it is another level of MAP
> that defines how to describe a MAP.  Should we call it an ontology or
> should we set a specific name for this "kind" of MAPs? - you called it
> DSP, actually, but I think we should be carreful on how we call things
> and specially try to stick to the same names, just giving descriptive
> variation names.

This is meta, which is tricky. The idea was to develop terms to describe
profiles. I was generally following the DSP structure [1] but did not
want to mint new properties where there were ones I thought I could use.
The result is that this ends up being a profile for profiles. And I
wonder if there still needs to be a truly meta vocabulary for profiles.

> 
> 
> 2. The "diagram for the vocabulary" - what vocabulary? The ontology?
> 
> Why to you use a relational model, with keys, and foreign keys? I would
> do a conceptual model in a UML class diagram since it is more clean and
> less "tableitis" [1]. 

This is because of the intention to make use of the work of the tabular
data W3C working group.[2] Although tables are perhaps not the ideal
technology, the fact is that many application profiles use tables or
some tabular form (e.g. in spreadsheets and even Word documents). The
tabular data group has developed code that transforms the tables of
instance data into either RDF or JSON. That code needs foreign keys.

Your statement below about URIs and IDKeys is exactly where I started
and this may be why a more "meta" model would be needed. Perhaps I need
to name this something more like "tabular profile vocabulary" and have
that be a profile of a more general profile. Do you think that removing
the foreign keys would be sufficient to create that general profile?
that would not be difficult, and adding in the foreign keys for the
tabular data profile would then be simple.

> 
> We guys from the software engineer background suffer a lot of tableitis
> and it is something that we need to be cured of!
> 
> 
> Each IDKey is an URI, and the foreign key will be a property (if needed
> - probably not - with the range being the entity from where the
> foreignKey comes from). Each line with an arrow is another property with
> the range to the other entity. I don't really think you should introduce
> this entropy in the diagram.
> 
> 
> 3. SchemaList.csv
> 
> How do you describe "Description", "Statement", "Datatype value",
> "Literal value" and "Object value"? - that is, the entities of your
> relational model?

Yes, I do need to go back and create a column for definitions. Note that
although I used "description set" "description" and "statement" from the
DSP, I must say that I like the terms used in the BIBFRAME profiles. [3]

> 
> 
> I don't know if what I say makes sense to you.
> 

It absolutely does. And thanks.

kc
[1] http://dublincore.org/documents/dc-dsp/
[2] https://www.w3.org/TR/tabular-metadata/
[3] http://www.loc.gov/bibframe/docs/bibframe-profiles.html


> 
> Thank you and regards, Mariana
> 
> 
> 
> [1] http://geverest.umn.edu/home/papers-and-publications/-tableitis
> 
> 
> 1464102710367_image005.png
> 
> POLITÉCNICO DO PORTO. INSTITUTO SUPERIOR DE CONTABILIDADE E
> ADMINISTRAÇÃO DO PORTO
> 
> POLYTECHNIC OF PORTO. PORTO ACCOUNTING AND BUSINESS SCHOOL
> 
> ——
> 
> 
> Mariana Curado Malta
> 
> Professora Adjunta. Senior Lecturer
> 
> Rua Jaime Lopes Amorim, s/n. 4465-004 S. Mamede de Infesta. PORTUGAL   
> 
> T +351 22 905 00 XX  F +351 22 902 58 99
> 
> 
> [log in to unmask]
> 
> CEOS.PP <https://www.iscap.ipp.pt/investigacao-1/centros/ceos/ceos>
> Research Center
> Researcher ID: http://www.researcherid.com/rid/D-8627-2014
> 
> ------------------------------------------------------------------------
> *De:* DCMI Architecture Forum <[log in to unmask]> em nome
> de Karen Coyle <[log in to unmask]>
> *Enviado:* 21 de janeiro de 2018 18:39:47
> *Para:* [log in to unmask]
> *Assunto:* [RDF AP] First draft Tabular Metadata Profiles
>  
> All,
> 
> It's been a while since we had the DCMI RDF AP group active, and I feel
> that we took a bit of a detour due to the W3C work on RDF validation.
> However, I remain interested in finding a truly "core" solution for the
> many small and not-so-small developers who are working with metadata and
> need some direction for the formulation of useful profiles.
> 
> I have been working with a small group of folks to develop a viable
> method for creating simple profiles in a tabular form. The work so far
> is on my github site.[1] The home page there includes a short
> explanation of the goals of the project. Files highlighted on that page
> include a statement of requirements [2], and a proposed
> ontology/vocabulary [3]. There is also a diagram giving a picture of the
> area covered by the vocabulary [4]. Finally, there is a tabular
> comparison of this vocabulary, the DSP vocabulary, and the vocabulary of
> BIBFRAME profiles [5].
> 
> I consider this a beginning, with nothing set in stone at this point,
> and appreciate all comments, questions, suggestions, corrections, and of
> course offers to participate in making this work.
> 
> Thank you,
> kc
> [1] https://github.com/kcoyle/RDF-AP/
> [2] https://github.com/kcoyle/RDF-AP/blob/master/requirements.md
> [3] https://github.com/kcoyle/RDF-AP/blob/master/schemaList.csv
> [4] https://github.com/kcoyle/RDF-AP/blob/master/dspDiagram2.jpg
> [5] https://github.com/kcoyle/RDF-AP/blob/master/BIBFRAMEcompare.csv
> 
> -- 
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> m: 1-510-435-8234 (Signal)
> skype: kcoylenet/+1-510-984-3600

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234 (Signal)
skype: kcoylenet/+1-510-984-3600

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
September 2005
August 2005
July 2005
June 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
December 2000
November 2000
October 2000


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager