need to use more descriptive relationships in building triple statements
Morpho and other clients that build triple statements in eml-dataset docs
should use more descriptive relationship strings. They should also come from
an standard list. Perhaps:
is data entity in
provides access control rules for
provides data entity information for
provides project information for
provides protocol information for
provides attribute information for
provides physical file information for
etc. Lastly, some relationships for data files such as:
isDataFileFor(C:\Documents and Settings\cjones\DESKTOP\allsp.txt)
are being generated by the package wizard. Seems like the path should be nixed
from the relationship...
#1 Updated by Dan Higgins over 19 years ago
Discussions at NCEAS on 3/13/2002 indicated that using sentences for
relationships is highly desired for user readability when a triple is displayed.
<subject> provides access control rules for <object>.
It was also noted that since <subject> and <object> are just ids, data types of
both should be shown in the relationship where appropriate. e.g.
<subject> provides entity information for data <object>
<subject> provides entity information for package <object>
might be used to distinguish when an entity is linked to a package (e.g. no data
in package) and when it is linked to a data object.
#2 Updated by Dan Higgins over 19 years ago
Triples are now created with "human-readable" relationship phrases that indicate
just what the triple is for; e.g.
"provides table-entity information for package"
"provides eml-attribute information for Table"
"provides eml-physical information for Table"
"provides access control rules for"