Details view: Requirements

Views
Add
Edit
- Edit page
- Delete page
Share
Login
- Member login
- Register now for a free account
🔎

Requirements Issue1 #440314 What are the use cases and/or technical requirements for knowledge federation?

CONTEXT(Help)

Knowledge Federation Webservices Protocol »Knowledge Federation Webservices ProtocolKnowledge Federation Webservices Protocol☜Permitting communication among many different participants in an online knowledge federation.☜F1CEB7

■

RequirementsRequirements☜What are the use cases and/or technical requirements for knowledge federation?☜FFB597

●

An idea can be transcluded in a different platform »An idea can be transcluded in a different platformAn idea can be transcluded in a different platform☜It should be possible to transclude an idea coming from a different platform into a given platform, i.e. import it with a live reference. Whether properties of the transcluded idea are updated manually or automatically could be implementation-dependent.☜59C6EF

●

An idea can have multiple expressions »An idea can have multiple expressionsAn idea can have multiple expressions☜There is not always a canonical expression. We want to allow choral explanations, multilingualism, or an explanation of an idea in the context of a given view.☜59C6EF

●

Assertions can be subjects »Assertions can be subjectsAssertions can be subjects☜Any assertion can be contested, and as such can become the topic of another assertion. (Compare the unwieldiness of RDF reification.) In other terms, sometimes it makes sense to treat an edge like a node.(Also, sometimes, it makes sense to represent that node like an edge in a given view, to declutter that view.)☜59C6EF

●

The communication between platforms should allow a services ecosystem »The communication between platforms should allow a services ecosystemThe communication between platforms should allow a services ecosystem☜It should be possible to develop a platform-independent (micro-)service that enriches the information base of the platforms.It means that the service needs access to the platforms data, hopefully in a dynamic way, and needs to send information back to the platform.☜59C6EF

●

Topics evolve in time »Topics evolve in timeTopics evolve in time☜We may discover that a topic (idea, subject...) is the same than another one (merge) or hides a distinction between two different ideas (fork). Also, an idea may simply evolve over time.I may agree with rough project, and even vote for it, but disagree when I see how it evolves. I may want to fork it after the fact. So references should be marked with time.☜59C6EF

Heading

Summary

Click the button to enter task scheduling information

Details

Enter task details

Message text

Select assignee(s)

Due date (click calendar)

RadDatePicker

Open the calendar popup.

Calendar

Title and navigation
Title and navigation
<<	<	November 2024	>	<<

November 2024
	S	M	T	W	T	F	S
44	27	28	29	30	31	1	2
45	3	4	5	6	7	8	9
46	10	11	12	13	14	15	16
47	17	18	19	20	21	22	23
48	24	25	26	27	28	29	30
49	1	2	3	4	5	6	7

Reminder

Ready to post Copy to text

Task assignment(s) have been emailed and cannot now be altered

Lock

Comment graphing options

Choose comments:Comment onlyWhole threadAll comments

Choose location:To a new mapTo this map

New map options

Select map ontology Graph to private map

+Comments (1)

- CommentsAdd a commentNewest firstOldest firstShow threads

+Citations (0)

- CitationsAdd new citationList by: CiterankMap

+About

- About

Entered by:- Marc-Antoine Parent
NodeID: #440314
Node type: Issue
Entry date (GMT): 8/31/2016 9:09:00 PM
Last edit date (GMT): 8/31/2016 9:09:00 PM
Show other editors
Incoming cross-relations: 0
Outgoing cross-relations: 0
Average rating: 0 by 0 users

x Select file to upload