[
Lists Home |
Date Index |
Thread Index
]
For sure, and that is why from an amateur perspective (mine),
it looks like a topic map system using roles although I
guess an RDF would work just as well.
If this were done as part of site metadata, wouldn't
that get rid of the need for a centralized database?
In other words, it is just another resource inside
the REST architecture. Would that work for this?
len
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
<Quote>
> Ok, put another way: what is the information
> registered? What rights does it infer or confer? What
> validates that registration and any associations
> made as a result of registration? What responsibilities
> will the registrar assume given a dispute? (See
> the Copyright Office). What responsibilities will
> the registrar explicitly disavow? If one mirrors it,
> is one a registrar or a site serviced by a registrar?
</Quote>
If you're familiar with the ISO 11179 standard ("Information technology
-- Specification and standardization of data elements"), it defines many
of the things you mention above in terms of roles such as "Registration
Authority" (RA), "Submitting Organization" (SO), and "Responsible
Organization" (RO). This standard has been around for quite some time
(at least 12 years), and is still being referred to today in other
standards such as ebXML and UBL.
|
